Bot or no bot: which meeting recorder fits your calls
If you need meetings you do not attend, use a bot. If you need the audio to stay on your own machine, record from the machine. The rest is trade-offs.
There are two ways to record a call. A bot joins the meeting as an extra participant and records from inside it, or an app on your own computer records the audio that machine is already playing. If you need notes from meetings you are not on, you need a bot. If you need the audio to stay on your own machine, you need an AI notetaker without a bot.
What a bot gets you
You connect the tool to your calendar, and when the meeting starts the bot joins through the link, appears in the attendee list and records from inside. As a participant it gets what the platform gives everyone, often a separate stream per speaker and the platform’s list of who is talking, so speaker labels tend to be clean.
It does not depend on your laptop. A bot can attend a meeting you skipped, left early, or that runs while you are asleep in another timezone.
Everyone can see it. Read.ai’s help centre describes its bot as needing to be added by someone invited to the meeting, asking permission to join, and showing “a visual indication that Read has joined, either as a participant that the host can remove, or a Read logo in the meeting window”. Any participant can remove it by typing “opt out” in chat.
What recording from your Mac gets you
Nothing joins, so nothing appears in the participant list. The app records two sources: the call audio and your microphone.
On a Mac, Listenr uses a Core Audio process tap, which hears each app’s output before it reaches your speakers or headphones and keeps working when you switch output devices. That needs the Microphone and System Audio Recording permissions. Screen Recording is optional and only adds meeting detection by window title and a fallback audio path.
Because the audio never had to leave to be recorded, it does not have to leave to be transcribed. Check this in any tool you evaluate: being bot-free does not mean on-device. In Listenr, transcription defaults to Apple’s on-device engine and four of the five backends run on the Mac. The fifth sends audio to OpenAI. See which local model your Mac can run.
Who is speaking?
A bot gets speaker structure from the platform. A recorder on your machine gets one mixed call track, so it has to work out the speakers itself.
Listenr does that in two steps:
- Separate the voices. An on-device model (NVIDIA’s Nemotron diarization) splits the call audio by voice while the meeting records. When the meeting ends, each voice is labelled Speaker 1, Speaker 2 and so on. Your microphone is You.
- Name them where the meeting app shows names. In the Zoom desktop app, Listenr can read the participant list, mute states and active speaker through Accessibility (off by default). In Google Meet, the Listenr browser extension for Chrome, Brave, Edge, Arc and Safari reads the People panel and speaking tiles. Listenr names speakers in Microsoft Teams too. An optional pass with a local model can also pick up names people say aloud. Zoom in a browser and other apps stay at Speaker N unless that pass names someone.
When the evidence is unclear, the voice keeps its Speaker N label. A wrong name is harder to spot than a missing one. Listenr does not read the screen and stores no voice profiles across meetings. Otter, by comparison, keeps speaker profiles that recognise the same voice in later recordings.
Bot-free is now common
As of October 2026, Granola, Fathom, Otter, tl;dv, Fireflies, Notion, Circleback, Krisp, Read.ai and Wispr Flow’s Notetaker all record from the device, and several also offer a bot:
- Otter’s desktop app offers recording without the Notetaker joining, alongside its bot.
- Fireflies and tl;dv record from system audio.
- Circleback’s free tier covers a bot or its bot-free desktop app.
- Notion’s desktop app captures system audio and your microphone.
- Fathom’s bot-free mode is a beta on Mac.
- Krisp offers device recording and a bot.
- Read.ai’s desktop app records “without needing a bot”.
- Wispr Flow’s Notetaker (Mac only) records from the device and transcribes on Wispr’s US servers.
Zoom, Teams and Google Meet have note-taking inside the client, so no bot is needed there either.
Reading names from the meeting app is not unique to Listenr. Granola’s speaker tags cover Google Meet, Zoom and Microsoft Teams on macOS and Windows, using Chrome’s accessibility data or its Chrome extension for Meet.
So the questions that separate these tools are where the audio is transcribed, who chooses the model that writes the notes, and what you can do with the notes afterwards. Ten products are scored on those on the requirements page, and individual comparisons are under /compare/.
What recording from your Mac costs
- It cannot record a meeting you do not attend. Fathom states the same limit for its own version.
- Nobody else gets a banner. There is no bot in the list and no announcement.
- Consent is on you. Recording rules differ by country and by state, and some places require everyone’s consent.
- Names depend on the app. Zoom desktop, Google Meet and Microsoft Teams can be named. Zoom in a browser and other apps stay Speaker N. The transcript itself is unaffected.
Choosing
Use a bot if coverage matters most: meetings you skip, meetings across timezones, meetings recorded whether or not your laptop is open. Use a platform assistant if your company lives in one platform and an administrator will turn it on. Teams intelligent recap needs Teams Premium or a Copilot licence, and Google Meet’s note-taking handles one of eight languages at a time.
Record from your own Mac if the recording and transcript should stay there. It is the only setup where a meeting can be recorded, transcribed and written up without leaving the device, and it leaves telling people to you. What each choice sends where is in what actually leaves your Mac, and plans are on the pricing page.