Why Teams now makes your meeting notetaker wait in a lobby

Jude Mercer, SEO and Content, Memoe — 12 October 2026

Three unrelated things happened to AI meeting notetakers in 2026. Microsoft Teams started detecting third-party notetaker bots and holding them in a lobby until a human lets them in. Google Meet began defaulting to deny unrecognised bots entry, so a host now has to approve one before it gets a seat. And at least one large employer banned the whole category of tool by name. None of this is about how good the notes are. It is about what a notetaker has to do to get into the room at all: join the call as its own participant, with its own name in the roster.

• Microsoft's own documentation for the feature says external meeting-assistant tools "may also introduce security and compliance risks when they access meetings without the organizer's awareness or consent," and lists what they may do: "record or transcribe meetings without participant awareness," and "store meeting data in third-party systems outside of the organization's compliance boundaries." Under the default policy, "the participants detected as bots are placed in the meeting lobby irrespective of the lobby configuration for the meeting," and organisers "need to explicitly admit these bots into the meeting." (Microsoft Learn, "Manage external bots and their access to meetings," updated 20 July 2026)
• BlueCross BlueShield of South Carolina told its own staff, on 14 May 2026, that "third-party AI note-taking assistants threaten our commitment to data security," named Otter.ai, Fireflies and Grain specifically as prohibited, and suggested going back to "traditional handwritten or typed notes" in the meantime. (BlueCross BlueShield of South Carolina, 14 May 2026)
• Being a bot that joins calls is its own maintenance problem even for the people building one: an open-source meeting bot's own bug tracker records that dismissing it from a channel doesn't stick. "The first person will join the channel and dismiss the bot. The second person will join the channel and will start the meeting again and we'll have to dismiss the bot again," a developer wrote, asking for the bot to remember it had already been turned away — "this can get annoying." (GitHub issue, 29 December 2025)

Two other teams building meeting notetakers noticed the same gap this year and sold the absence of a bot as the whole pitch: one shipped a note-taker advertised as having "no meeting bots" in February, another built one to run on the Mac itself in July. Not needing a bot is now a selling point on its own, not a footnote.

Why joining the call causes this

A notetaker that works this way needs a way into the room: a calendar invite it can dial into, or a meeting link it opens as a guest, so it can ask the platform for a seat and a name in the participant list. From the platform's side, that guest looks exactly like what its own anti-bot detection is built to find — an account whose only job is to listen, with no person behind it in the room. The lobby, the "please admit," and the compliance memo above are all reactions to that one design decision, not to the quality of any particular transcript.

How Moe takes notes without any of that

Moe never has to clear that bar, because it was never built to ask the call platform for anything. As the Meetings guide puts it: it takes meeting notes on your Mac, and nothing joins the call. Moe asks macOS which app already has your microphone open — Zoom, Teams, FaceTime, Slack, Discord, Webex, WhatsApp, Signal, or a browser tab on a video call — and records your own Mac's microphone and the call's own audio locally from there. There is no invite to accept, no guest name to add to the roster, and no lobby to sit in, because nothing ever asked the call for a seat.

That is not the same as recording people without telling them. Before anything starts, a consent sheet says what is being captured and where it goes, and reminds you that the other people on the call should know; a button copies a one-line announcement onto your clipboard to paste into the call's chat, because Moe cannot say it for you.

If you're deciding

A workplace policy against third-party AI note-taking is usually written about what happens to the data, not about the shape of the integration — the South Carolina memo above names specific tools and the risk of their cloud handling, not "any bot that joins a call." If the question in front of you is a compliance one, ask whoever wrote that policy whether it covers a Mac app that never contacts the call platform at all, rather than assuming the absence of a bot answers it for you on its own. It removes the lobby and the detection policy above; it doesn't remove the need to ask.