Can an AI Notetaker Attend a Meeting for You?

Some can, and the reason the rest cannot is the useful part

Otter can. Its own help page says that if you cannot attend a meeting, you can send its Notetaker anyway and catch up from the notes afterwards. Fireflies can too. Its auto-join setting offers four choices: every calendar meeting with a conferencing link, meetings you own, meetings with teammates, or only meetings where you invite it. None of the four asks whether you will be there.

Fathom, which also uses a bot, cannot. Its help centre says it records a Zoom, Teams or Google Meet call only when you are on the call as well, because recording is linked to your presence, and says a solo mode is not available at the moment. Tools with no bot at all cannot either, and never will. Granola runs on your computer and listens to its system audio and microphone. Driffle works the same way. If your computer is not in the call, there is nothing for either of them to hear.

So the question that decides the answer is simple: is capture tied to your calendar, or to a person in the call? Ask that before you compare anything else, because it settles this question for every tool on your list.

Everything that has to go right while nobody is there

A bot sent on its own is a guest arriving at a door with nobody inside who expects it. Otter's troubleshooting page is a good list of what stops it. If the host has not started the meeting and guests cannot join before the host, the bot waits up to five minutes, tries four times, then leaves. If there is a waiting room and nobody admits it, it keeps trying for about twelve minutes. If the meeting requires people to sign in to the conferencing app, it cannot get in at all, because it joins as a guest and cannot sign in to your organisation's account. On Zoom, a host can also deny it permission to record.

When you are on the call, each of these takes ten seconds to fix. You message the host, you admit the bot, or you notice it never arrived and take your own notes. When you are not on the call, you find out from an error on a calendar event that is already over. The meeting you most wanted covered is gone, and so is anyone you could have asked to let the bot in.

Internal meetings at larger companies are the ones most likely to require sign-in or keep guests out. Those are often exactly the meetings a busy operator wants to skip and still know about.

It turns up wearing your name

Otter's bot appears in the participant list as "[Your Name]'s Notetaker (Otter.ai)", and Otter states that it cannot join without being visible. When you are in the call, that label reads as you taking notes. When you are not, the room sees a recorder with your name on it and nobody behind it to ask what it is for, who will read the output, or whether they can switch it off.

People adjust to that. A customer, a candidate, or a colleague from another team may say less with an absent person's recorder in the call, and the more careful version of the meeting is the one you then read about. That is a judgement, not a measurement, but it is worth weighing before you make it a habit. Recording consent rules also apply exactly as they would if you were there. The difference is that nobody in the call can ask on your behalf.

A record of a meeting is not attendance

What comes back is a transcript and a summary of a conversation you could not steer. The questions you would have asked were not asked. If a decision needed your view, it was either made without it or pushed to a follow-up you now have to attend anyway. A summary can tell you what was said. It cannot tell you what would have been said if you had been there, and that is usually why the meeting was on your calendar in the first place.

That gives a fair rule for when sending a bot is worth it. For meetings where you would only listen, such as an all-hands, a vendor demo you are tracking, or a webinar, a delegated recorder is a reasonable trade. For meetings where your view is an input, it is a poor substitute, and it can make missing the meeting feel handled when it is not.

What Driffle does instead, and what it cannot do

Driffle has no bot and never joins a meeting on its own. It captures your Mac's microphone and system audio while you are on the call, which means it cannot attend a meeting for you. If sending a recorder to meetings you skip is a core need, a calendar driven bot tool such as Otter or Fireflies fits that need better, and you should buy one of those.

What Driffle does is work on the meetings you do attend. Before your next meeting with the same people, it builds a prep view from what it heard on earlier calls: commitments carried over with their owner and due date, overdue ones flagged, open questions, and things worth bringing up. That memory only grows from calls it heard. Before a first meeting, the app says so in plain words: "Not much to prepare yet. After this call, Driffle will know the people, the topics and anything you owe each other, and the next prep will show them."

The same is true of every tool. A meeting you skip is a gap in your record, whether a bot covered it or not, because the bot's notes sit apart from the context you built in every call before it.

If you really cannot make it

Send your one question ahead, in writing, to someone who will be there, and ask them to reply with the answer the same day. That gets you the thing you would have said, which no recorder can do.

Ask whoever is capturing the meeting anyway to send you the notes. The organiser often records on the meeting platform, and you get the record without adding a recorder under your name.

If you do send a bot, tell the host first. Otter even has a setting that notifies the host a day ahead so they will admit it. A bot the host expected gets in far more often than one that surprises them.

Read the notes the same day and reply with any correction or objection while people still remember the conversation. An objection sent a week later reopens a decision; one sent the same afternoon is still part of it.

If you want a Mac notetaker for the meetings you do attend, with no bot in the call, Driffle is at driffle.ai/download.