Consent and etiquette when the AI takes the minutes

Every tool on our shortlist records people. That makes consent the first feature to configure — before the summary templates, before the CRM sync. This page is the practical version: what the rules generally look like, what decent behavior looks like, and words you can actually say out loud.

The lay of the land, in plain language

Most recording rules in the United States descend from wiretap statutes, and they sort into two broad families. In one-party consent jurisdictions, a conversation may generally be recorded if at least one participant — you count — consents. In all-party consent jurisdictions (often called two-party), everyone in the conversation generally needs to consent. Federal law is commonly described as one-party; a number of states — California, Florida, Illinois, Maryland, Massachusetts, Pennsylvania and Washington come up most often in legal summaries — are commonly described as requiring all parties' consent, with definitions and exceptions that differ state to state.

Three practical consequences follow. First, in a multi-state video call you generally don't get to pick the friendliest rule; careful organizations default to the strictest plausible one. Second, "consent" in practice is often satisfied by clear notice plus continued participation — the reason meeting platforms show recording banners — but what counts varies. Third, outside the US the frame changes again: in much of Europe, recording and transcribing employees and customers lands in data-protection territory (GDPR-style lawful basis, retention, access rights), which is a compliance project, not a checkbox. International calls deserve extra caution and real counsel.

If you want the actual law, go to the actual sources: the Reporters Committee for Freedom of the Press maintains a well-regarded state-by-state recording guide, and the Justia and state-legislature summaries are a reasonable second stop. We deliberately don't reproduce a full state table here — it would rot, and you'd be trusting an affiliate site on a legal question, which you shouldn't.

The etiquette rules, which apply everywhere

Law is the floor. The ceiling — the thing that determines whether people speak freely around your note-taker — is etiquette, and it's the same in every jurisdiction:

• Announce before the first agenda item. "Quick note — I've got an AI note-taker running so I can stay in the conversation. Summary goes to everyone after. Anyone rather I switch it off?" Eleven seconds. Do it even when a platform banner already said so.
• Make the offer real. If someone objects and your answer is visibly reluctant, you've taught the room the question was theater. Kill the recorder cheerfully; take notes by hand; move on.
• Bot or no bot, same speech. A visible bot in the participant list is its own disclosure, awkward as it is (we've written about that awkwardness). Bot-free capture — Krisp's model, or Fathom's beta — removes the awkwardness, which means your announcement is the only disclosure. Quieter capture raises your speaking obligation, not lowers it.
• Externals get warned in writing. For candidates, clients, and anyone you'd like to keep as either: put "we'd like to record and AI-summarize this call" in the invite, so nobody spends the first five minutes deciding whether to object on camera.
• Sensitive moments go off the record. Compensation, health, conflict, anything HR-shaped: pause the capture and say you're pausing it. The pause is the trust-builder.
• Share what you captured. The cleanest legitimacy move there is: send the summary to everyone who was recorded. Secret minutes are how note-takers get banned.
• Know where your recording goes. "It's just notes" isn't true — audio and transcripts sit on some vendor's servers under some retention policy. Read our privacy rundown before you promise a room anything.

Scripts that don't kill the mood

Internal recurring meeting: "Standing reminder — the note-taker's on, minutes land in the channel after. Shout if today should be an exception." After the first week it's furniture.

Client call: "We use an AI note-taker so I'm not typing while you talk — you'll get the summary too. OK to leave it on?" The summary-sharing offer converts most skeptics; it turns surveillance into a service.

Interview (you're the interviewer): "We record and auto-summarize interviews so the panel debrief is based on what you actually said, not my memory of it. Comfortable with that?" And honor a no without a flicker.

Someone objects mid-meeting: "Done — it's off." Not "may I ask why." The why is theirs.

For the meeting owner: a two-minute policy

1. Decide the default (record internal recurring meetings: usually yes; record externals: only with written heads-up).
2. Decide the announcement wording and put it in meeting templates.
3. Decide where summaries go and who can search old transcripts — that's an access-control question, see privacy.
4. Decide the off-the-record gesture and use it visibly.
5. Write all four down where new hires will find them.

Teams that do this stop having the consent conversation weekly, because it's had once, properly, in writing.

Fair questions