Jiminny can log your recorded meetings to your CRM automatically, or you can do it manually after each meeting. This article explains the difference and how to set up each option for your teams.

Manual logging lets you review and confirm CRM details after each meeting before the activity is logged. This is useful when your CRM data is complex — for example, when you need to manually associate the call with the correct contact, lead, or deal. For how reps log manually, see Logging a call.

Automatic logging sends meeting data to your CRM without any action from the rep. Once set up, every recorded meeting that matches your playbook criteria is logged automatically against the correct CRM record.

Jiminny automatically detects the activity type for each call, so even complex setups with multiple activity types are handled without manual input. Combined with AI CRM filling, which automatically populates CRM fields after the call, automatic logging removes the admin burden from reps entirely.

Note: Automatic logging matches meetings to CRM records based on attendee email domains. If no matching account is found, the call is tagged as Unknown. Keep your CRM accounts up to date to avoid this.

1. Set up your playbook

Go to Settings > AI Automations > Playbooks & Activity Types and make sure your playbook reflects your activity types. This should match your CRM setup — auto-logging uses the playbook to determine how meetings are categorised and logged.

You can set a default playbook to ensure any unassigned team members are covered automatically.

2. Define your teams

Go to Settings > Teams and set up your teams — for example, BDRs and AEs. Each team is linked to a playbook.

3. Enable logging for each team

Go to Settings > CRM Activity Logging > By Team. The page lists every team and its current logging settings, and you can search and filter to find a team. Select a team to edit its settings.

Note: Each team has its own configuration — there is no shared setting that applies across all existing teams. New teams start with the defaults described below.

4. Choose a default activity type (optional)

You can select a default activity type, used when a call's activity type hasn't been detected automatically or set manually. This is optional — if you leave it as None, calls without a detected activity type are still logged, just without one.

5. Choose when activities are logged

Choose how long after the meeting ends Jiminny waits before logging to the CRM — from instantly up to 8 hours. This gives reps a window to review or adjust before the activity is sent.

6. Set the defaults for new teams

The page shows the logging settings that will be applied whenever a new team is created. Select it to change them. Manual and auto logging are on by default for new teams, and each team can be adjusted individually after creation.

1. What happens if Jiminny can't detect the activity type?
If you've set a default activity type, Jiminny uses it. If you haven't, the call is still logged — without an activity type.

2. Can I manually log a meeting if auto-logging is enabled?
Yes. You can still log or update a meeting manually from the meeting page in Jiminny at any time.