Why did an AI bot join my meeting?

Somebody in IT gets this ticket every week now. A meeting starts and there is an extra name in the participant list: "Priya's Notetaker (Otter.ai)", "Fireflies.ai Notetaker", a tile called Read. Nobody invited it. Sometimes Priya is not even in the meeting. The help desk answers with the symptom: remove it, ask the organiser to switch off auto-join. I wanted to write down the mechanism instead. Once you see the plumbing the whole category makes sense, and so do the fights the platforms picked with it in 2026 and the lawsuit a court let proceed.

I build a meeting recorder that does not use a bot, so I have a stake. I have tried to keep the facts straight and give the bot vendors credit where it is due. Every claim about another company below is footnoted to a page I checked on 6 September 2026.

How the bot got in

An AI notetaker bot is a program on the vendor's servers that joins a video call the way a person would. It opens the meeting link and gets a tile like any other participant, and from there it hears everything. To know which link to open, the vendor asks for access to your calendar. Once it has that, the default in most products is to join every event that carries a meeting link. Circleback's help centre states the precondition in one sentence: it "will only join meetings that have an online meeting link (Zoom, Google Meet, Microsoft Teams, or Webex)". Which of those it joins is then a matter of toggles: internal, external, declined, someone else's.¹ Read.ai describes its default the same way: web mode is what happens "when Read AI is invited from a connected calendar".²

That explains the meetings you are not attending. The bot does not check whether its owner showed up. If a colleague granted calendar access months ago and forgot, their bot keeps arriving in meetings they declined or never planned to attend. It is not malicious. It is doing what the calendar told it to do.

The vendors that build bots are clear that the bot is not hiding. Otter's help centre answers the anonymity question with one word.³

"No. Notetaker cannot join a meeting anonymously or without appearing to other participants."

Otter.ai help centre, Notetaker overview, checked 6 September 2026

Fireflies says the same thing: its bot "is always visible in the participant list to ensure compliance".⁴ So the surprise is not that the bot is hidden. The surprise is that one calendar permission, granted once, turned into a standing invitation for a third party to sit in every call.

The three places a recorder can sit

Every meeting recorder I have looked at sits in one of three places. The place decides where your audio goes, who gets told, and what the platform can do about it.

01A bot joins as a participant

The vendor's server dials into your meeting link. Everyone sees a tile. Everyone's audio streams to the vendor before it goes anywhere else, and it is transcribed and stored there. This design works on Zoom, Meet and Teams without installing anything on anyone's computer, which is why Otter, Fireflies, Read and Circleback all default to it.³⁴²¹

02The platform records natively

Zoom, Google Meet and Microsoft Teams each have their own notes feature now. Zoom's whitepaper explains that inside a Zoom meeting its notes feature reads the shared audio from the meeting's own media router; no participant is added.⁵ Google's "Take notes for me" is switched on inside the call and puts a pencil icon on every participant's screen.⁶ When Teams transcription starts, "All participants see a notification that the meeting is being transcribed."⁷ The recording lands in that platform's cloud. The cost is that it works inside that one platform (Zoom's desktop mode for Teams and Meet is the exception), and mostly only on a paid plan.

03Your own computer records

A desktop app captures what your microphone hears and what your speakers play. Granola's docs describe it exactly: "Granola runs locally on your device and captures audio directly from your microphone and system audio. No bot joins your meeting".⁸ tl;dv's desktop app records "Your microphone input" plus "Any system audio playing on your computer (including your participants' speech)".⁹ Fathom 3.0 added two bot-free modes; in Audio Only mode "Audio is captured locally on your device".¹⁰ Nothing appears in the participant list, and it works with any app that plays sound, Discord and a phone on speaker included.

Capturing locally and transcribing locally are two different things. Most bot-free apps capture on your machine and then upload the audio to their own servers to transcribe it. A few do the transcription on the machine too. MacWhisper is one: "Process sensitive content locally without data ever leaving your Mac."¹¹ MidMeeting is another.

2026: two platforms pushed back

For years the platforms had no cheap way to tell a bot from a person. In 2026 two of the three decided to try.

Microsoft went first and hardest. It announced Teams bot detection on 13 March 2026, in message centre notice MC1251206.¹² Its Teams admin documentation, updated 20 July 2026, describes bot detection at join time and a meeting policy called ExternalBotAccessMode with two values, AllowBots (the PowerShell reference spells it AllowAllBots) and RequireApprovalWhenDetected; the second is the default.¹³

"The participants detected as bots are placed in the meeting lobby irrespective of the lobby configuration for the meeting."

Microsoft Learn, Manage external bots and their access to meetings, checked 6 September 2026

Microsoft has announced a third value, BlockDetectedBots, under which a detected bot is blocked outright before it reaches the lobby.¹⁴ The roadmap (item 566201) listed it as "Rolling out" for September 2026 when I checked.¹⁵ As of 6 September neither the admin page nor the PowerShell reference lists it yet.¹³¹⁶ Microsoft also has a Bot Identification Program, in public preview and already at capacity, through which vendors can register their bots.¹⁷ Maestro Labs, Otter.ai, Read AI and Recall.ai had registered by the end of August.¹⁸ The same admin page is honest about the limits: some external bots may not be detected, and a person can be misclassified.¹³

Google moved the same month. On 24 March 2026 Google Meet shipped a "safeguarded guest admit flow" that splits knock requests into two queues and defaults the second one to deny. Google's post never uses the word bot.¹⁹ The help page for meeting access is less coy: "Anonymous users or third-party bots, like note takers, that try to use 'Ask to join' are automatically denied access without any action from the host."²⁰ The same page's access levels still admit anyone with the link under Open, and anyone on the Google Calendar invite under Trusted, without knocking. That is how a calendar-invited bot gets in, and why the calendar permission is the whole game.

Zoom has no account-wide switch. Its guidance, relayed on its own community forum, is to disable the notetaker app under Marketplace admin settings, which does nothing about a bot brought in by an external participant. In August 2026 a user on that thread was still reporting that domain blocking and authenticated-only meetings "doesn't seem to stop every AI notetaker".²¹ Waiting rooms are the practical answer on Zoom.

Notice what none of these controls touch. The platform's own notes feature is not a participant, so it never sees a lobby. Neither is a desktop app on someone's computer. The squeeze is on the bot specifically, and it is pushing vendors toward the other two places in the diagram.

A tile in the participant list is not consent

The bot vendors' implicit theory: the bot is visible, so everyone knew, so everyone consented. On 13 August 2026 a federal court declined to accept that theory at the pleading stage. The order in In re Otter.AI Privacy Litigation, No. 25-cv-06911-EKL (N.D. Cal.), by Judge Eumi K. Lee, let the wiretap, California Invasion of Privacy Act and Illinois biometric claims go forward against Otter.²² Two holdings matter to anyone buying or building one of these tools. First, the court held that Otter was plausibly a third-party eavesdropper rather than an extension of the host, because, as plaintiffs allege, it retains the recordings and uses them to improve its own models. Second, on one plaintiff's Washington claim, it said this about the visible tile.

"Even if the Otter Notetaker appeared in the meeting as another participant, the Court cannot infer that Dolan knew his communications were being recorded, transcribed, and retained by Otter."

Order on motion to dismiss, In re Otter.AI Privacy Litigation, 13 August 2026

The court still dismissed Dolan's Washington claim, with leave to amend, because he had not pleaded enough to show the conversations were private. It was Otter's consent argument that lost, not Otter.²² This is still a ruling on a motion to dismiss, not a verdict. It says the surviving claims are plausible, nothing more. But it is the first time I have seen a court engage with an AI notetaker's consent defence, and the tile-equals-consent argument did not survive the first round.

If you conclude from that ruling that the fix is to drop the bot and capture system audio quietly, read the next case. Chamberlain v. Granola, Inc., No. 3:26-cv-07926 (N.D. Cal.), filed 30 July 2026, is a class action under the same California statute against a notetaker that never appears in the participant list. The complaint's theory, as summarised by the law firm Barnes & Thornburg, is that "Granola uses system audio and microphone input to capture and transcribe all participants' communications in real time."²³ Bot-free moves the question from "did they see the tile" to "did you tell them"; it is not a legal free pass.

The rules differ by place, and the two California cases above are the strict end. In Canada, where I live, the Criminal Code is one-party: "if you're part of the conversation, you can record it". But a business recording for commercial purposes still owes notice and consent under privacy law (PIPEDA federally, or the provincial statute in Quebec, Alberta and BC). "Secretly recording a conversation is almost always seen as a hostile act," as a Canadian privacy lawyer puts it of workplace recordings.²⁴

Who sits where

The table shows each product's default capture method and whether the other people in the call can see it. Several bot vendors also ship a desktop mode; the table lists the modes I checked.

What the desktop route costs

I took the desktop route with my eyes open. Here is what it costs.

• A bot can attend a meeting you cannot. MidMeeting needs you, and your computer, in the call. Double-booked, a bot gets you a transcript and MidMeeting gets you nothing.
• A bot can record video and the shared screen. MidMeeting records audio only. If you need the slides back, this is the wrong tool.
• You have to press record. There is no calendar integration, so there is no auto-start, and sometimes you will forget.
• Them is everyone else, unnamed. A bot with a participant list can put names on lines. MidMeeting will not guess who among the other people said what.
• Transcription on your own machine means your machine does the work. Without a recent GPU the live text lags further behind the speaker, and you have to download a whisper model on first launch.
• It is not a team product. One licence covers up to three of your own machines; there is no shared workspace and nothing syncs.
• Device capture is invisible to the other people unless you make it visible: a feature against bot fatigue, a liability for consent.

Someone gave a notetaker their calendar and the calendar had your link on it. Removing the bot from the call fixes today's meeting. Asking who granted the calendar, and whether anyone in the room agreed, fixes the next one.

Sources

1. Meeting joining preferences, Circleback help centrechecked 6 September 2026
2. How consent works on web mode vs desktop mode, Read.ai supportchecked 6 September 2026
3. Otter Notetaker overview, Otter.ai help centrechecked 6 September 2026
4. How Fireflies joins and records your meetings, FAQs, Fireflies guidechecked 6 September 2026
5. My Notes, Zoom AI whitepaperchecked 6 September 2026
6. Take notes for me in Google Meet, Google Meet Helpchecked 6 September 2026
7. View live transcription in Microsoft Teams meetings, Microsoft Supportchecked 6 September 2026
8. Security, privacy and data FAQs, Granola docschecked 6 September 2026
9. Bot-free recording, tl;dv help centrechecked 6 September 2026
10. Capture modes in Fathom 3.0, Fathom help centrechecked 6 September 2026
11. MacWhisper home page, macwhisper.comchecked 6 September 2026
12. Teams meetings to block third-party recording bots, Office 365 for IT Pros, 16 March 2026checked 6 September 2026
13. Manage external bots and their access to meetings, Microsoft Learnchecked 6 September 2026
14. Microsoft Teams to block external bots automatically, UC Today, 30 June 2026checked 6 September 2026
15. Microsoft Teams: Block all identified external bots automatically from joining your meetings, Microsoft 365 roadmap item 566201checked 6 September 2026
16. Set-CsTeamsMeetingPolicy, Microsoft Teams PowerShell referencechecked 6 September 2026
17. Teams Bot Identification Program, Microsoft Learnchecked 6 September 2026
18. Teams blocks meeting notetaking bots, Office 365 for IT Pros, 24 August 2026checked 6 September 2026
19. Safeguarded guest admit flow in Google Meet, Google Workspace Updates, 24 March 2026checked 6 September 2026
20. Manage who can join your meeting, Google Meet Helpchecked 6 September 2026
21. How do I disable AI notetakers from joining our meetings, Zoom Communitychecked 6 September 2026
22. Order on motion to dismiss, In re Otter.AI Privacy Litigation, N.D. Cal., via Courthouse Newschecked 6 September 2026
23. What the Granola class action means for conversation capture tools, Barnes & Thornburgchecked 6 September 2026
24. Recording conversations using AI, Canadian Privacy Law Blogchecked 6 September 2026
25. Otter desktop app (Mac, Windows), Otter.ai help centrechecked 6 September 2026
26. Recording permissions with Otter, Otter.ai help centrechecked 6 September 2026
27. How to record meetings without a bot on the Fireflies desktop app, Fireflies guidechecked 6 September 2026
28. Recording consent and meeting compliance in Fireflies, Fireflies guidechecked 6 September 2026
29. Admitting and removing Read from a meeting, Read.ai supportchecked 6 September 2026
30. Understanding and setting your preferences, tl;dv help centrechecked 6 September 2026
31. Record meetings with the desktop app, Circleback help centrechecked 6 September 2026
32. Customize meeting participant, Circleback help centrechecked 6 September 2026
33. Transparency solutions, Granola docschecked 6 September 2026
34. Cluely home page, cluely.comchecked 6 September 2026