How to Use Fathom AI for Meeting Notes (Setup Guide)

To use Fathom for meeting notes, create an account at fathom.ai, connect the Google or Microsoft calendar you actually meet from, and let Fathom join your scheduled calls. Per Fathom’s own quick start documentation (checked 2026-08-04), it supports Zoom, Google Meet, and Microsoft Teams, and the desktop app is recommended for full functionality, particularly when you are not the meeting host. After the call, Fathom’s overview page states you get a transcript, an AI summary, and action items. Two setup conditions catch people out before any of that happens, and they are covered first.

What Fathom does, and who it fits

Fathom is a bot-based meeting assistant. It joins your scheduled video calls, records and transcribes them, and produces a summary with action items afterward. Fathom’s overview page also describes live summaries that update while you talk and a private scratchpad for your own notes and reminders.

It suits people whose meetings are scheduled, virtual, and run through one of the three supported platforms. If most of your conversations happen in a room with no video link, a bot-based tool cannot capture them at all, and a different approach applies. Our guide to capturing AI notes for in-person meetings covers that case. If you have not settled on a tool yet, the hub piece on how to choose an AI meeting note taker walks through the criteria before you commit to any one product.

Before you sign up: the two conditions that trip people

Most tutorials skip straight to “connect your calendar.” Two documented conditions sit in front of that, and both tend to surprise solo users.

A consumer email account needs a meeting on the books. Fathom’s quick start states that consumer email users need at least one meeting scheduled within seven days to complete signup. If you are trying Fathom on a personal Gmail address on a quiet week, signup will not complete, and the reason is not obvious from the error. Put a real meeting on the calendar first, or sign up with a work domain.

The desktop app matters more than it looks. Fathom’s documentation recommends the desktop app for full functionality, and specifically calls out the case where you are not the meeting host. That is the normal situation for anyone joining a client’s or a vendor’s call. If you plan to rely on Fathom in meetings you did not schedule, install the desktop app during setup rather than discovering the gap mid-call.

Step 1: Create the account and connect a calendar

Sign up at fathom.ai, then connect your Google or Microsoft calendar. Fathom’s documentation frames this as the step that lets it automatically join your meetings and handle the notetaking, so the calendar connection is not optional housekeeping. It is the mechanism.

Connect the calendar your meetings actually live on. If you keep a personal calendar and a work calendar, and your client calls sit on the work one, connecting the personal account produces a tool that quietly never joins anything.

Step 2: Decide how Fathom joins

Fathom’s quick start emphasizes turning on automatic recording for all meetings, framed as never having to remember to hit record. That is the low-friction default and it is the right starting point for most people.

It is worth pausing on it anyway. Automatic recording means Fathom joins everything on the connected calendar, including the one-to-one where a colleague tells you something in confidence, and the call where a client has not been asked. If any of your recurring meetings are sensitive, set the scope deliberately rather than accepting the blanket default and correcting later. The cost of getting this wrong is social, not technical, and it lands on the other person.

Step 3: Your first call, and what to do during it

Let the tool join and then leave it alone. The instinct to watch the transcript scroll defeats the point, which is that you stay in the conversation.

Two in-call features are worth knowing. Fathom’s overview describes live summaries that update as you talk, useful if you join late or lose the thread. It also describes a private scratchpad for notes, ideas, and reminders, with the ability to tag teammates. The scratchpad is the place for your own judgments, the things you would not want in a shared record, such as a read on how a negotiation is going.

One habit is worth building from the first call: say out loud that the meeting is being recorded, before it starts. The bot is visible in the participant list, so people will notice regardless, and hearing it from you is the difference between a normal meeting and an awkward one. Recording rules also vary by location, so check the ones that apply where you are. This is etiquette, not legal advice.

Step 4: What arrives afterward, and what to check

Fathom’s overview page states that a full recap arrives after the call, including the transcript, an AI summary, and action items, and that it syncs meeting insights with the tools a team already uses.

Read the first one end to end, even though the whole point is not having to. You are checking three things:

• Did it hear everyone? Distant speakers, heavy accents, and people talking over each other all degrade the transcript. If the output is rough, the cause is usually the audio rather than the tool, and why your AI meeting transcript is inaccurate covers the specific fixes.
• Did the summary keep the decision? Summaries reliably capture what was discussed and less reliably capture what was decided. If a decision is missing, fix it while you still remember it.
• Are the action items real? Generated action items tend to over-collect. Something said as a passing maybe becomes a task with your name on it. Delete the ones that were never commitments, because a task list nobody trusts gets ignored entirely.

Treat the output as a strong first draft. Two minutes of correction on the day is worth more than a perfect-looking record nobody checked.

Where Fathom is the wrong pick

Fathom is a poor fit in three situations, and it is worth naming them plainly.

If your meetings are in person, it has nothing to join. If a visible bot in the participant list is a problem for your client relationships, a tool that captures device audio without appearing as an attendee fits better, and the trade-offs of that choice are covered in our guide to bot in the call versus bot-free capture. And if your meetings run on a platform outside Zoom, Google Meet, and Microsoft Teams, check current support before you build a habit on it.

Plan limits, supported platforms, and feature names in this category change often. Confirm the current details on Fathom’s own site before you rely on any specific one.

FAQ

Does Fathom join my meeting as a visible bot?
Yes. Fathom is bot-based, so it appears as a participant in the call. Everyone in the meeting can see it in the attendee list. Our guide on what everyone else sees when your notetaker joins covers what that looks like from the other side.

Which platforms does Fathom support?
Per Fathom’s quick start documentation (checked 2026-08-04), Fathom supports Zoom, Google Meet, and Microsoft Teams. Confirm current support on Fathom’s site before relying on it for another platform.

Why will my Fathom signup not complete?
Fathom’s quick start states that consumer email accounts need at least one meeting scheduled within seven days to complete signup. If you are signing up on a personal email address with an empty calendar, schedule a meeting first.

Do I need the desktop app?
Fathom’s documentation recommends it for full functionality, especially when you are not the meeting host. If you regularly join calls that other people scheduled, install it during setup.

Does Fathom work for in-person meetings?
No. It is built around joining scheduled video calls, so a face-to-face meeting gives it nothing to join. For that, see our guide to capturing AI notes for in-person meetings.