Sales representatives and Customer Success Managers (CSMs) routinely spend between thirty and sixty minutes each day manually typing call notes, formatting action items, and copy-pasting updates across CRM records. When meeting notes remain unstructured or trapped in individual notebooks, pipeline reporting degrades, deal handoffs falter, and customer context is lost.
Fathom AI Notetaker eliminates this administrative overhead by recording, transcribing, and converting customer conversations into structured, framework-aligned summaries. Within seconds of a call ending, Fathom pushes meeting notes, action items, and mapped field updates directly into HubSpot and Salesforce. Revenue and customer success teams use this workflow to enforce CRM hygiene, streamline sales-to-CS handoffs, and keep deals moving without manual data entry.
1. How Fathom Generates Structured Meeting Summaries
Unlike generic transcription bots that dump unformatted text into a document, Fathom organizes conversational data using structured summary templates, automated action item extraction, and interactive query tools.
[ Video Meeting: Zoom / Google Meet / MS Teams ]
│
▼
[ Fathom AI Processing Engine ]
│
┌───────────────────┼───────────────────┐
▼ ▼ ▼
[ Methodology [ Action Items & [ "Ask Fathom" &
Templates: Next Steps: Context-Rich
BANT / Sandler / Task Assignment Follow-Up Emails ]
Custom CS ] │ │
│ └─────────┬─────────┘
▼ ▼
┌────────────────────────────────────────────────────────┐
│ CRM Synchronization │
│ │
│ HubSpot: Salesforce: │
│ • Meeting Activity Timeline • Logged Task │
│ • Open Action Items as Tasks • Open Tasks │
│ • Deal Property Field Mapping • Opportunity Field │
│ • Embedded Fathom Card Mapping (H3/H4) │
└────────────────────────────────────────────────────────┘
Pre-Built Frameworks and Custom Summary Templates
Fathom includes more than 15 expert meeting templates based on recognized sales and account management methodologies, such as BANT (Budget, Authority, Need, Timing) and Sandler.
For teams with specialized discovery or onboarding processes, Fathom allows organizations on Business and Enterprise plans to build custom summary templates. Administrators configure prompt instructions to enforce specific heading structures:
- Discovery Calls: Sections such as
### Current Pain Points,### Technical Stack,### Decision Timeline, and### Budget Range. - Customer Success Kickoffs: Sections covering
### Agreed Success Metrics,### Key Stakeholders,### Integration Dependencies, and### Target Launch Date. - Quarterly Business Reviews (QBRs): Sections detailing
### Value Delivered,### Product Feedback & Feature Requests,### Churn Risks, and### Expansion Opportunities.
Formatting sections with H3 (###) or H4 (####) headers is critical: Fathom uses these exact header tiers to power field-level CRM synchronization.
Automated Action Items and Post-Call Follow-ups
During the call, Fathom detects commitments made by both reps and prospects, automatically generating a standalone list of action items. Reps can review, edit, or append tasks immediately after the session.
Fathom also drafts contextual follow-up emails instantly. Sellers and CSMs can copy the recap or ask Fathom to tailor the tone before sending it to clients, cutting the post-call wrap-up cycle from 20 minutes down to two minutes.
In-Call Bookmarking and "Ask Fathom" Intelligence
- One-Click Highlights: During critical moments—such as a prospect raising a pricing objection or detailing a workflow blocker—users click a button to bookmark the timestamp. Fathom generates a shareable video clip linked directly to the transcript.
- Ask Fathom: A conversational AI assistant available inside every call. Reps and managers can query the conversation using natural language (e.g., "What were the prospect's primary concerns regarding API security?" or "What did the client state about their renewal timeline?") to extract exact quotes without scrubbing through 45 minutes of audio.
2. Syncing Notes and Data to HubSpot CRM
Fathom's native HubSpot integration was awarded HubSpot's Most Used App of the Year, with over 20,000 installs. It connects customer-facing conversations directly to Contacts, Companies, and Deals.
Setup and Authentication
- In your Fathom workspace, navigate to Settings > Integrations.
- Locate HubSpot and click Connect.
- Authenticate with HubSpot credentials using OAuth (HubSpot Super Admin permissions are required for the initial authorization).
- Select the target HubSpot account. Free and Team plans support up to three connections per user; Business and Enterprise plans allow unlimited account connections.
Record Matching and Data Placement
- Primary Email Matching: Fathom identifies attendees using the primary email address on the calendar invitation and matches it against HubSpot Contact records. External contacts are matched automatically; internal domain-only meetings are excluded from CRM logging.
- Meeting Events: Once a call concludes, Fathom writes the full AI summary, key takeaways, and a shareable recording link directly to the Meeting event under the Contact's Activity timeline and any associated Deals.
- Task Creation: Action items captured by Fathom can sync as native HubSpot Tasks assigned to the meeting owner.
- Embedded HubSpot Cards: Teams can add the Fathom Card to HubSpot Contact, Company, or Deal layouts. The card displays the five most recent calls with direct links to call recordings, AI summaries, and timestamped highlights, allowing account executives and managers to inspect call context without leaving HubSpot.
Deal-Level Field Sync (Business Plan)
On Business and Enterprise tiers, Fathom enables field-level property mapping:
- Team administrators enable HubSpot at the organizational level under Organization Settings > Integrations.
- Open any deal in Fathom's Deals view.
- Hover over an
H3orH4heading in the deal summary (e.g.,### Pain Pointsor### Next Steps) and select Map to HubSpot. - Choose the corresponding HubSpot deal property.
When future calls occur, Fathom automatically overwrites the selected HubSpot property with the freshest AI summary segment, keeping pipeline fields accurate for forecasting reports.
3. Syncing Notes and Data to Salesforce CRM
Fathom's Salesforce integration is built for enterprise pipeline accuracy, eliminating manual Task logging and ensuring that Opportunity stages match real buyer conversations.
Salesforce Prerequisites and OAuth Permissions
Salesforce orgs must meet standard API requirements:
- Edition Support: Salesforce Enterprise, Performance, Unlimited, or Developer editions with the REST API enabled.
- User Permissions: The connecting user must have read and write permissions on
Contact,Account,Opportunity, andTaskobjects, along with theAPI Enabledadministrative permission. - OAuth Scopes: Fathom requests four standard OAuth 2.0 scopes:
api,id,custom_permissions, andrefresh_token. - Territory Management: If Opportunities use Territory Management rules, the connecting Salesforce user must have access to the assigned territories.
The Salesforce Cascade Matching Engine
When a call ends, Fathom processes each external attendee through a deterministic three-step hierarchy:
[ External Attendee Primary Email ]
│
▼
1. Match Contact record in Salesforce
(Note: Leads are not matched; only Contacts are evaluated)
│
▼
2. Traverse Contact.AccountId to link the Account
│
▼
3. Traverse OpportunityContactRole to link all OPEN Opportunities
(Closed-Won and Closed-Lost Opportunities are strictly excluded)
If an external attendee does not exist as a Salesforce Contact, Fathom does not create orphan tasks. Similarly, if a Contact is not linked to an open Opportunity via OpportunityContactRole, deal-level intelligence will not attach to that Opportunity.
What Fathom Writes to Salesforce
- Logged Calls as Tasks: The meeting summary and recording link are written as a completed
Task(logged call) on the matched Contact, Account, and open Opportunity activity timelines. On orgs utilizing the modern Notes experience, notes also link to theNotes & Attachmentslist. - Task Attribution: While the task is created via Fathom's API service connection, it is assigned directly to the meeting host. Activity-by-rep dashboards and sales performance reports in Salesforce reflect rep activity accurately.
- Action Items: When the
Create Tasksoption is toggled on, Fathom generates a separate open Task for each action item. If open Opportunities exist, tasks link to both the Contact and the Opportunity; otherwise, they attach to the Contact.
Field-Level Mapping on Salesforce Opportunities
On the Business plan, administrators can map specific sections of Fathom's AI summary directly into Salesforce Opportunity fields:
- Supported Field Types:
Long Text Area(textarea) fields supporting up to 32,000 characters (auto-truncated if exceeded), as well as single-lineTextfields. - Template Heading Rule: Mappable sections must use
H3(###) orH4(####) headings. Unstructured paragraphs orH1/H2tags cannot be selected. - Configuration: An administrator opens a deal in Fathom, hovers over the target heading (e.g.,
### Competitor Mentionsor### Decision Criteria), clicks Map to Salesforce, and selects the Opportunity field. - Refresh Behavior: When subsequent meetings take place on that deal, Fathom refreshes the mapped Opportunity fields with the updated section contents, overwriting outdated information with real-time customer data.
4. Workflows for Sales Teams
Sales organizations use Fathom to shorten deal cycles, maintain pipeline integrity, and improve coaching.
| Sales Workflow | How Fathom Is Used | CRM Outcome |
|---|---|---|
| Discovery & Qualification | Reps conduct discovery without typing notes. Fathom structures notes using BANT/MEDDPICC templates. | Key pain points, budgets, and timelines sync immediately to HubSpot Deal or Salesforce Opportunity fields. |
| Deal Velocity & Handoffs | When an SDR qualifies a prospect, the AE accesses the full call recording, AI summary, and highlighted clips. | Context stays attached to the CRM record; AEs avoid asking prospects repeat questions. |
| Follow-Up Execution | Reps review Fathom's AI-generated action items and email drafts within two minutes of call completion. | CRM tasks are assigned and scheduled; follow-up emails reach prospects while the conversation is fresh. |
| Coaching & Pipeline Reviews | Sales leaders review "Deal View" to inspect chronological summaries across multiple calls on high-value deals. | Forecast meetings rely on verified conversational data rather than rep optimism. |
| Competitor & Objection Tracking | Teams set Trackers for competitor names and pricing objections, routing instant alerts to Slack. | Leadership identifies market trends and provides real-time objection coaching. |
5. Workflows for Customer Success Teams
Customer Success teams operate in high-retention environments where missing a handoff detail or risk signal directly impacts renewal rates.
| CS Workflow | How Fathom Is Used | CRM Outcome |
|---|---|---|
| Sales-to-CS Handoff | Incoming CSMs review the deal's Fathom history and Deal View rather than scheduling internal debriefs. | CSMs join the kickoff call with full awareness of pre-sales promises, technical constraints, and scope. |
| Onboarding & Kickoff | CSMs capture technical architecture, milestones, and client responsibilities using onboarding summary templates. | Action items sync to HubSpot or Salesforce as implementation tasks; next steps are logged on Account records. |
| QBRs & Health Tracking | CSMs use custom QBR templates to document business outcomes, feature requests, and workflow bottlenecks. | Value delivered and client feedback are documented directly on Account/Company records. |
| Risk Detection & Churn Prevention | Fathom keyword trackers flag phrases like "budget cut", "re-evaluating", or competitor mentions. | Account teams receive immediate warnings to intervene before an upcoming renewal is jeopardized. |
| Renewal & Expansion Preparation | Prior to renewal discussions, CSMs query "Ask Fathom" ("What ROI figures did the client cite in June?") to pull proof points. | Expansion opportunities in the CRM are updated with concrete client-validated data. |
6. Implementation Checklist & Best Practices
To ensure a seamless rollout across sales and customer success departments, adhere to these architectural recommendations:
- Verify Calendar Cleanliness: Fathom syncs scheduled meetings on the user's primary connected calendar. Sub-calendars, secondary calendars, and unscheduled impromptu calls without a calendar invite will not auto-sync to CRM records.
- Standardize CRM Contact Records: Ensure external attendees are logged as Contacts in Salesforce or HubSpot using their primary email address. In Salesforce, verify that Contacts participating in sales cycles are explicitly linked to open Opportunities via
OpportunityContactRole. - Audit Salesforce Validation Rules: Custom validation rules on
TaskorOpportunityobjects requiring specific picklist values or mandatory custom fields can block automated API writes. Work with your Salesforce administrator to ensure integration permissions bypass non-essential UI validation rules. - Enforce Markdown Heading Discipline: If planning to use field-level property sync on the Business plan, mandate the use of
H3(###) headings in custom templates for every field you intend to sync into HubSpot or Salesforce. - Select the Proper Plan Tier: While individual reps can test basic note-taking on the Free plan, team-wide CRM logging across more than three users, automated field-level mapping, and centralized Deal View require the Business plan ($25/user/month billed annually, or $34/user/month billed monthly, 2 user minimum).
References
- HubSpot Integration: Auto-Log Calls to CRM – Fathom
- Salesforce Integration: Sync call summaries & highlights to matching Contacts, Accounts, and open Opportunities – Fathom
- Fathom + Salesforce Integration Admin Guide: Setup and Sync
- HubSpot Integration – Fathom Help Center
- Customer success that actually scales – Fathom
- Meet your brilliant AI meeting copilot – Fathom
- Pricing to supercharge every meeting – Fathom