Your playbook maps your sales process into a set of activity types — the calls and meetings that move a deal forward. Jiminny uses these types to categorise conversations and give you richer coaching and reporting.
Playbooks are configured in Organisation Settings > Playbooks & Coaching Frameworks, available to Admins and Managers. Each team is assigned one playbook, so you can segment users flexibly. For example:
Sales (Sales Playbook)
Customer Success – UK (Success Playbook)
Customer Success – US (Success Playbook)
Your account starts empty. Most teams begin with a Sales Playbook and a Success Playbook.
Creating a playbook
Go to Organisation Settings > Playbooks & Coaching Frameworks.
Click Add Playbook.
Enter the details:
Name — something descriptive, e.g. Sales Playbook.
Log activity as — Tasks or Events (Salesforce only).
Enabled — turn this on if you want the playbook to be used.
Click Save.
Managing activity types
Activity types are the steps that make up your process — a Sales Playbook might use Cold Call, Discovery Call, Web Demo, Proposal Call and Price Negotiation. These are different from opportunity stages: an activity is what moves a stage forward.
When you create a playbook, Jiminny automatically pulls in all activity types from your connected CRM. Manage your types in your CRM — create, rename and delete them there, and Jiminny keeps them in sync (see below). In Jiminny, select Activity Types under the playbook to:
Disable a type a playbook doesn't use — toggle off Enabled to stop it being used in this playbook.
Set where it applies — choose whether the type applies to conference meetings, dialer calls, or both.
Reorder types — drag and drop them into the sequence you want. Jiminny keeps this order in dropdowns.
Note: Zoho doesn't have activity types, so there's nothing to pull. If you use Zoho, manage your activity types directly in Jiminny.
You can add a type manually, but this is the exception — a manually added type won't be logged to your CRM unless it also exists there with the exact same name. Wherever possible, add it in your CRM and let it sync.
Once your types are in place, you can set up AI detection of the activity type so Jiminny assigns the right type to each call automatically. This involves writing a description for each type and testing it before you enable Autodetect — the linked article walks through it.
How activity types sync with your CRM
Your CRM is the source of truth for activity types, and Jiminny keeps your playbooks in sync with it. Sync runs once a day: new types are added, renamed ones are updated, and types that no longer exist in your CRM are removed — or disabled if they've already been used on calls, so those calls keep their type.
To apply CRM changes straight away rather than waiting for the daily sync, click the ↻ button in the top right to pull the latest.
Each activity type shows whether it is connected to your CRM:
Connected — the type exists in your CRM and will be included when calls are logged there.
Not connected — the type exists only in Jiminny, so it won't be included when calls are logged to your CRM. To connect it, add it to your CRM with the exact same name, then pull the latest.
A type is only used when it is enabled for the playbook, whatever its connection status.
FAQ
How do I remove an activity type I don't need?
You can't delete activity types in Jiminny — disable it for the playbook instead. To remove it everywhere, delete it in your CRM and Jiminny will sync the change.Why is one of my activity types marked as not connected?
It exists only in Jiminny — either you added it manually, or it was removed from your CRM. Add it to your CRM with the exact same name and pull the latest to connect it.