AI note-takers without a bot: how they work and which to use

An AI note-taker without a bot captures the conversation without adding a participant to the meeting. It does this in one of three ways: a desktop app that listens to your computer's audio, a browser extension that captures a meeting running in the browser, or the meeting platform's own AI feature. The candidate sees no extra name in the call, but you still need to tell them they are being recorded.

This page explains how each method works, why bots cause problems in interviews in particular, and how the main bot-free tools compare, with vendor facts checked as of September 2026.

Three ways to take notes without a bot

There is a fourth, narrower case: an app that runs inside one meeting client. BrightHire, for example, says its assistant opens inside Zoom without a bot joining each call, while on Google Meet it joins as a participant (BrightHire, as of September 2026).

Why a bot is a problem in an interview

In an internal team meeting, an extra participant called "Notetaker" is a minor distraction. In an interview, the dynamics are different:

• The candidate cannot easily object. They want the job. An unexplained participant makes some candidates guarded, and the guarded version of a candidate is the one you then score.
• It looks like someone else is listening. Bots often show a vendor name, not yours. Candidates reasonably ask who that is, and the first minutes go on explaining it.
• Meeting platforms are now filtering bots. Microsoft's admin documentation for Teams says Teams detects external bots and, by default, holds them in the lobby until an organizer admits them, with a reminder about the risk. If a hiring manager or client hosts the meeting, your bot may sit in a lobby nobody checks.
• Other companies' policies apply. When a client or partner hosts, their admin settings decide whether your bot is admitted, not yours.

None of this means bot-based tools are wrong. Many work well where the recruiter hosts every call and candidates are told in advance. It means you should decide deliberately rather than by default.

Bot-free note-takers compared

As published by each vendor, as of September 2026. This is not an exhaustive list; several general meeting tools now offer a bot-free mode.

Sources: Otter desktop and Otter pricing; Fireflies help center and Fireflies pricing post; Granola and Granola pricing; CoRecruit and CoRecruit pricing; our pricing.

Two things stand out. First, the general tools are inexpensive and good at transcripts, but they are not built around interview output such as scorecards or client submittals, so check what you get after the call. Second, Fireflies' desktop app shows that bot-free does not have to mean silent: its help center describes an optional meeting-chat message, a spoken audio notice and an on-camera watermark, all on by default.

Built-in AI notes in Zoom, Meet and Teams

If your company already pays for a meeting platform, its own AI feature may be enough for some interviews. All three show participants that notes are being taken, which helps with notice.

• Zoom: Meeting Summary with AI Companion is available to licensed users on paid Zoom Workplace plans, and only the host or co-host can start it (Zoom support).
• Google Meet: "Take notes for me" needs an eligible Workspace edition or Google AI plan, and Meet tells all participants when notes are being taken (Google Meet Help).
• Microsoft Teams: intelligent recap requires a Teams Premium license or one of Microsoft's AI add-on licenses, and transcription must be turned on (Microsoft Learn). Everyone sees a notification when transcription starts (Microsoft Support).

The limits for interviewing are consistent across all three:

• The notes live in the host's account. If the candidate or a client sends the link, you usually cannot start them.
• They produce meeting summaries, not a scorecard against your competencies or a submittal.
• They do not cover a phone screen on your mobile.

For a Teams-specific walkthrough, including recording expiry and admin policies, see how to record a Teams interview without a bot.

The trade-offs of going bot-free

Bot-free capture solves the participant problem and introduces a few of its own. Know them before you switch.

• You have to be on the call. A bot can attend a meeting you miss. A desktop app only captures what your computer hears.
• Your audio setup matters. Laptop speakers feeding back into the microphone produce echo and muddled speaker labels. Headphones fix most of it.
• Operating system permissions. On macOS in particular, an app needs permission to capture system audio and the microphone. Grant it before a real interview, not during one.
• Nothing announces you. A bot's presence is a crude form of notice. Without it, the notice is entirely your job.
• Where the data goes still varies. Bot-free describes how audio is captured, not where transcripts are stored. Read each vendor's security page. For ours, transcripts and notes stay on your computer and audio is sent in short chunks for transcription and not retained (security).

Consent still applies without a bot

Recording law cares whether a conversation is recorded, not whether a bot was visible. In places that require every party's consent, a note-taker nobody mentions is the setup most likely to cause a problem. The fix takes fifteen seconds at the start of the call:

Before we start: I use an AI note-taker so I can listen instead of typing.
It transcribes this call and I use the notes for your application only.
Is that OK with you? If you'd rather I didn't, I'll turn it off and take
notes by hand. It won't affect your application.

Add a line to the calendar invite as well, so the question is not a surprise. If the candidate says no, pause capture before continuing and note that they declined. Our consent script has longer and stricter versions, and the consent guide lists the states where everyone must agree.

Test your setup before a real interview

Run this ten-minute check with a colleague once, on each platform you use:

1. Install the app and grant microphone and system audio permissions.
2. Join a test call on Zoom, Teams or Meet with headphones on. Confirm no new participant appears.
3. Have your colleague say three specific facts: a number, a company name and a date. Check the transcript gets all three right.
4. Talk over each other for a few seconds. Check the transcript still labels who said what.
5. Try the pause control and confirm nothing is captured while paused.
6. If you screen by phone, repeat with a softphone or a phone routed through the computer.
7. Join a meeting someone else hosts and confirm capture still works.
8. Find where the transcript is stored and how to delete one.

Questions to ask a bot-free vendor

"No bot" is a capture method, not a privacy policy. These questions separate tools that look alike on a feature page:

• Is audio stored, and for how long? Some tools keep no audio file at all; Fireflies, for example, says its bot-free desktop recording saves no audio or video. Others keep recordings in the cloud.
• Where do transcripts live? On your computer, in the vendor's cloud, or in your meeting platform's storage. Each has a different deletion process when a candidate asks.
• Does it capture both sides on every platform you use? Ask for the list the vendor supports, then test the ones that are missing from it.
• What notice does it give, if any? A chat message, an audio line, or nothing. Decide whether you want the tool to announce itself or to do it yourself.
• What happens after the call? A transcript, a summary, a scorecard, or a submittal. The minutes you save come from this step, not from the capture.

Which option fits your situation