Ask Every Participant Before the AI Notetaker Joins the Call

Do I need consent, or is the recording banner enough?

Consent, and from everyone. A banner announcing that recording has started arrives after the decision was made and offers nobody a way to decline. In an all-party consent state the question is whether every participant agreed, and a candidate who watched a banner appear and said nothing has not clearly agreed to anything.

The statutes are older than the tools and they are written broadly. California makes it an offence to intentionally record a confidential communication without the consent of all parties, punishable by a fine of up to $2,500 per violation on a first offence and up to $10,000 on a repeat ¹. Washington bars intercepting or recording a private communication without first obtaining the consent of all the participants ². Neither turns on what the recorder is called.

That last point disposes of the most common workaround. It makes no difference whether the notetaker joins the call as a named participant, runs server-side inside the meeting platform, or is a phone propped against a monitor. All three produce a recording of a private conversation, which is the act the statute reaches.

It also makes no difference that the tool is used on every interview and always has been. Habit creates no agreement. A policy document the candidate never read reaches nobody, and a line in the calendar invitation discloses at most that a tool exists.

Which states are all-party, and why does the count move?

Published lists put the count near a dozen and disagree about the exact membership, because several of those statutes are all-party only for some kinds of communication. Two are not in doubt: California makes it an offence to record a confidential communication without the consent of all parties ¹, and Washington bars recording a private communication without the consent of all the participants ².

That disagreement is not carelessness on the part of whoever compiled the list. A statute can require every party's consent for a telephone call and not for a conversation in a room, or sit in a civil code rather than a criminal one, or turn on a court reading that has moved since the last time anyone counted. A compliance rule that depends on the exact count is fragile before you start.

The multi-state call is where the clean answers run out. A hiring panel is routinely four people in four states talking to a candidate in a fifth, and no court has produced a tidy rule for which state's law governs that call. The cautious reading is that the strictest participant's law is the one you have to survive. In a remote pipeline that is almost always an all-party state. Whether that reading holds for your pipeline is a question for your own counsel.

All of that argues against running the analysis at all. Deciding per call who is where, then looking up what that means, is slower than asking, gets delegated to whoever is running the interview, and fails silently the first time a candidate takes the call from an airport in a different state than the one on their application.

What do you owe the candidate beyond the word yes?

Four things, and all of them before you ask: who reads the transcript, how long it is kept, whether it becomes part of the hiring file, and whether the vendor trains on it. Consent to being recorded is not consent to everything downstream, and those four are the terms nobody put to the candidate. State them up front, or the yes you collected covers the recording alone.

The last one is where a default does the damage. Whether the vendor trains on your transcripts is a setting, and that setting has a value right now that somebody other than you chose. An interviewer who has never opened the admin console has already answered the question on the candidate's behalf without knowing what the answer was. Go and look before the next interview rather than after the next complaint.

The transcript's second life is a records question too. California's amended employment regulations, effective October 1, 2025, name the analysis of word choice and voice in online interviews as an example of an automated-decision system, and they extended the employment-records retention period from two years to four with automated-decision-system data expressly included ³⁵. A transcript that informs a hiring decision is part of the hiring record, which means it cannot quietly disappear when the req closes. What that implies for everything else you capture is worked through in what you may collect and keep from a candidate's AI session.

Do not expect the AI hiring statute you have heard of to cover this. Illinois has required notice, an explanation and consent since 2020, but its Artificial Intelligence Video Interview Act reaches exactly one technology, AI analysis of applicant-submitted video interviews, and it names no penalty and creates no private right of action ⁴. Your live panel call is governed by the wiretap statute instead, which does carry criminal exposure. And once the transcript exists, its summary raises its own problem: see what to do when the notetaker calls a candidate nervous and rehearsed.

Ask for consent in one sentence, before the bot joins

Say it out loud in the first thirty seconds, before the tool is admitted, and note the answer in the file. One sentence does the work: name the tool, say what it captures, say what happens to the transcript, and ask each person on the call to say yes. If anybody declines, the notetaker stays out and a human takes notes.

A script that fits in a breath, and has survived being read by real interviewers:

> Before we start: I use an AI notetaker that transcribes this call. The transcript goes to the hiring panel and into your file, it is kept for as long as hiring records are kept here, and the vendor does not train on it. Is that all right with everyone?

Then configure the things a script cannot fix, once, for the whole company:

• Default the notetaker to off for interview calendars, so joining is a decision rather than an accident.
• Turn vendor model training off and get that in the contract, not in a support-chat screenshot.
• Set a retention period that matches your hiring-records schedule and applies automatically.
• Limit transcript access to the panel plus the recruiter, and log who opened it.
• Record the consent itself, one line per candidate, in the same place you record the notice.

Two questions sit next to this one. Candidates increasingly run your interviews through their own tools, which is a different question with a different answer: what to do when candidates record and analyse your interviews. And an async video tool that scores what the candidate says sits under a separate statute and possibly a biometric one: what an AI video interview tool actually obliges you to do.

See how it works >