AI call notes via Otter (L2)
A sanctioned recorder summarizes calls and posts to Slack. It is not coaching, it is transcription with lipstick.
The steps
- 01
Establish the unified workspace
To begin, you must select and deploy a single sanctioned recording tool across the entire sales org to prevent data silos. In this playbook, we utilize 'Otter.ai' for its robust workspace management. • Action: Log into Otter.ai as an admin. Navigate to 'Account Settings' > 'Workspace' and invite your team members using their professional email addresses. • Config: Under 'Security & Permissions,' toggle 'Enforce single sign-on (SSO)' if your company uses Okta or Google Workspace. Disable the 'Allow guests to record' feature to maintain security. • Settings: Instruct all users to go to 'Account Settings' > 'Meetings' and toggle 'Auto-join all calendar events with an invite link' to 'ON.' This ensures no call is missed because a rep forgot to click record. • Owner: Sales Operations or IT Admin. • Time Estimate: 45 minutes for setup; 15 minutes for team onboarding. • Pitfall: Avoid 'Shadow AI' where reps use personal accounts. Ensure everyone is on the same Business or Enterprise workspace for centralized data. • Definition of Done: All reps appear in the 'Members' list, and the 'Auto-join' setting is confirmed on three random workstations.
- 02
Sync Otter to your CRM system
The value of AI transcription is lost if it lives in a silo. You must link Otter to your CRM (HubSpot or Salesforce) to automate data entry. • Action: In Otter, navigate to 'Apps' or 'Integrations' and select your CRM. Follow the OAuth prompts to authorize the connection. • Config: Map the 'Meeting Summary' and 'Action Items' fields in Otter to specific 'Note' or 'Task' objects in the CRM. For Salesforce, ensure the Otter integration has permission to write to the 'Task' and 'Opportunity' objects. • Automation: Set the sync trigger to 'Immediate' so that as soon as a meeting transcript is finalized, the summary is pushed to the 'Activity Timeline' of the matching Lead or Contact record based on the attendee's email address. • Owner: CRM Administrator. • Time Estimate: 30 minutes. • Pitfall: The sync will fail if the CRM contact doesn't exist. Ensure your SDRs are creating Lead/Contact records prior to the call. • Definition of Done: After a test call, the 'Notes' section of the CRM Lead record contains a bulleted summary generated by Otter.
- 03
Configure the Slack notification loop
Move from passive transcription to active notification by pushing summaries to a shared Slack channel. This allows managers and cross-functional teams to stay updated without attending every meeting. • Action: Create a new Slack channel named #feed-sales-notes. In Otter, go to 'Account Settings' > 'Integrations' > 'Slack.' • Config: Select 'Post summaries and action items to a channel.' Map specific folders (e.g., 'AEs' or 'SDRs') to the #feed-sales-notes channel. • Selection: Choose the 'Summary' and 'Keywords' levels to be posted. Avoid posting the full 3,000-word transcript to Slack; only post the 'Otter Outline' which contains the TL;DR. • Owner: RevOps or Sales Manager. • Time Estimate: 20 minutes. • Pitfall: Over-notification. If the channel is too noisy, create separate channels for #notes-discovery and #notes-closing to keep the signal-to-noise ratio high. • Definition of Done: A summary of a test meeting appears in the designated Slack channel within 5 minutes of the call ending.
- 04
Optimize AI output quality
Standard AI summaries can be generic. You must 'tune' the AI output to capture industry-specific data points by creating a custom 'Meeting Type' or 'Prompt template' if your tier allows, or by training reps on the 'Custom Vocabulary' feature. • Action: Go to 'Workspace Settings' > 'Custom Vocabulary.' Add your company name, product names, competitor names, and industry jargon (e.g., 'BANT,' 'MEDDPICC,' 'Kubernetes'). • Prompting: If using the Otter AI Chat, provide reps with a 'Golden Prompt' to run after every call: 'Summarize this meeting using the MEDDPICC framework. Identify the Economic Buyer, the Decision Criteria, and specific pain points mentioned regarding [Product].' • Owner: Sales Enablement or Team Lead. • Time Estimate: 1 hour for vocabulary setup; 15 minutes for prompt training. • Pitfall: Ignoring the vocabulary list leads to 'hallucinations' where the AI misspells your product or misunderstands technical terms. • Definition of Done: Summaries consistently use correct terminology and follow the requested sales framework.
- 05
Conduct weekly summary spot-checks
To ensure the 'Lipstick' (the summary) is actually useful, managers must perform weekly quality checks on the automated notes. • Action: Every Friday, the Sales Manager selects 3 random summaries per rep from the #feed-sales-notes Slack channel. • Process: Compare the summary against the CRM 'Next Steps' field. Use the 'Otter Chat' feature to ask the recording: 'Did the prospect mention a budget?' if the summary is vague. • Feedback Loop: If summaries are missing key data (like 'Timeline'), update the Otter Custom Vocabulary or the rep's manual prompting instructions. • Owner: Sales Manager. • Time Estimate: 30 minutes weekly. • Pitfall: Treating this as an 'audit' rather than 'coaching.' The goal is to improve the AI's accuracy and the rep's follow-up speed. • Definition of Done: A weekly 'Note Quality Score' is shared in the leadership meeting, or a 'thumbs up' emoji is consistently applied to Slack summaries that meet the quality bar.
Next playbooks
Unfamiliar terms are defined in the AI and Revenue Dictionary. Related frameworks live in the framework library.