How meeting bots work: what actually joins your call

The vendor then transcribes and summarises what it received and sends you the result.

Everything about how bots behave — why they appear as a tile, why they wait in lobbies, why they sometimes never arrive — follows from that one fact. This guide explains the mechanics in neutral terms. Bot-free meeting notes compares bots with the alternative.

The life of a bot, step by step

1. It learns about the meeting

Most notetaker services connect to your calendar. They read your events, find the video-call links in them, and decide which meetings to attend based on your settings — all meetings, only ones you organise, only ones with outside guests, and so on. Some also let you paste a link to send a bot on demand.

2. It joins at the start time

Shortly before the meeting, the vendor starts a process on its servers that joins the call. How it joins depends on the platform and the vendor:

• Through the platform's developer tools. Meeting platforms publish ways for software to take part in calls. Microsoft, for example, documents "real-time media" bots that join Teams calls and meetings and receive the audio frame by frame — 50 frames a second, each 20 ms of audio — alongside video and screen sharing (Microsoft Learn, as of September 2026).
• As a guest. Some bots join the way a person with the link would, and take the audio and video from what the meeting sends to that guest.

Either way, the platform treats it as an attendee. It gets a display name, usually the vendor's or one built from your name, and a tile.

3. It waits to be admitted

If the meeting has a lobby or waiting room, the bot waits there like anyone else until the host or an allowed participant admits it. Platforms have started treating bots as a category of their own. In Teams, detected external bots are placed in the lobby by default "irrespective of the lobby configuration for the meeting", and the organiser has to admit them explicitly (Microsoft Learn, as of September 2026).

4. It receives the meeting

Once in, the bot receives what an attendee receives: the audio of whoever is speaking, video, and shared screens. Because the platform knows who is talking, some bots can attach a name to each stretch of speech from the platform's own data rather than guessing from the sound.

Some platforms also require the host's permission before a participant — bot or person — can record. Zoom, for example, lets the host grant recording privileges to a participant during the meeting (Zoom support). A bot may therefore need the host's permission as well as admission.

5. It leaves and the vendor processes the recording

When the meeting ends or everyone leaves, the bot leaves too. The vendor transcribes the audio on its servers, writes notes, and sends them to you. What happens to the audio and video afterwards — kept, deleted, used for training or not — is set by the vendor's policies, not by the meeting platform.

Why bots fail to join

A bot depends on getting through the same doors as a guest, from a data centre, on time. The usual failures:

• Nobody admits it. The host is presenting, does not recognise the name, or declines it.
• The link changed. The meeting was rescheduled or moved to a new link, and the calendar event the bot read is out of date.
• The meeting requires sign-in. Some meetings only admit people from the same organisation, or signed-in accounts, which a vendor's bot is not.
• A passcode or registration is needed that is not in the calendar event.
• Policy blocks it. The hosting organisation has configured the platform to hold or refuse bots.

When a bot does not get in, there is no recording of that meeting at all.

Why bots get removed

Any participant with the right role can remove another participant. Hosts remove bots when they do not recognise them, when a client objects, or when their organisation's policy says to. Why companies block AI meeting bots covers the reasons security teams give.

What the others experience

For the rest of the meeting, a bot is a new face that nobody invited personally. Someone usually asks what it is. That question is healthy — people should know when they are recorded — but it is a conversation to have at the start, and in some client meetings it is an awkward one. Meeting bot etiquette covers how to handle it.

The other way to hear a meeting

The alternative is to capture the meeting on the device you are already using. Your computer already has the whole conversation: your microphone for you, and the audio output for everyone else. A recorder that captures those two as separate tracks can tell your side from theirs without joining anything.

That approach needs you to be in the meeting, and the call shows nobody that you are recording, so you have to tell them. In exchange, there is no participant to admit, and nothing depends on a lobby or a link. Notey works this way: it records your microphone and your Mac's audio as two tracks and transcribes them on the Mac.

Questions to ask a bot vendor

• Which calendars does it read, and which meetings does it join by default?
• What name does it join under, and does it announce itself?
• Where is the audio transcribed, and is it kept afterwards?
• Who can remove it, and what happens to a recording if it is removed?
• What happens when it cannot get in — are you told?

Frequently asked questions

What is a meeting bot?

A participant in a video call that is a program rather than a person. A notetaker bot is run by the notetaker's vendor on its servers, joins using the meeting link, and receives the audio and video so it can transcribe them.

How does a notetaker bot know which meetings to join?

Usually from your calendar. You connect a calendar to the vendor, it reads meeting links from your events, and it sends a bot to each one according to your settings.

Why is my notetaker bot stuck in the waiting room?

Because the meeting has a lobby or waiting room and nobody admitted it. Bots are subject to the same entry rules as guests, and some platforms hold detected bots in the lobby by default.

Can a meeting bot record if the host removes it?

No. Once removed it stops receiving the meeting, so there is nothing more to record.