Most people install a meeting recorder, run it once, and then forget it exists. Three weeks later their CRM is still empty, the action items from Tuesday’s call are buried in a Slack thread, and nobody remembers who agreed to send the pricing sheet. Fathom AI doesn’t fix that on its own. A workflow does.
What follows is the exact sequence I’d hand to a new hire: seven steps, roughly 40 minutes of setup, and a repeatable pattern you can run on every call after that. No theory, no feature tour.
Step 1: Understand What Fathom Is Actually Good At
Fathom AI is a meeting assistant that joins your Zoom, Google Meet, or Teams call, records it, transcribes it, and then produces an AI summary with highlights and action items. The free tier is unusually generous, which is a big part of why teams keep adopting it as their default. If you want the full breakdown of plans and limits, there’s a solid Fathom AI review covering why teams are ditching manual notes worth reading before you pick a tier.
The important thing to internalise early: Fathom is a capture and structuring tool, not a decision-maker. It will hand you a clean transcript. It will not tell your client that the contract clause they objected to is actually negotiable. You still have to do that part.
Step 2: Connect the Calendar Before You Touch Anything Else
Install the desktop app first, then connect your Google or Outlook calendar from inside it. The calendar connection is what lets Fathom auto-join meetings and, more usefully, match recordings to the right attendees and company.
- Install the desktop app (Mac or Windows), not just the browser extension.
- Sign in with the Google account that owns your work calendar, not a personal one.
- Grant calendar read access. Read-only is enough for scheduling.
- Connect your video tool of choice: Zoom, Google Meet, or Microsoft Teams.
One gotcha: if your company uses a shared calendar for external meetings, you’ll need the organiser’s account connected, not just yours. Otherwise Fathom won’t know the meeting exists.
Step 3: Set Recording Rules Now, Not Mid-Call
The default behaviour is to record everything with a meeting link attached. That’s fine for a 10-person startup and a disaster for anyone with an executive calendar.
Go into recording preferences and pick one of two modes: record everything, or ask before recording. If you’re in sales, support, or recruiting, take the ask-first option and set an automatic rule for meetings with external domains. Internal standups rarely need a transcript.
Then check your notification settings. Fathom announces itself in the meeting, and you want that announcement visible. Sneaky recording is how you lose a client in the first five minutes.
Step 4: Run One Throwaway Test Call
Book a 10-minute meeting with a colleague. Label it “Fathom test.” Talk for eight minutes about something with real structure to it, like a project update with three blockers and two deadlines.
Afterwards, open the recording and check three things:
- Is the transcript accurate on names? Fix the spelling errors in your contact list, because Fathom uses those to label speakers.
- Did it correctly identify who said what? Speaker attribution fails most often on speakerphone audio.
- Does the summary list the three blockers? If it only lists two, you now know how much you can trust the auto-summary on a real call.
That last point matters. Treat the AI summary as a first draft you edit, not a finished artifact you forward.
Step 5: Build a Highlight Habit During the Call
Here’s where most people leave value on the table. Fathom lets you mark moments during the meeting with a keyboard shortcut. Use it. Every time someone states a number, a deadline, or a decision, tap the shortcut.
Try this rule: if you’d write it on a sticky note on the way out the door, mark it. Pricing figures. Go-live dates. The sentence “we’d need legal to sign off on that.” Those marked moments become the backbone of your follow-up, and they’re flagged with a timestamp you can jump straight back to.
Step 6: Turn the Summary Into a Follow-Up Email
This is the step that pays for the tool. Open the recording, copy the action items, and write the email yourself in five sentences. Something like:
“Hi Priya — thanks for the time today. Quick recap: you need the SOC 2 report before your security review on the 14th, and we agreed I’d send the revised pricing by Friday. I’ve attached the report. The one open question is whether the annual discount applies to the two-year term, and I’ll confirm that with our finance team by Wednesday. Anything I’ve missed?”
Notice what’s missing: a wall of transcript. Nobody reads that. The point of an AI summary is to shrink the call into decisions and owners. If you want a comparable walkthrough of the same idea in a different tool, this guide on setting up Otter.ai so meetings become follow-up emails follows the same principle and is a useful cross-check on your template.
Timing beats polish
Send the recap within two hours. A slightly rough email at 11:15am outperforms a beautifully formatted one at 6pm, because the call is still fresh for them too. Fathom’s speed here is the real advantage — it’s not that the summary is magic, it’s that it removes the 30-minute gap where you’d otherwise be scrubbing through audio.
Step 7: Automate the Handoff
Once the manual loop works, wire up the destinations. In Fathom’s integrations you can push summaries and action items to Slack, HubSpot, Salesforce, Notion, or a shared folder. Do it in this order of value:
- CRM fields. Push the summary and next-step date into the deal record so it isn’t only living in someone’s inbox.
- A Slack channel. For internal calls, a single channel beats five people each writing their own notes.
- A project doc. Action items into the same Notion page every week, so the team sees a running list instead of a new doc per meeting.
The auto-push is what turns Fathom from an individual productivity toy into something a team actually relies on. It’s also the direction the whole category is heading — Fathom’s own product roadmap shifted meaningfully after Superhuman’s acquisition of the YC-backed notetaker, with the emphasis moving from passive transcription toward agents that take action on what was said.
A Worked Example: The 30-Minute Discovery Call
Say you’re selling project management software to a 60-person agency. Here’s how the steps stack up in real time.
Minutes 0–2. Fathom joins and announces itself. You mention the recording in your opening line so nobody is surprised.
Minutes 2–20. Discovery. The prospect mentions they lose roughly four hours a week per account manager chasing status updates. You tap the highlight shortcut. Twice.
Minutes 20–28. You agree on a pilot with eight account managers, starting the first week of next month, with a check-in scheduled for day 14.
Minute 30. Call ends. By 2:45pm you’ve sent the recap, created the deal in your CRM with the four-hour figure quoted in the notes, and dropped the 90-second audio clip of the prospect describing their status-update problem into the internal deal channel.
That clip is the underrated move. Sending a sales leader a 90-second recording of their own team describing the pain point does more than any deck. It also works for research: an aggregator of customer calls becomes a searchable record of what buyers actually say, which is the same instinct behind the current wave of agent-powered research tools turning raw conversations into structured insight.
Where Fathom Stops Working
Three honest limits. It struggles in rooms with heavy crosstalk or thick accents, so keep a live note-taker for anything high-stakes. It doesn’t understand context you never said out loud, so a summary of a call with no stated decisions will be thin. And it can’t replace judgement on what to send — if you don’t know whether the deal is won or lost, the transcript won’t tell you.
If your calls are mostly one-on-one and highly structured, Fathom’s free tier will cover you indefinitely. If you’re juggling a dozen tools and need the recorder to slot into a bigger stack, it’s worth comparing it side by side with the alternatives in this Fireflies.ai review of the best AI meeting assistants. Either way, the workflow above transfers. Connect the calendar, set the recording rules once, mark the moments that matter, and send the recap before lunch. The tool is the easy part; the habit is what compounds.