Google Meet Now Blocks Meeting Bots by Default: What It Means for Your Note-Taker
You're on a Google Meet call and a name you don't recognize is sitting in the "waiting to join" list: Anon.Bot. A few months ago, Meet would have let it straight in. Starting this spring, Meet's default answer is no — and the host has to manually click "Admit" to let it through.
If you run an AI note-taker that joins your calls as a bot — Otter.ai, Fireflies, or similar — this is worth five minutes of your attention. Google didn't ban meeting bots by name, but it just changed the default in a way that catches a lot of them. Here's exactly what changed, why it happened now, and what it means for how you take meeting notes going forward.
What actually changed in Google Meet
In February 2026, Google announced the "safeguarded guest admit flow," a redesign of the Meet waiting room. It started rolling out to Rapid Release Workspace domains on March 24, 2026, with Scheduled Release domains following on April 7, 2026 (gradual rollout, up to 15 days).
Instead of one "waiting to join" list, hosts now see two separate queues:
"Confirmed users" — people already on the calendar invite, or from the host's own organization. These are admitted quickly, with a one-click "Admit all."
"Potential risk" — connections Meet flags as automated, suspicious, or unverifiable. Per Google's own announcement, the default action for this queue is to deny entry, and the host has to override it manually, one request at a time.
That second queue is the one that matters here. A bot that joins as an anonymous or unverified guest — which is exactly how most third-party meeting recorders work — now has to clear a "deny by default" gate on every single call, not just the ones where IT has explicitly blocked it.
Source: Google Workspace Updates — "Safeguarded guest admit flow in Google Meet"
Why Google did this now
This isn't happening in a vacuum. Otter.ai is currently defending a consolidated federal class action alleging its OtterPilot bot recorded and transcribed Zoom, Teams, and Google Meet calls without the consent of everyone on the line. The claims cite the Electronic Communications Privacy Act, California's wiretapping law, and Illinois' biometric privacy statute. The motion-to-dismiss hearing was held May 20, 2026 in San Jose; as of this writing the judge has not yet ruled.
Every major meeting platform has moved on bots since that lawsuit landed. Microsoft Teams now labels external bots "Unverified" in the lobby and requires explicit organizer admission by default, with tenant-wide auto-block available to admins (rolling out mid-2026). Zoom requires a host or co-host to start its own AI Companion and shows a visible on-screen indicator when it's active. Google Meet's own native note-taking feature, "Take notes for me," works the same way — host-initiated, with a visible banner, and data that stays inside the organization's tenant.
The common thread: platforms are making the presence of an AI listener something the host has to actively choose, not something a third party can quietly add. A bot that shows up uninvited is exactly the pattern all three companies are now designing against.
What this means if your note-taker uses a bot
Nothing gets you banned outright — Google didn't publish a blocklist of vendor names, and this feature is about connection risk signals, not brand names. But in practice:
Every external call gets an extra step. If your note-taker's bot lands in the "potential risk" queue, someone has to notice it, click through, and manually admit it — on every call, with every new host.
Distracted or unfamiliar hosts will just deny it. A host who doesn't recognize "Otter.ai Notetaker" sitting in a risk-flagged queue is more likely to hit deny than dig in and admit it, especially on a call with an external client who's also watching.
You won't always know it failed. If the bot gets denied, you may not find out until you go looking for notes that don't exist.
None of this affects tools that never send a bot into the call in the first place — there's no join request to flag, so there's nothing for the new queue to catch.
Bot-based vs. bot-free, after this change
Bot-based (Otter, Fireflies, tl;dv) | Bot-free (Micky, Granola) | |
|---|---|---|
Can land in Meet's "potential risk" queue | Yes, if unverified | No join request to flag |
Needs host to click "Admit" | Often, now | Never |
Works if you forget to start it before the call | Yes — can be added mid-call by anyone with the link | No — must be running on your machine first |
Captures meetings you're not personally in | Yes | No — follows your device, not the meeting |
Visible to other participants | Yes, as a named guest | No |
The honest trade-off cuts the other way too: a bot can join a meeting on your behalf even when you're double-booked, and it needs no local install. Bot-free tools give that up in exchange for never touching the admit flow at all.
The bot-free alternative
Bot-free recorders like Micky sidestep this entire problem by not joining the call as a participant. A small desktop app on your Mac or Windows machine captures system audio locally — the same sound already coming through your speakers — and transcribes from there. There's no guest in the roster, so there's no join request for Meet's risk detection to evaluate, admit, or deny.
The recording itself is also just the starting point. Micky's Meeting-to-X pipeline turns the transcript into the things you actually need afterward — a mindmap of the discussion, a slide draft, action items pushed to Slack or Notion — and stores each meeting as part of a connected knowledge graph, so patterns and decisions across meetings become queryable instead of buried in a folder of transcripts.
What to do this week
If you host external calls: check your Meet "waiting to join" list for a risk-flagged queue before your next client call, so you're not caught off guard mid-meeting.
If you're a Workspace admin: the org-level control for blocking specific third-party OAuth apps in Meet and Calendar is separate from this feature and has existed for a while — review it in the Admin console if bot access is a compliance concern.
If your note-taker keeps getting denied: it may be time to try a bot-free tool for the calls where it matters most — client pitches, board meetings, anything where an uninvited "Notetaker" in the queue is a bad look either way.
FAQ
Q. Did Google Meet ban all meeting bots?
No. Google didn't publish a list of blocked vendors. The safeguarded guest admit flow flags connections it assesses as automated or unverified into a queue that defaults to deny, and any bot joining as an anonymous or unrecognized guest can land in that queue — but the host can still admit it manually.
Q. When did this roll out?
Rapid Release Workspace domains started seeing it March 24, 2026; Scheduled Release domains followed April 7, 2026, both gradual rollouts of up to 15 days.
Q. Are Microsoft Teams and Zoom doing the same thing?
They're moving the same direction with different mechanics. Teams labels external bots "Unverified" and requires organizer admission by default (rolling out mid-2026), with an admin option to auto-block them tenant-wide. Zoom requires a host or co-host to start its AI Companion and shows an on-screen indicator when it's recording.
Q. Does switching to a bot-free tool mean I don't need consent anymore?
No — recording-consent laws apply to how you capture a conversation, not which app you use. Bot-free tools just remove the platform-level admission risk; telling participants you're taking notes is still good practice everywhere.
Try a note-taker that never has to ask permission
Micky records locally on your Mac or Windows machine, so there's no bot for Google Meet, Zoom, or Teams to flag, deny, or eject. Download it at micky.pro and your next meeting turns into notes, a mindmap, and the deliverables you needed — without a single admit-flow click.