Will an AI Notetaker Catch a Call That Was Never on Your Calendar?

The short answer, and what it leaves out

Yes. Every major AI notetaker can capture a call that never appeared on your calendar. Otter, Fireflies, Fathom and Granola each document a way to do it, and so do we. If that is the whole question, you can stop here.

The narrower version of the question is the one that decides whether your archive is any good. Will it catch the call on an ordinary Tuesday, when the conversation starts because somebody sent you a message and you clicked join without thinking about it? Read the four tools' own help centres on that and a pattern shows up that none of their landing pages mention. The automatic part of an AI notetaker is a calendar feature. Capture is not. Take the calendar event away and in every one of these products, ours included, something has to happen in the first minute of a call you did not know you were going to have.

What follows is what each product's documentation says, read in October 2026, with the costs and the failure modes that come out of it.

Every automatic setting is a calendar setting

Here is what each tool keys its automatic capture to, in its own words.

• Otter has five auto-join options and all five are defined over calendar events: meetings with a video link, meetings where you are the host, external meetings outside your domain, internal meetings inside it, and meetings you toggle on individually. The help centre answers the obvious follow-up without hedging. Asked whether you can create a new meeting in Otter, it says no, meetings have to be created in your calendar or in Zoom and synced across before Notetaker can join, and that for ad-hoc meetings you add Notetaker by hand.
• Fireflies documents three ways to invite its bot. Two are calendar routes, the auto-join settings and adding [email protected] to an invite. The third is a form on the dashboard where you paste a meeting link yourself.
• Fathom offers four auto-capture levels: All Meetings, External Meetings, Internal Meetings and No Meetings. The first three are each described in terms of scheduled meetings. Anything off the calendar sits in a separate category the documentation names impromptu meetings, with its own settings.
• Granola sends a notification one minute before a calendar event, with a documented limit worth knowing: calendar notifications only appear for events with two or more attendees. Its transcription page is blunt about the rest, saying Granola does not automatically transcribe meetings without you having clicked into a note.
• Driffle has nothing automatic at all, and says so as the first thing on our privacy page. Driffle never auto-joins meetings, auto-records, or runs in the background.

Detection is a prompt, not capture

Two of these tools have added detection that does not depend on the calendar, and it is worth being precise about what detection buys you.

Otter's desktop app can watch for a live meeting and offer to record it, and lists Slack huddles, dialers, browser calls, Microsoft Teams and WhatsApp among the things it recognises. Granola does the same job by noticing that your microphone is in use, and labels the prompt by platform: Huddle detected for Slack, Call detected for FaceTime or WhatsApp, Meeting detected for everything else. Fireflies sends a desktop notification when it detects an upcoming or active meeting and offers two buttons, one to capture device audio and one to send the bot.

All three of those are prompts. Something still has to be clicked, by you, while the conversation is already running. That is the honest shape of the answer to the question in the title. The off-calendar call is reachable in every one of these products and automatic in none of them.

What it costs to send a bot into a call already in progress

If your tool's off-calendar route is a bot, the cost is measurable and the vendors publish it.

• Fireflies tells you to expect two to three minutes between clicking Start Capturing and the notetaker arriving. On a twelve minute call that is a quarter of the conversation, and usually the quarter where somebody says what the call is really about.
• Otter warns that a pasted Zoom link has to carry the embedded password or the bot cannot join at all, and that arrival may take a few minutes.
• Either way the host may have to admit the bot, and on Google Meet that has turned into a small obstacle course. A Google security update can file a notetaker under participants with potential risks, where the Admit button is hidden behind a three dot menu. Fireflies and Fathom both document the workaround, which tells you how many people hit it.
• Fathom's help centre still documents a constraint of its own, on a page last edited in June 2025: Fathom can only record a Zoom, Teams or Meet call if you are also present on it, because recording is tied to your user presence, and it exits when the meeting ends.

Count the steps on the call that matters most

Add it up for an unscheduled external call where you are not the host. You notice the call matters. You find the link. You open a dashboard, paste it, pick a language, click. Then you wait two or three minutes, and then somebody you do not manage has to find a hidden menu item while the conversation carries on without them.

Every one of those steps is a place where the record does not get made. None of them are bugs. They are what it looks like to bolt an off-calendar path onto a system designed around calendar invitations.

The off-calendar route is a thinner record, and the docs say so

There is a second effect that is easier to miss, and it matters more over a year than the lost first three minutes.

In the tools where device capture is the fallback rather than the main path, the fallback produces a different artifact. Fireflies publishes a side by side table comparing bot capture with system audio capture. On system audio you do not get speaker labels, you get Speaker 1 and Speaker 2. Audio and video files are not saved. Sales Assist does not run. The same three points are repeated in prose further down the page, so this is not a footnote somebody forgot to update.

Fathom says a version of the same thing about Slack huddles. Capture works, video depends on whatever Slack happens to expose, and the advice is that anyone who needs reliable video should hold the conversation on a bot supported platform instead.

Now put that next to which conversations are the ones nobody books. The thirty minute status meeting with eight attendees is on the calendar. The call where a customer explains why they are leaving usually is not. Neither is the huddle where two engineers settle an architecture question in nine minutes, or the conversation that happens because a cofounder picked up the phone. The records that matter most route to the path with no speaker names and no retained audio. Nobody designed it that way. It falls out of which route is the main one and which is the backup.

The worse failure is a note filed under the wrong meeting

A missing note is at least obvious. You look for it, it is not there, you rebuild it from memory and you are annoyed for ten minutes. A misfiled note is worse, because nothing tells you to go looking.

Granola documents a rule that produces exactly this. Start a call within fifteen minutes of a scheduled meeting and Granola assumes the call is related to that calendar event, and shows the event's name on the notification. For most people most of the time that is helpful. For somebody running back-to-back calls it is a trap. The five minute conversation straight after a product review, which is where the real decision gets made because the review ran out of time, lands under the product review's name. Six weeks later you search for the decision and you find a note about the review.

Fathom has a cleaner version of the same problem, stated in its own troubleshooting. If you had auto-record switched on and your Slack huddle was not captured, that is expected behaviour, because auto-record does not apply to huddles. There is a separate toggle for it, and it stays off until somebody finds it. Fathom also notes that its bot free experience is still rolling out, so the huddle options may not be there yet on your account.

Both of these are defensible engineering decisions. Both of them mean the state of your archive depends on a setting you have probably never opened.

What Driffle does here, and what we will not do

Driffle has no bot. Capture is audio from your own machine, which means there is no calendar dependency in the capture path and no lesser fallback to land in, because device capture is the only path there is. A call that exists nowhere except in your speakers is the normal case rather than the exception.

The calendar still does a job, a different one. If you connect Google Calendar, Driffle asks for read only access to event titles, times, descriptions, locations and attendee names, and uses it to know which meeting you are in and to prepare briefs. It does not write to your calendar and it is not what starts a recording. Labelling and triggering are separate things here, and only the labelling needs a calendar event to exist.

Here is the part that is not a sales pitch. Driffle does not solve the press. Our privacy page leads with it: nothing happens automatically, Driffle never auto-joins meetings, auto-records, or runs in the background, you hit a button and it works, you close it and it stops. That is a deliberate choice about a tool that sees a lot of your work, and it has a real cost on exactly the question this article is about. An unscheduled call needs you to start it, the same as it does in Granola, and the same as it does in Otter and Fathom unless you have gone and switched their detection on.

The other limits, so nobody meets them at a bad moment. Driffle runs on Apple Silicon Macs on macOS 14.4 or later, as a direct download rather than from the Mac App Store. Intel Mac, Windows and Linux have a request form, not a build. Transcription and the AI run inside our own AWS account, so Driffle is not an offline or on-device product and a call captured with no connection is not something we promise. Audio is discarded within about a minute and the text is what we keep. The Google Calendar connection is still going through Google's verification review, so you may see an unverified app screen when you connect it. Our pricing is still in draft, so there is nothing here to quote.

Four tests worth running in a trial week

None of these need the vendor's cooperation and all four take minutes.

• Start a Slack huddle with one colleague, say three sentences, and time how long it takes before a record exists. Count every click, including the ones inside a notification you had to notice first.
• Take a five minute call that starts right after a scheduled meeting ends. Then look at what the record is called and which meeting it is attached to. This is the test almost nobody runs and the one most likely to change your mind.
• Capture the same kind of conversation twice, once through the tool's main route and once through its off-calendar route, then compare the two records field by field. Speaker names, action items, whether the audio survived. If the second one is worse, you now know what your unplanned calls will look like for the next year.
• A week later, search for something from the off-calendar record using the words you would plausibly reach for then rather than the words you remember writing. If it does not come back alongside everything else, capture worked and memory did not.

The question underneath the question

What people type is whether the tool can record an unplanned call. What decides whether a work archive is worth anything a year later is whether the unplanned calls are in it at the same quality as the planned ones. Those two come apart quickly in most tools, and the gap is documented in public, by the vendors themselves, on pages their own customers rarely read.

If you want capture that does not begin with a calendar invitation, Driffle is a Mac download at driffle.ai/download.