Free tool · no sign-up
An AI notetaker can join a call because one person on the invite connected it to their calendar. It arrives as a participant, records the people on the call, and the host may not know who brought it. This page gathers the settings Zoom, Microsoft and Google document for keeping uninvited participants out, with the menu paths and plan requirements from their own help pages.
Every step links to the official page it comes from, read on 8 Oct 2026. Menus move, so if a label on your screen differs, trust the linked page. Nothing you choose here leaves your browser.
Zoom’s page on blocking bots says bots, including AI notetakers, try to join as a participant, show up in the video tiles and the participant list, and can be hard to tell apart from real people. These are the settings a host can use in the Zoom web portal and in the meeting. Zoom’s articles name the same menus two ways: older ones say Account Management > Account Settings, newer ones say Admin Center > Settings. Each path below is written the way its article gives it, so the words on your screen may differ. (Source: Blocking bots from joining meetings and webinars, read 8 Oct 2026.)
Turn on the waiting room, then use Edit Options to choose who waits. The choices include “Everyone”, “Users not in your account”, “Users not on the meeting invite” and “Users not in your organization”. You can admit people one at a time or all at once.
Source: Zoom: Enabling and customizing the waiting room, read 8 Oct 2026.
When you schedule a meeting, tick “Require authentication to join” under Meeting Options or Security, and pick a sign-in profile if there is more than one. To let in a named guest who can’t sign in, click Add next to “Authentication Exception” and send them their own link. Exceptions don’t work with your Personal Meeting ID, so choose Generate Automatically for the meeting ID. For all your meetings, you can turn on “Only authenticated users can join meetings” in your settings; people without a Zoom account can’t join while it’s on.
Source: Zoom: Requiring authentication to join a meeting or webinar; Zoom: Allowing only authenticated users in meetings, read 8 Oct 2026.
Turn on “Block users in specific domains from joining meetings and webinars”, enter the domains separated by commas, and click Save. Zoom can check the domain only for someone who signed in, so use this together with sign-in. The checklist builder below writes the domains you enter in this format.
Source: Zoom: Blocking users in specific domains, read 8 Oct 2026.
When a Zoom Marketplace app starts reaching the meeting’s video, audio, chat or files, an icon appears in the meeting window. Open it to see the app, what it can reach and which participants approved it. It stays for the rest of the meeting, and it doesn’t report activity outside Zoom.
Source: Zoom: Using the Active Apps Notifier, read 8 Oct 2026.
In the meeting, click Host tools (called Security before desktop app 6.0.0) and choose Lock meeting. New participants can’t join while it’s locked. The same menu has Enable waiting room and Remove participant.
Source: Zoom: Changing security settings in a Zoom meeting, read 8 Oct 2026.
An account admin can block notetaker apps that join through Zoom’s Meeting SDK for everyone in the account, and can see how many joins were blocked. Choose I’m an account admin above to see how.
Source: Zoom: Blocking bots from joining meetings and webinars, read 8 Oct 2026.
Link to these steps, to send to a host or an admin.
Zoom says bots get in two ways: through Zoom Marketplace integrations (the Meeting SDK and Real-Time Media Streams), and through automated use of the Zoom apps and web app. Its page on blocking bots lists the controls below. Zoom’s articles name the same menus two ways: older ones say Account Management > Account Settings, newer ones say Admin Center > Settings. Each path below is written the way its article gives it, so the words on your screen may differ. (Source: Blocking bots from joining meetings and webinars, read 8 Oct 2026.)
Turn on “Manage which Zoom apps can join as a participant in meetings and webinars in your organization”. In the “Allow or block Zoom SDK apps” dialog, choose “Block specific SDK apps” (or “Allow specific SDK apps” to admit only the apps you pick), select the apps in “Select SDK apps” and click Save. Use Manage apps next to the setting to change the list later.
To switch from a block list to an allow list, remove every blocked app first. Apps that Zoom support blocked for you earlier were moved to this list and stay blocked, even if some don’t show. Zoom also says Meeting SDK apps that aren’t published on the Zoom Marketplace can’t join meetings outside the developer’s own account.
Source: Zoom: Managing SDK app access for meetings and webinars; Zoom: Blocking bots from joining meetings and webinars, read 8 Oct 2026.
“Only authenticated users can join from web client” applies to everyone who joins from a browser, inside and outside your account. “Only authenticated users can join meetings” applies to every meeting your users host, and people without a Zoom account can’t join while it’s on. Users can change these in their own settings unless you lock them.
Source: Zoom: Enabling or disabling Only authenticated users can join from web client; Zoom: Allowing only authenticated users in meetings; Zoom: Blocking bots from joining meetings and webinars, read 8 Oct 2026.
Authentication profiles decide what counts as signed in. The options include “Sign in to Zoom”, “Signed-in users in my account”, “Sign in to Zoom with specified domains”, “Signed in to account associated with invited email” and “Sign in to external Single Sign-On (SSO)”. Turn on “Allow authentication exception” so hosts can let in named guests who can’t sign in.
This article calls the main toggle “Only authenticated meeting participants and webinar attendees can join meetings and webinars”, where the article in the step above says “Only authenticated users can join meetings”.
Source: Zoom: Enabling and configuring authentication settings and profiles, read 8 Oct 2026.
Turn on “Enable waiting room”, click Edit Options and choose who waits. Zoom’s bot page suggests sending guests, meaning people who aren’t signed in, to the waiting room. The closest choice in the waiting room article is “Users not in your account”, which offers sign-in to people who aren’t signed in. Lock the setting to apply it to every user.
Source: Zoom: Enabling and customizing the waiting room; Zoom: Blocking bots from joining meetings and webinars, read 8 Oct 2026.
Turn on “Block users in specific domains from joining meetings and webinars”, enter the domains separated by commas, click Save and lock it. It matches only people who signed in, so pair it with sign-in. This list overrides domains allowed in authentication profiles, and a host can still let one person in by adding them as an authentication exception. For a group, use User Management > Groups.
Source: Zoom: Blocking users in specific domains, read 8 Oct 2026.
Leave “Allow removed participants to rejoin” off. By default, Zoom says removed participants “will not be able to rejoin the session using the same email address”. A change doesn’t apply to a meeting already in progress. The setting also exists for groups and for each user.
Source: Zoom: Allowing participants and panelists to rejoin, read 8 Oct 2026.
In the account settings, turn on “Identify guest participants in the meeting/webinar”. Anyone who isn’t signed in, or is signed in with an email outside your account, then shows with Guest in brackets after their name. The guest doesn’t see the label.
Source: Zoom: Identifying guests in the meeting/webinar, read 8 Oct 2026.
The Meeting Apps report shows join attempts, blocked join attempts, allowed joins and meetings with apps, split by whether the block came from the SDK settings or the web client settings, with the top five apps and a table of meetings with apps. It only reports. It doesn’t show apps that use Real-Time Media Streams or livestreaming apps.
Source: Zoom: Using the Meetings app dashboard, read 8 Oct 2026.
Zoom’s web app bot protection is on for every account and can’t be turned off; a real person it flags can still sign in to join. Zoom is also turning on “Require solving a CAPTCHA for guest users” for all accounts in phases, starting 22 July 2026. Guests get an invisible check, anyone flagged is asked to sign in, and once it’s on the setting no longer shows in the web portal.
Source: Zoom: Blocking bots from joining meetings and webinars; Zoom: Enabling or disabling the Join from your browser link setting, read 8 Oct 2026.
This covers apps your own users install, which is a separate question from who joins a meeting. Turn on “Require publicly listed apps on the Zoom App Marketplace to be approved by admin”, and the matching setting for unlisted apps. To turn an app off for everyone, use Disable (reversible) or Remove under Manage > Apps on Account > Added Apps.
Zoom says approval is on by default for multi-user accounts that haven’t used the Marketplace, and off for single-user accounts.
Source: Zoom: Admin management of the Zoom App Marketplace, read 8 Oct 2026.
Link to these steps, to send to a host or an admin.
Microsoft Teams detects some external bots and, by default, holds them in the lobby until someone admits them. Your admin’s meeting policy sets the defaults below, and as the organizer you can change most of them for each meeting in Meeting options, unless a sensitivity label or meeting template has locked them. (Source: Manage external bots and their access to meetings hosted in your organization; Meeting options in Microsoft Teams, read 8 Oct 2026.)
Open the meeting in your Teams calendar, select View event (or Edit series for a series), then Options. Meeting options open in a browser window. Under Meeting access, set “Who can bypass the lobby?” and select Apply. “People who were invited” also lets in people the invite was forwarded to. “People in my org” and “Only organizers and co-organizers” hold everyone from outside your organization in the lobby. A change to a series applies to future meetings.
Source: Microsoft: Using the lobby in Microsoft Teams meetings; Microsoft: Meeting options in Microsoft Teams; Microsoft: Roles in Microsoft Teams meetings; Microsoft: IT Admins: Manage lobby options in Microsoft Teams, read 8 Oct 2026.
In the same section, set “Who can admit from the lobby” to “Organizers and co-organizers”, so presenters can’t admit people. Microsoft recommends this alongside its bot detection, so a presenter can’t admit a detected bot by mistake.
Source: Microsoft: Meeting options in Microsoft Teams; Microsoft: Manage external bots and their access to meetings hosted in your organization, read 8 Oct 2026.
Leave “People dialing in can bypass the lobby” off. Off is the default unless your admin changed it.
Source: Microsoft: Meeting options in Microsoft Teams; Microsoft: IT Admins: Manage lobby options in Microsoft Teams, read 8 Oct 2026.
Select People and look under Waiting in the lobby: the check mark admits someone and the X denies them. When Teams detects bots, the lobby shows two sections: Waiting, for registered bots and people, with Admit All, and Suspected threats, for unverified bots Teams detects from behavioural and infrastructure patterns, with Deny All. The lobby notification has no Admit option for identified bots, and admitting one asks you to confirm, with a warning that it may record or transcribe the meeting. If Teams flags a person by mistake, you can mark them as human for that meeting.
Source: Microsoft: Using the lobby in Microsoft Teams meetings, read 8 Oct 2026.
Select Controls, then View more options, change Meeting access and select Apply. A change made during the meeting doesn’t move people who are already waiting.
Source: Microsoft: Using the lobby in Microsoft Teams meetings, read 8 Oct 2026.
Once everyone you expect has joined, select Controls > Lock meeting > Lock. Anyone trying to join is told the meeting is locked, and people who leave can’t rejoin until you unlock it. On a phone, use More actions > Lock the meeting.
Source: Microsoft: Lock a meeting in Microsoft Teams, read 8 Oct 2026.
Turn on the Meeting option “Require unverified participants to verify their info before joining”. Unverified participants then get a one-time code by email before they join. Your admin must first set “Anonymous users can join a meeting after verifying” to By email code. It isn’t supported for events.
Source: Microsoft: Meeting options in Microsoft Teams; Microsoft: Manage anonymous participant access to Teams meetings and events (IT admins), read 8 Oct 2026.
Link to these steps, to send to a host or an admin.
These settings live in meeting policies in the Teams admin center, and users get the Global policy unless you assign another. Microsoft calls the lobby settings below per-organizer policies, so everyone in a meeting gets the lobby settings of the organizer’s policy. Changes can take up to 24 hours. In tenants with the newer admin center layout, policies are under Settings & policies, so the path may look different. (Source: Manage meeting and events policies in Microsoft Teams; IT Admins: Manage lobby options in Microsoft Teams, read 8 Oct 2026.)
In the Meeting join & lobby section, set “Manage external bots and their access to meetings” to “When detected, require approval before joining”, which is the default. Microsoft says detected bots are then placed in the lobby “irrespective of the lobby configuration for the meeting”, and the organizer, or presenters if allowed, must admit them explicitly. The other value, “Do not detect bots”, lets bots appear like any other external participant. Set it in the Global policy or in a policy for a group or user.
Microsoft says some external bots may not be detected (you can report them through Feedback in Teams) and that a person may occasionally be flagged as a bot.
The same setting in PowerShell:
Set-CsTeamsMeetingPolicy -Identity <policy> -ExternalBotAccessMode RequireApprovalWhenDetectedSource: Microsoft: Manage external bots and their access to meetings hosted in your organization; Microsoft: Set-CsTeamsMeetingPolicy; Microsoft: Use Microsoft Teams administrator roles to manage Teams, read 8 Oct 2026.
In the same section, set “Who can admit from lobby” to organizers and co-organizers. Microsoft recommends this with bot detection, so presenters can’t admit a bot. Organizers can still change it for a meeting, and meeting templates and sensitivity labels can’t enforce this setting.
Source: Microsoft: Manage external bots and their access to meetings hosted in your organization; Microsoft: IT Admins: Manage lobby options in Microsoft Teams, read 8 Oct 2026.
Set “Who can bypass the lobby” to the narrowest choice that suits your organization, such as “People in my org”, and leave “People dialing in can bypass the lobby” off. The default for the first is “People in my org and guests”. Organizers can change both for a meeting; to enforce a value, use a meeting template or a sensitivity label.
Source: Microsoft: IT Admins: Manage lobby options in Microsoft Teams; Microsoft: Teams settings and policies reference, read 8 Oct 2026.
Teams counts as anonymous anyone not signed in with a work or school account, people from organizations you don’t trust, and people from trusted organizations that don’t trust yours. To stop them joining meetings your organizers host, set “Anonymous users can join a meeting unverified” to Off. With Teams Premium for the organizer, you can instead set “Anonymous users can join a meeting after verifying” to By email code. This also affects real guests who join anonymously, so consider who your organizers meet.
Microsoft says the org-wide setting “Anonymous users can join a meeting” (Meetings > Meeting settings > Participants) is going away, and recommends leaving it on and using the policy instead.
Source: Microsoft: Manage anonymous participant access to Teams meetings and events (IT admins), read 8 Oct 2026.
Next to “Teams and Skype for Business users in external organizations”, choose Allow all external domains (the default), Allow only specific external domains, Block only specific external domains or Block all external domains. Microsoft notes: “People from blocked domains can still join meetings anonymously if anonymous access is allowed.” Blocking a domain doesn’t block its subdomains unless you set -BlockAllSubdomains $True with Set-CsTenantFederationConfiguration.
Source: Microsoft: IT Admins: Manage external meetings and chat with people and organizations using Microsoft identities; Microsoft: Use Microsoft Teams administrator roles to manage Teams, read 8 Oct 2026.
Microsoft’s roadmap lists an option to block identified external bots automatically, rolling out from September 2026. Microsoft’s admin documentation didn’t describe the setting when we read it, so check the external bots article for the options your tenant has.
Source: Microsoft: Microsoft 365 roadmap, item 566201: Block all identified external bots automatically from joining your meetings; Microsoft: Manage external bots and their access to meetings hosted in your organization, read 8 Oct 2026.
Link to these steps, to send to a host or an admin.
Google says that when knocking is turned off, “Anonymous users or third-party bots, like note takers, that attempt to use ‘Ask to join’ are automatically denied access without actions required by the host.” These steps set that up for a meeting you schedule in Google Calendar. (Source: Tips to control meeting access and participation, read 8 Oct 2026.)
Trusted and Restricted meetings let people invited through the Google Calendar event join without knocking, so invite everyone you expect from the event. If a notetaker’s address is on the guest list, remove it.
Source: Google: Start or schedule a Google Meet video meeting, read 8 Oct 2026.
In the event, click Video call options next to Join with Google Meet, click Host controls and scroll to Meeting access. With Trusted, people in your organization and people invited through the Calendar event join without knocking, and everybody else knocks. With Restricted, only people invited through the Calendar event, or by a host from the meeting, can join, and everyone else knocks, including people in your organization who aren’t on the invite. Click Save. During a meeting, use Host controls at the bottom right.
Source: Google: Start or schedule a Google Meet video meeting; Google: Tips to control meeting access and participation, read 8 Oct 2026.
Under Meeting access, uncheck “Anyone with the meeting link can ask to join” for Trusted, or “Anyone can ask to join, including people who dial in” for Restricted. Google says this turns off knocking for the whole meeting. With Trusted, people in your organization and invited people from outside can still join, and they have to be signed in to a Google Account. Open meetings don’t offer this, because anyone with the link joins without knocking.
Source: Google: Tips to control meeting access and participation; Google: Tips to set up business meetings, read 8 Oct 2026.
Turn on Host must join before anyone else. If your organization has Google Meet waiting rooms, you won’t see this option. Use the Waiting room tab in Video call options instead and turn on Waiting room. Google says the waiting room holds people outside the main meeting even if they’re on the invite. If you turn on Bring in automatically, Google says the meeting starts and everyone waiting is moved in as soon as you or a co-host joins, so leave it off if you want to see who is waiting first.
Source: Google: Start or schedule a Google Meet video meeting; Google: Use waiting rooms in Google Meet; Google: Manage waiting room settings for your users, read 8 Oct 2026.
In Host controls, turn on Host management. Only hosts and co-hosts can then accept knocks, remove or mute people and add co-hosts. Google’s Calendar steps say it’s off by default, and your admin can set a different default for your organization.
Source: Google: Manage host controls; Google: Add co-hosts in Google Meet; Google: Tips to set up business meetings, read 8 Oct 2026.
A request to join shows Admit and Deny entry. With several requests, click View all to admit or deny each person, or use Admit all or Deny all. Since a change Google rolled out in March and April 2026, Meet shows requests in two queues. Google says the second holds requests from people the host is more likely to need a closer look at, and that its default action is to deny entry, so check it before you admit anyone from it.
Source: Google: Tips to control meeting access and participation; Google: Add or remove people from a Google Meet meeting or call; Google: Google Workspace Updates: Safeguarded guest admit flow in Google Meet (24 March 2026), read 8 Oct 2026.
Link to these steps, to send to a host or an admin.
In the Google Admin console you set the defaults that hosts start from. Users can change the joining settings for meetings they create. Changes can take up to 24 hours, and Google says feature availability depends on your edition. (Source: Manage Meet settings (for admins); Manage meeting access settings for your users, read 8 Oct 2026.)
The rows that matter here are Domain (who can join meetings your organization creates), Joining (whether the host must join first and who must ask to join), Access Type (the default meeting access type), Waiting Rooms, Host management (on or off by default) and Warn for external participants, which marks people from outside your organization External in the People list. Apply them to an organizational unit or a group.
Source: Google: Manage Meet settings (for admins); Google: Manage meeting access settings for your users, read 8 Oct 2026.
For Google Workspace, Google lists the default under Domain as “By default, all Google Account users and those who haven’t signed in to a Google Account”. You can change it to “Only users in your organization or anyone who dial-in with a phone” or “Anyone signed in with a Google Account”. For Education, the default is users in your school and anyone who dials in. A narrower choice also keeps out real guests from outside, so pick the one that fits the meetings your people hold.
Source: Google: Join a meeting; Google: Manage Meet settings (for admins), read 8 Oct 2026.
Under Waiting Rooms, check Waiting room. Google describes it as allowing meeting hosts to move attendees to a waiting room.
Source: Google: Manage waiting room settings for your users, read 8 Oct 2026.
Google documents these as controls for apps, separate from guests who join by link. Meet video settings > Supplemental add-ons lets you pre-install and block Meet add-ons. Google Workspace Marketplace apps > Apps list > User Install Settings chooses whether users can install any apps, only allowlisted apps or no apps. Security > Access and data control > API controls lets you set a third-party app that signs in with Google to Blocked. Google doesn’t say that any of these stops a bot that joins by link.
Google warns that if you change the install setting to a more restrictive one, users might lose access to apps they installed before.
Source: Google: Manage Meet settings (for admins); Google: Set whether users can install Marketplace apps; Google: Control which apps access Google Workspace data, read 8 Oct 2026.
Link to these steps, to send to a host or an admin.
Choose your platform and the notetakers you want to keep out. You get the settings to use, the names to watch for when someone waits to join, the invite addresses to take off the guest list and the chat commands the vendors document. Each version ends with a line you can paste into the invite.
For Zoom, you can also enter domains to block, and the builder writes them in the format Zoom's block setting takes. Zoom matches that list only against people who signed in, and it keeps out everyone who signs in with an address at those domains. No notetaker vendor says which domain its bot signs in with, so the builder doesn't add any vendor's domain for you.
Keeping notetaker bots out of a Zoom call From recordist.app/tools/keep-bots-out. Settings checked against Zoom's help pages on 8 Oct 2026. Before the call - Turn on the waiting room (Settings > Meeting > Security > Waiting Room) and choose who waits under Edit Options. Choosing who waits needs a paid account. - Require sign-in: tick "Require authentication to join" when you schedule. This needs Pro, Business, Education or Enterprise, and an admin must have set up sign-in profiles. - Remove these addresses from the calendar invite if they are on it: - [email protected] (Avoma) - [email protected] (Fireflies.ai) - [email protected] (MeetGeek) - [email protected] (Sembly) - Account admins can block notetaker apps that join through Zoom's Meeting SDK: Admin Center > Settings > General > Security > "Manage which Zoom apps can join as a participant in meetings and webinars in your organization" > Block specific SDK apps. Search "Select SDK apps" for Avoma, Fathom, Fellow, Fireflies.ai, Gong, Grain, MeetGeek, Otter.ai, Read AI, Sembly, tl;dv. Zoom's help doesn't list which notetakers appear there. Names to watch for in the waiting room and participant list - Avoma: Avoma Assistant. Admins can rename it on plans that allow custom bot names. - Fathom: [Name]'s Fathom Notetaker. This is the default; Premium and Team plans can change it. - Fellow: no name documented. Fellow's help says the name is the inviter's first name or a name the workspace chooses. It also says the note taker posts a chat message saying who added it, unless the workspace has turned that message off or changed it, and it doesn't give the message's default wording. - Fireflies.ai: Fireflies.ai Notetaker; Fireflies Notetaker. Paid plans can change the name. - Gong: Gong recorder. Gong's invite address is different for each company, so it isn't listed here. Gong can also record through Zoom's own recording, with nothing in the participant list. - Grain: no name documented. Grain's help says its bot joins as a visible participant, but doesn't give a default name. - MeetGeek: [Your name] MeetGeek Notetaker. MeetGeek's Zoom guide says the Business plan can change the name and that the keyword "MeetGeek Bot" must stay in it. That differs from the name its in-call guide shows, so watch for both. - Otter.ai: [First name]'s Notetaker (Otter.ai); [Workspace name]'s Notetaker (Otter.ai). Users can change the first-name part, and Enterprise workspaces can change the rest of the name. Otter's own example is "Dani's AI Notetaker (Otter.ai)". - Read AI: read.ai meeting notes; Meeting Analytics from Read; [Name]'s Assistant; [Name]'s Notetaker. The first is the default. Workspace admins on paid plans can set a custom name. - Sembly: [Workspace name] Sembly Agent; Sembly Teammate. Sembly's help uses Sembly Teammate for Google Meet calls. Paid plans can rename it. - tl;dv: [First name]'s AI Notetaker If one gets in - Participants > the ellipsis (...) next to the name > Remove. By default a removed participant can't rejoin with the same email address. - Then Host tools > Lock meeting, so nobody new can join. - Fireflies.ai: type "/ff leave" in the meeting chat; Fireflies leaves the meeting. - Otter.ai: type "stop otter" in the meeting chat; any participant can type it, including people without an Otter account, and it removes every Otter Notetaker in the meeting. - Read AI: type "Read Stop" in the meeting chat; any participant can type it, and Read AI leaves and keeps a report of what it captured. - Read AI: type "Opt Out" in the meeting chat; any participant can type it, and Read AI leaves and deletes what it measured; if Read AI posted an opt-out link in the chat, use the link instead. Names in square brackets are filled in with a person's or workspace's name, and several vendors let users rename their bot, so treat the names as a guide. A line for the invite Please don't bring a notetaker bot to this call. If you'd like to record, ask at the start.
These notetakers say in their own help that they can join a call as a participant. The names are the ones each vendor's help shows, where square brackets stand for a person's or workspace's name. An invite address or chat command appears only where the vendor documents one. Notetakers that only record on the user's computer aren't listed, because nothing joins the call.
Admins can rename it on plans that allow custom bot names. Avoma's help says that in Google Meet it may be listed under "With potential risks", marked "Appears to be a bot".
Source: How to remove the Avoma Notetaker or stop and pause meeting recordings in Avoma; Admitting Avoma's Notetaker in Google Meet; How to record meetings without calendar connection; Automatic recording settings, read 8 Oct 2026.
This is the default; Premium and Team plans can change it.
Source: bot name setting; recording consent, read 8 Oct 2026.
Fellow's help says the name is the inviter's first name or a name the workspace chooses. It also says the note taker posts a chat message saying who added it, unless the workspace has turned that message off or changed it, and it doesn't give the message's default wording.
Source: Note Taker security and privacy; Customizing the Note Taker, read 8 Oct 2026.
Paid plans can change the name. Fireflies' help says that in Google Meet it may be listed under "With potential risks" in the participants panel.
Source: How Fireflies joins and records your meetings (FAQs); How to remove Fireflies from a meeting; How to invite Fireflies to Google Meet (and set up Google Workspace settings beforehand), read 8 Oct 2026.
Gong's invite address is different for each company, so it isn't listed here. Gong can also record through Zoom's own recording, with nothing in the participant list.
Source: How calls are recorded; Stop or cancel a recording, read 8 Oct 2026.
Grain's help says its bot joins as a visible participant, but doesn't give a default name.
Source: Bot capture, read 8 Oct 2026.
MeetGeek's Zoom guide says the Business plan can change the name and that the keyword "MeetGeek Bot" must stay in it. That differs from the name its in-call guide shows, so watch for both.
Source: Controlling MeetGeek during the call; How to invite MeetGeek to a meeting; Getting started with Zoom, read 8 Oct 2026.
Users can change the first-name part, and Enterprise workspaces can change the rest of the name. Otter's own example is "Dani's AI Notetaker (Otter.ai)".
Source: Otter Notetaker overview; Change Otter Notetaker's display name; Remove Otter Notetaker from your meeting, read 8 Oct 2026.
The first is the default. Workspace admins on paid plans can set a custom name.
Source: changing the assistant name; How to stop or opt out of a Read AI recording, read 8 Oct 2026.
Sembly's help uses Sembly Teammate for Google Meet calls. Paid plans can rename it.
Source: Customize Sembly Agent; Invite Sembly by email, read 8 Oct 2026.
Source: Updating your profile; How to stop tl;dv, read 8 Oct 2026.
Remove it, lock the meeting so it can't come straight back, and ask whose it is. If you aren't the host, tell the host, or ask the person who brought it to stop it.
Source: Managing participants in a meeting; Allowing participants and panelists to rejoin; Changing security settings in a Zoom meeting, read 8 Oct 2026.
Source: Using the lobby in Microsoft Teams meetings; Roles in Microsoft Teams meetings; Remove a person from a meeting (Outlook); Lock a meeting in Microsoft Teams, read 8 Oct 2026.
Source: Add or remove people from a Google Meet meeting or call, read 8 Oct 2026.
Typed in the meeting chat, these make the notetaker leave.
Say what you see: "A notetaker has joined. Whose is it?" The person who connected it can usually stop it from their notetaker's own app, and can turn off automatic joining for your future meetings. If they'd like a record of the call, agree on it out loud, with everyone, at the start.
Recordist is a Mac app that records calls and writes notes on the computer it runs on. It never joins the call, so there is nothing here to block. When a call starts, a card asks whether to record it, unless you have added that app to the automatic-recording list, which is empty until you do. Recordist doesn't tell the other people on the call, and it doesn't ask them for you, so tell them and ask. How to ask to record a call has the words.
Each page was read on 8 Oct 2026. The platform steps come only from Zoom, Microsoft and Google; the notetaker names, addresses and commands come only from each notetaker's own help.
Zoom, Microsoft Teams, Google Meet and the notetaker names on this page are trademarks of their owners, named here only to identify their products. Recordist isn't affiliated with any of them. This page is general information about their settings. If something here is out of date, write to [email protected] and we will correct it.
Wren · Recordist's support assistant (AI)
It answers from the Help Center and isn't a human.
Hi, I'm Wren, an AI assistant, not a person. I answer from Recordist's help articles and docs. I can't see anything on your computer, I can't access your recordings, and I can't issue refunds or make commitments on Recordist's behalf, and what I say about recording laws is general information, not legal advice. If you'd rather talk to a human, choose "Talk to a human" at any time and someone at Recordist will reply within one business day. Please don't paste transcripts or audio here; I don't need them, and support never asks for your transcripts or meeting audio.