When Someone in the Meeting Objects to the Bot

Somebody has just said they would rather this meeting was not recorded, and five other people are listening. The mechanical part is easy: stop the recording. The part that decides how this goes is the twenty seconds afterward, and the most common mistake is reasonable-sounding and makes it worse. This is about handling the moment well, and about what a repeated objection is telling you. It is about etiquette and judgment rather than law, and recording rules vary by location, so check the ones that apply where you are.

What to do in the first ten seconds

Stop it. Then say some version of: "Of course, turning it off now. I'll take notes by hand."

That is the entire correct response. No explanation of how secure the tool is, no offer to delete it later instead, no clarifying question. Stop, acknowledge, move on, and let the meeting continue.

Then actually do it, visibly, so people can see the bot leave the participant list. If your tool captures system audio and there is nothing for anyone to see, say when it has stopped, because otherwise they have only your word and no confirmation.

Get the meeting moving again quickly. The longer the pause, the bigger the moment becomes, and the person who spoke up is already aware they interrupted the flow.

Why you do not ask them to justify it

The natural instinct is to ask why, and it is worth understanding why that lands badly.

Asking someone to explain an objection in front of a group means asking them to defend a preference publicly. If they have a specific reason, it may be something they do not want to say in that room, such as a concern about a particular colleague reading it. If they have only a vague discomfort, they now have to either invent a justification or back down. Both outcomes are worse than simply stopping.

The same applies to reassurance, which feels helpful and functions as pressure. "It's completely private, only I see it" is an argument for continuing, delivered to someone who has just asked you to stop. However gently you put it, you are relitigating a decision they made.

If you genuinely need to understand the concern, ask afterward and one to one. Often you will not need to.

What the objection is usually actually about

An objection is rarely about recording as such. In most cases it is one of three things:

They do not know who will see it. This is the most common by a distance. People are not objecting to a transcript existing; they are objecting to not knowing its audience. Someone who has never been told whether their manager can read the archive is making a reasonable inference in the absence of information.

They want to say something they cannot say on the record. Sometimes the objection arrives precisely because the meeting is about to get to the real subject. Stopping is what makes the useful conversation possible, so treat it as valuable rather than obstructive.

They have had a bad experience. A recording that circulated further than expected, or a quote taken out of context. That is not something you can argue away and not something you should try to.

None of these are addressed by explaining the software, which is exactly why explaining the software does not work.

Stopping properly, and proving it stopped

"Stopping" should mean nothing is being captured any more, and it is worth knowing what your tool actually does.

Most bot-based tools let you remove the bot from a meeting mid-call, and its disappearance from the participant list is visible proof. tl;dv, for example, documents being able to remove the bot from a meeting at any time.

Bot-free capture is where people get this wrong. If your tool is transcribing your computer's system audio, closing a window may not stop it, and there is no visual signal for anyone else. Know how to genuinely stop yours before you need to, and say clearly when it has stopped. This is one of the honest costs of invisible capture discussed in bot in the call versus bot-free capture.

Pausing for part of a meeting is a reasonable middle path where a specific section is the problem, such as a compensation discussion inside a longer review. Say when you are restarting.

What to do with the recording you already have

If the objection came ten minutes in, you are holding ten minutes they did not want captured.

Delete it, and say that you have. Keeping it because it is technically already recorded and might be useful is the decision most likely to damage trust, and it converts a well-handled moment into a bad one if it ever comes up.

Remember that deleting it may mean deleting in two places. The video platform's own recording and the notetaker's transcript are separate copies with separate controls, as covered in where your meeting recordings live. Deleting one leaves the other.

If the meeting was genuinely important and you need a record, take handwritten notes and share them with the person afterward so they can see what you wrote. That usually resolves the underlying concern entirely.

The same person objects every time

One objection is a preference. The same person objecting repeatedly is information about your setup, not about them.

Ask privately, and ask the specific question rather than the general one: "Is it the recording, or is it not knowing who can see it?" In most cases the answer is the second, and it points at a fixable setting rather than a personality clash.

Then stop recording meetings that person is in, as a standing arrangement. Do this without making it a thing. The cost is low, and repeatedly putting someone in a position where they must object publicly is a much higher cost that lands entirely on them.

Rewriting the default so it stops happening

Recurring objections mean your default is wrong. Three fixes, in order of effectiveness:

Tell people in advance. Most objections happen because the recording is a surprise. A line in the calendar invite gives people a private route to raise it, and the wording is covered in telling people you are recording.

Publish who can see the archive. If your team does not know the answer, they will assume the worst plausible one. Answering it up front removes the most common cause of objection outright, and it is part of the rollout advice in rolling a notetaker out to a team.

Record fewer meetings. The simplest fix. If a meeting type reliably draws objections, that is a signal it should not be recorded, and when not to use an AI notetaker at all covers where that line usually sits. For what people see that prompts the objection in the first place, see what everyone else sees when your notetaker joins, and for the wider criteria, the hub guide on how to choose an AI meeting note taker.

FAQ

What should I do if someone objects to being recorded?
Stop immediately, say you are stopping, and continue the meeting by hand. Do not ask them to justify it and do not offer reassurance about the tool, because both read as pressure to continue.

Should I ask why they object?
Not in front of the group. Asking someone to defend a preference publicly puts them in a worse position than simply stopping. Ask privately afterward if you genuinely need to know.

What do I do with the part I already recorded?
Delete it and say so, remembering that the platform recording and the notetaker transcript are separate copies. Keeping it because it exists is the choice most likely to cost you trust.

What if the same person objects every time?
Treat it as feedback on your setup. Ask privately whether it is the recording or not knowing who can see it, then stop recording meetings they are in as a standing arrangement.

How do I stop people objecting in the first place?
Tell them in advance in the calendar invite, publish who can access the archive, and record fewer meetings. Most objections are a reaction to being surprised.