28 August 2026
Say it in the first ten seconds: "Heads up, this is being transcribed so I don't have to take notes — say if you'd rather it wasn't." That's the whole trick. The awkwardness people anticipate almost never shows up once the sentence is out.
Most people over-prepare this. They imagine a paragraph about data retention and consent and end up saying nothing at all, which is worse than saying something clumsy. One sentence, said before anyone starts talking about the actual agenda, does the job. It names what's happening, why, and gives an easy out.
Notice how the sentence above doesn't ask permission — it states a fact and offers an option. "Is it okay if I record this?" invites a negotiation nobody wants to have out loud in front of five colleagues. "This is being transcribed, say if that's a problem" gets the same consent with none of the theater.
The legal requirement depends entirely on where the people on the call are sitting, and this isn't a page that's going to pretend to settle that for you — jurisdictions split on one-party versus all-party consent, and the split can differ by which participant's location controls. If your meetings cross state or country lines regularly, that's a question for whoever handles compliance at your company, not a blog post.
What's decent is simpler and doesn't depend on geography: say it out loud, say it before substantive discussion starts, and don't rely on a participant having read a calendar invite footer three days ago. A line in the invite is a paper trail. A sentence at the top of the call is what actually counts as notice to a human being who's thinking about the agenda, not the fine print.
Saying it once at the start is necessary but not sufficient — people forget, join late, or step away and come back. The stronger version of notice is a persistent, visible indicator that doesn't depend on anyone's memory of what was said in the first minute.
On AVAY, that's a recording indicator on screen for the length of the call, and the AI participant itself is visible in the meeting — it's not a bot that silently dials in behind the scenes, it shows up as a participant like everyone else, which is a different kind of honesty than a badge in the corner. Someone who joins ten minutes late still sees it, without having to ask whether they missed an announcement.
This is the scenario people are actually anxious about, and it resolves faster than expected. Most of the time "no" isn't a hard no — it's someone who wasn't told in advance and wants a beat to think, or who's fine with notes but not a recording, or who's fine for the main discussion but not for one specific part.
Have the fallback ready rather than improvised. Turning transcription off for one call is not a big deal; scrambling to explain the policy live in front of the group is what makes it feel like one.
Almost nobody objects to being transcribed. What they're uneasy about is not knowing what happens to the transcript afterward — who can search it later, whether it leaves the room, whether a stray comment about a client becomes searchable forever. The recording itself is rarely the fear; the afterlife of the recording is.
That's worth addressing in the same breath as the notice, not as a separate policy document nobody reads. "This goes into our shared notes, searchable by the team, nothing external" answers the actual question a wary participant is holding, and it's a shorter sentence than most people expect it to be.
It depends on where the participants are — some places require only one party's consent, others require everyone's, and the rule can follow the participant's location rather than the host's. This isn't something a blog post can settle for your specific team; check with whoever handles compliance if your calls cross jurisdictions regularly.
It's a useful paper trail but not real notice, because most people don't reread invite footers before a call starts. Say it out loud at the top of the meeting as well — that's what participants actually register.
A spoken sentence at the start only reaches people who were there for it, which is why a persistent on-screen indicator matters — it gives anyone who joins late something to see rather than something they'd have to ask about.
Say it once as a standing team norm — "our calls are transcribed by default, same as always" — and it stops being a fresh announcement each time. The awkwardness people feel is almost always about novelty, not the fact itself.
Yes — it appears in the meeting as a visible participant rather than a bot dialing in from outside, so people can see it's there without needing a separate announcement mid-call. That's a different kind of transparency than a badge in the corner of the screen.
One plain sentence at the start, a visible indicator for the whole call, and a ready answer for where the notes end up — that's the entire practice. The dread is bigger than the moment.
AVAY is a video meeting platform that transcribes the call itself — no bot joins, because there is nothing to join. Start one at avay.ai, read how each part works in the documentation, or see what it costs.