Why companies block AI meeting bots, and what people use instead

People who still want notes usually move to a notetaker that runs on their own computer and does not join the call. That solves the first problem completely, changes the second depending on the tool, and does nothing for the third — which remains the person recording's job. This guide goes through each reason and what a bot-free tool changes.

What the platforms say

The clearest statement of the concern comes from Microsoft, in the documentation for the Teams admin setting that detects external bots. As of September 2026, it says note-taking bots "may also introduce security and compliance risks when they access meetings without the organizer's awareness or consent", and that they may:

• "Record or transcribe meetings without participant awareness."
• "Store meeting data in third-party systems outside of the organization's compliance boundaries."
• "Introduce compliance, privacy, and data leakage risks."

(Microsoft Learn: manage external bots)

The setting, Manage external bots and their access to meetings, has two options: Do not detect bots, or When detected, require approval before joining. The second is the default. Detected bots are placed in the lobby "irrespective of the lobby configuration for the meeting" and the organiser has to admit them explicitly. Microsoft also notes the limits: some bots may not be detected, and a person can occasionally be misclassified as a bot.

Microsoft is also running a programme for bot vendors to identify their bots when joining (Teams Bot Identification Program), which points the same way: the platform wants bots to be visible and deliberately admitted.

Reason 1: an unknown participant

A bot is a participant. It arrives with a name the vendor chose, from infrastructure the host does not control, and receives everything said in the meeting. For the host, it looks much like any other stranger asking to be let in.

Security teams object to this because meeting access is how they keep conversations to the people invited. A lobby, a passcode and a "who can bypass" rule all exist to answer one question — who is in the room — and a bot adds an entry to that list that nobody in the organisation invited.

What a bot-free tool changes: everything, for this reason. A notetaker running on your computer is not a participant. There is nothing in the participant list and nothing for the host to admit. The people in the meeting are the people invited.

Reason 2: the content leaves for a vendor

A bot's whole job is to deliver the meeting's audio to its vendor. From there it is transcribed, summarised and stored, often in another country, under the vendor's retention rules and its own processors. For a regulated business, each of those is a question to answer: is there a contract, where is the data, who can see it, how long is it kept, can it be deleted.

What a bot-free tool changes: it depends on the tool. Some notetakers that run on your computer still stream the audio to a cloud transcription service; the difference from a bot is only that your computer does the sending. Others transcribe on the device, so the audio stays on the machine, and send only text — if anything — when you ask for a summary.

This is why "bot-free" alone is not an answer to a security team. Where does your meeting audio go? lists the questions to ask any vendor, bot or not.

Reason 3: people do not know they are being recorded

A bot is at least visible. People can see "Notetaker" in the participant list, even if they do not know what it does. Some organisations block bots because recording was happening that participants never agreed to — sometimes because a bot joined from someone's calendar without the person noticing.

What a bot-free tool changes: nothing in the tool's favour, and you should be honest about that. A recorder on your computer is not in the call, so the call shows no indicator. Your colleagues and clients cannot see that you are recording unless you tell them. That makes the announcement your job:

• Say it at the start: "I'm recording this for my notes — is that all right?"
• Put a line in the invite for recurring meetings.
• Stop if someone objects.

Where the law requires everyone's agreement, it requires it whatever tool you use. Bot-free meeting notes sets out the trade-offs of each approach in more detail.

What bot blocks do not cover

A lobby policy controls participants. It does not control what happens on each attendee's computer. That is why the real policy question for an organisation is not "bots or no bots" but "what may be recorded, how are people told, and where may it go". A few things an organisation that has blocked bots should also decide:

• Whether local recording is allowed on company machines, and with which tools.
• How people must announce it — out loud, in the invite, or both.
• Where recordings and notes may be stored, and for how long.
• Which outside services may receive transcript text for summaries, if any.

Rolling out a notetaker to a team and a written meeting recording policy are where those decisions belong.

If you work somewhere that blocks bots

1. Read the policy. The block may be only about bots, or it may cover recording in general. Those are different rules.
2. Ask IT before installing anything on a work machine. Tell them what the tool does with audio and text. A tool that transcribes on the device and sends nothing without an account is easier to approve than one that uploads audio, but that is their decision.
3. Tell people in the meeting, every time, whatever you use.
4. Keep what you record under the same rules as any other confidential document.

How Notey fits in

Notey is one of the tools people use where bots are blocked. It is a Mac app that records your microphone and the sound your Mac is playing as two separate tracks. Nothing joins the call.

• Participants: none added. There is nothing for a lobby policy to catch.
• Audio: recorded to your disk and transcribed there with Apple's on-device speech recognition. It is not uploaded, and there is no fallback that sends it.
• Text: with no account, nothing leaves the Mac. With an account, the transcript's text — never audio — is sent to Notey's service and on to OpenAI as a processor when you ask for AI notes, or when a meeting ends if write-ups are on. It is not used for training and not retained by Notey.
• Indicator: a red dot and elapsed time are shown in the window, menu bar and floating button whenever audio is being kept. They are visible to you, not to the call, which is why you still need to tell people.
• Permissions: microphone and system audio recording. It never asks for Screen Recording.

It does not solve the policy question for you. If your organisation has said no recording, a tool that is not in the call is not a way around that, and should not be used as one.

Frequently asked questions

Why was my AI notetaker bot not allowed into the meeting?

Either the host did not admit it from the lobby, or the organisation hosting the meeting has a policy that holds or blocks bots. In Microsoft Teams, detected external bots wait in the lobby for the organiser to admit them by default, as of September 2026.

Can Microsoft Teams block AI notetaker bots?

Teams admins have a meeting policy called "Manage external bots and their access to meetings". By default, detected bots are marked and held in the lobby until explicitly admitted. Microsoft notes that some bots may not be detected.

If bots are blocked, can I use a notetaker on my own computer instead?

Technically, yes — nothing joins the meeting. Whether you should depends on why the bot was blocked. If the concern was the audio going to a vendor or people not knowing, a local recorder does not remove your duty to tell people or to follow your organisation's rules.

Is a bot-free notetaker approved by IT automatically?

No. It is software on your computer, and many organisations control what can be installed. Ask before installing one on a work machine, and give IT the answers to where the audio and text go.