The bot that joins your calendar meetings doesn't check who's on the other end of them first.

Somebody in the call said "who's Fireflies?" or "did you invite a bot?" — and now the conversation is briefly about the bot instead of about the work. This happens because a notetaker connected to a calendar with autojoin turned on doesn't distinguish between an internal standup and a client's first call with your company; it dials into whatever is on the calendar, and it introduces itself by name when it does.

What actually happened

A calendar-connected notetaker watches every meeting on the calendar it's attached to and, when autojoin is on, sends itself in as a participant a few seconds after the meeting starts. It appears in the attendee list under its own name — fred@fireflies.ai is literally how Fireflies describes its own invite address — and depending on the platform, it may announce itself in the chat or with a short audio prompt. Everyone on the call sees a name they don't recognize show up mid-meeting, on a call where they were expecting only the people they already knew about.

This is a bigger problem the less internal the meeting is. Nobody minds a notetaker on a Tuesday standup. A sales call with a prospect meeting your company for the first time, a candidate's first interview, or a vendor's pricing call is a different room: the people in it did not agree to a third-party service recording and possibly redistributing the conversation, and a visible bot forces that conversation into the open in the worst possible moment — after it already joined.

Why nobody remembers inviting it

The person who gets asked "did you invite a bot?" often didn't, personally. Calendar autojoin is usually turned on once, at the account or workspace level, when someone signs the team up for a notetaker — and from then on, every meeting that lands on a connected calendar gets a visitor, regardless of who scheduled it or what it's about. A manager who approved the tool for internal syncs six months ago may have no idea it's now dialing into calls a new hire is running with outside vendors, because the setting was never scoped to specific meeting types in the first place — it was scoped to a calendar, and a calendar doesn't know the difference between a retro and a reference call.

This is also why the bot sometimes shows up on a call the person hosting it didn't expect at all. If the account is shared or the calendar sync is company-wide, one person's autojoin preference can add a visible guest to a meeting somebody else on the same domain organized, with neither of them having made a fresh decision about that particular call.

What it costs beyond the awkward two minutes

The immediate cost is small — a pause, an explanation, maybe a slightly stiffer tone for the rest of the call. The larger cost shows up afterward, when the other side remembers that a third-party tool had access to the conversation and starts asking what happens to the recording, who else can see it, and whether it was actually necessary. Some prospects and clients have a blanket rule against unfamiliar recording software on calls involving their own business, and a bot that joined without warning is the fastest way to trigger that rule after the fact rather than before, when it would have been a much smaller conversation.

None of this means the notetaker did anything wrong by its own logic — it did exactly what autojoin is supposed to do. The mismatch is between a setting built for convenience on routine internal meetings and a call where the other side never agreed to that convenience.

Which tools do this, and which don't

Fireflies autojoins calendar meetings by default once connected, appearing as fred@fireflies.ai in the attendee list. Otter has a similar AI Meeting Agent that can be invited to a specific call or set to autojoin from a connected calendar — Otter's own site also now sells a separate bot-free desktop app for exactly this reason, which is worth knowing if Otter's the tool your team already uses: the fix might be a setting change, not a new subscription.

Not every meeting AI works this way. Zoom's built-in meeting summary and Microsoft Teams' Intelligent Recap both run inside the call itself rather than joining as a second participant — nothing new appears in the attendee list either way, because the feature is part of the platform the call is already running on. The distinction that matters for this problem specifically isn't "AI notes, yes or no" — it's whether a separate account dials in.

The actual fix: record what your Mac already hears

Coii AudioNotes doesn't dial into anything. It records your microphone and your Mac's system audio — the call as your speakers are already playing it — as two separate tracks, entirely on the device running the app. There is no account for it to join under, no calendar it watches, and nothing on the call's attendee list changes, because nothing new connected to the call. It works the same way whether the call is on Zoom, Meet, Teams, a phone bridged through the Mac, or a conversation with no video call software involved at all.

That also means it can't autojoin a meeting on your behalf the way Fireflies or Otter's agent can — you have to be at your Mac, recording, for it to capture anything. For a solo consultant or account manager who's usually the one on the call anyway, that trade is the point: the tool does not decide, on its own, to show up somewhere. See meeting recorder without a bot for what that setup actually looks like, or the best meeting notes apps that don't put a bot in the call for other tools that made the same choice.

The pattern once it's happened once

A team that's had this moment once tends to overcorrect the second time: someone bans the notetaker from any calendar that touches external contacts, and now internal meetings lose the notes along with the external ones, because the setting that controls autojoin usually isn't granular enough to separate the two. The actual fix is narrower than a blanket ban — it's making sure the tool doing the recording is one that never needs a per-meeting decision about whether it's allowed to show up, so there's nothing to overcorrect against in the first place.

This is also where the choice of tool matters more than the choice of setting. A calendar-connected bot can, in principle, be configured carefully enough to only autojoin meetings tagged a certain way, on a calendar reviewed regularly, with someone responsible for keeping the rule current as the team's client list changes. In practice, that upkeep rarely survives contact with a growing team, a change in role, or someone forgetting the rule existed by the time the next new client is added to the calendar. A tool that was never watching the calendar in the first place doesn't have a rule that can go stale.

If you're stuck with the calendar bot for now

Turning off autojoin in the connected account's settings stops future meetings from getting an uninvited guest, but it's a per-account setting — a colleague on the same workspace can still have it on, and a bot someone else invited to a shared meeting isn't yours to switch off. If a client meeting is coming up and the bot's presence would be a problem, the safer move is inviting it explicitly only when everyone's expecting it, or recording that specific call a different way.

Checking a meeting for a bot before it becomes a conversation

If a call matters enough that a bot showing up would be awkward, look at the meeting platform's own participant list before anyone else joins, or ask directly at the top of the call whether anyone's connected recording software. It's a thirty-second question and it's a much better one to ask than the one that comes after someone's already noticed a name they don't recognize.

For a recurring external meeting — a client's weekly check-in, a candidate pipeline running through several interviewers — it's worth checking once whether autojoin is scoped narrowly enough that it won't surprise anyone on that particular series, rather than re-checking the participant list every single time. A setting fixed once is cheaper than a habit repeated forty times.

What to say if it's already happened

If the bot already joined and someone already asked about it, the honest answer is usually the least awkward one: name the tool, say it's for internal notes, and offer to remove it or turn it off for the rest of the call if that's more comfortable for the other side. Trying to talk around what it is tends to make people more curious about it, not less. Most people accept a straightforward answer and move on; what actually damages the relationship is a vague or evasive one, not the bot itself.

What actually changes once nothing joins the call

Once the recording is happening on your own Mac instead of through an invited participant, the mechanics of the call itself don't change at all — nobody has to be told anything is different, because from the other side there isn't anything to notice. The meeting starts the same way it always has, on whichever platform it was already going to run on, and the only thing that's different is that your own device is listening to what it can already hear rather than a separate service listening from inside the call. There's no attendee list entry to explain, no chat message announcing a notetaker, and no moment where someone has to decide whether to ask about it.

That also removes the need to remember to toggle anything before a sensitive call. A tool that has to be told, per meeting, whether it's allowed to dial in this time is a tool that will eventually dial in on the one call where it shouldn't have. A tool that only ever records what you're already listening to on your own machine doesn't have that failure mode, because there's no separate decision to get wrong.

What it costs

Coii AudioNotes is $19 once, covering three of your own Macs, with a 30-day trial that needs no card and no account to start. It runs on macOS 13 Ventura or later, on Apple Silicon and Intel, and nothing recorded ever leaves the machine it was made on. See what a meeting bot actually is for the underlying mechanics, or how to take notes without one joining for the full setup.