AI Meeting Notes, Call Recording and Consent

Why this matters

An AI note-taker is a recording device with a summary attached. The moment one joins a customer call, a supplier call or a staff meeting, the shop is recording a conversation, and recording a conversation without the consent the law requires is, in some states, a crime and a basis for a civil suit by every person on the call. Separately, the summary it produces is wrong often enough that a shop relying on it for a customer's approval or a disciplinary record will eventually be holding a document that says something nobody said. Both problems are easy to avoid and both are common, because the tool makes recording feel like taking notes.

This is not legal advice. It is the map an owner needs before turning one of these features on, and the point at which to call an attorney.

The consent rule has two layers, and the state layer decides

The federal floor is one-party consent. Under the federal Wiretap Act, 18 U.S.C. 2511(2)(d), a person who is a party to a conversation may record it, or consent to its recording, without telling anyone else, as long as the recording is not made for a criminal or tortious purpose. If the shop's office manager is on the call, the shop is a party, and federally that is enough.

States add their own rule on top, and roughly a dozen require every party to consent. Most states follow the federal one-party model. A minority are all-party (often called two-party) states, and the commonly listed group includes California, Florida, Illinois, Maryland, Massachusetts, Montana, New Hampshire, Pennsylvania and Washington. Several others are all-party only in part: some apply the stricter rule to phone calls but not in-person conversations, or the reverse, and a few have court interpretations that cut against the plain text. That last group is exactly why a list in an article is not the answer for your state. Read your own state's statute, or have your attorney confirm it, before you rely on it.

The stricter state can reach a call that crosses a state line. A shop in a one-party state calling a customer in an all-party state is the common case for anyone near a border or with a second-home customer base. California's Supreme Court applied California's all-party rule to calls recorded by a business outside California (the 2006 Kearney decision), and that is the reasoning to plan around: if any party might be in an all-party state, treat the call as all-party. The practical consequence is that a shop operating in several states, or taking calls from anywhere, should run one rule everywhere, and the one rule that works everywhere is consent from everyone.

Penalties sit at the state layer and they are not small. All-party states typically make secret recording a criminal offense and give each person recorded a private civil claim, in some states with statutory damages per violation, which means per call. A shop that recorded every inbound call for a year without notice in an all-party state has not made one mistake; it has made one per call.

What consent looks like in practice

Consent can be express (the person says yes) or, in many states, implied by continuing the conversation after a clear notice. The familiar "this call may be recorded" announcement relies on implied consent. Most all-party states have treated a clear notice followed by continued participation as consent, but how clear the notice must be, and whether a beep tone alone counts, varies. The notice that holds up best is spoken, at the start, before anything substantive is said, and it names what the recording is for.

On a call where the shop's office is placing the call, or where an AI note-taker is joining a video meeting, the cleanest practice is to ask:

OFFICE: Before we start, I'd like to record this so
        our note tool can write up what we agree.
        Is that all right with you?
CUSTOMER: What's it for?
OFFICE: So nobody has to remember the details later.
        It stays in your job file. If you'd rather
        not, I'll just take notes by hand.
CUSTOMER: No, that's fine.
OFFICE: Thanks. And for the record, it's recording
        now, and you're okay with that?
CUSTOMER: Yes.

Three things that exchange does that a recorded announcement does not: it offers a real alternative, so the consent is freely given; it gets the yes on the recording itself, which is your proof; and it tells the customer where the recording lives, which answers the next question before they ask it.

Everyone on the call, not just the customer. A three-way call with a supplier rep or a property manager means three consents. An AI note-taker joining a video meeting usually announces itself in the attendee list, and many people never read the list. Say it out loud.

Your own staff are parties too. Recording internal meetings, or a tech's calls from the truck, puts employees on the recording. In an all-party state they must consent like anyone else, and a written policy they acknowledged at hire is the usual way shops handle it. Employment-side recording questions (whether you can record a disciplinary meeting, what a union contract says) go to your employment attorney.

One more state layer to know about: voice biometrics. Some note-taking tools identify speakers by their voice. A voiceprint is a biometric identifier under some state laws, most notably Illinois' Biometric Information Privacy Act, which requires written notice and consent before collecting one and has produced large class actions. If a tool you are evaluating builds speaker profiles from voices, ask the vendor how it handles biometric consent, and ask your attorney before using it with anyone in a state with a biometric privacy law.

What the AI summary gets wrong, and in which direction

The recording is a record. The summary is a prediction of what a summary of that recording would usually say. That difference produces errors with a recognisable shape, and knowing the shape tells you what to check.

• Dropped negation. "We are not doing the relocation" becomes "relocation discussed." "Do not run it until the inspector clears it" becomes "run after inspection." This is the most dangerous error because it inverts the instruction while keeping all the right nouns.
• Invented action items. The tool is built to produce a tidy list of next steps, so it produces one even when the call ended with "let me think about it." A customer who said "maybe" appears as having approved.
• Merged or misattributed speakers. On a speakerphone with three voices, who said what gets reassigned, and "I'll pay for the tank" can migrate from the homeowner to the property manager.
• Smoothed disagreement. A call that was a dispute gets summarized as "discussed concerns, agreed to follow up," because summaries tend toward the resolution.
• Numbers and dates. A spoken "fifteen" heard as "fifty," "the 13th" as "the 30th." The transcript usually shows the mishearing; the summary hides it.

None of these are rare enough to ignore. The verification standard for AI output generally is its own card (see related: The Verify-Before-You-Send Rule for AI Output); for call summaries specifically, the rule is that the recording outranks the summary every time they disagree, and anything that matters gets checked against the recording or confirmed in writing.

What not to rely on an AI summary for

The pattern: a summary can help you remember; it should never be the thing that proves.

Worked example: a change order on a recorded call

A shop in a one-party state takes an inbound call from a customer with a water heater replacement already scheduled. The customer is at a second home in Florida, an all-party state. The office manager has the AI note-taker running on every inbound line.

The consent question first. The shop is in a one-party state, but the customer is in Florida. Under the cross-state reasoning above, the shop should treat this as an all-party call. The shop's line does play a recorded notice at pickup, which in many all-party states supports implied consent. Whether it does so in Florida, for this kind of notice, is the question the shop's attorney confirmed once, in writing, when they set the system up. If they had not done that, this call is the exposure, and every out-of-state call before it.

The call itself. Fourteen minutes. The customer agrees to add an expansion tank, asks about relocating the heater to the garage, and says, close to verbatim, "Don't do the relocation, call me Monday about it, I need to talk to my wife."

The summary. Nine bullets. Checked against the recording:

• One bullet says "Customer approved expansion tank and relocation to garage." The negation was dropped and two items were merged.
• One action item reads "Schedule relocation for Monday." Invented from "call me Monday."
• One bullet attributes "my wife will be there to let you in" to the office manager.

That is three of nine bullets wrong, a third of the summary, and two of the three point the same way: toward more work being approved than was. If the office had pasted the summary into the job record, the tech would have shown up ready to relocate a water heater the customer had told them not to touch.

What the office did instead. The office manager listened to the two minutes of recording around the change, corrected the job record by hand, and sent the customer a two-line written confirmation: expansion tank added, relocation not approved, call Monday. The customer replied "correct." That reply, not the summary and not the recording, is what the shop relies on if the invoice is disputed later.

What would change the call. If the customer had been in a one-party state and the shop had no out-of-state customers at all, the consent question shrinks to the federal floor, which the shop already meets by being a party. That is a narrower escape than it looks: it holds only while every party really is in a one-party state, and a shop near a border, with seasonal residents, or with any landlord customers who live elsewhere, cannot count on that from one call to the next. The summary problem does not change with the state at all.

Where to stop and call an attorney

Bring a professional in before you turn recording on, not after a complaint. Walk in with: the states your customers and staff are in; exactly what the tool records (audio, video, transcript, voice profiles); the notice you plan to give and when; where recordings are stored, who can access them and how long you keep them; and whether the vendor uses your recordings for anything else. Ask specifically whether your notice meets the all-party states you touch, how long you should keep recordings given that they become discoverable in any dispute, and whether any biometric privacy law applies to the tool's speaker identification.

References

• 18 U.S.C. 2511, the federal Wiretap Act, including the one-party consent provision at 2511(2)(d)
• Your state's own eavesdropping or wiretap statute (all-party states include California, Florida, Illinois, Maryland, Massachusetts, Montana, New Hampshire, Pennsylvania and Washington; confirm current text)
• Illinois Biometric Information Privacy Act (740 ILCS 14), where a tool builds voiceprints
• See related: The Verify-Before-You-Send Rule for AI Output
• See related: The Customer Recording You: Your Rights and Theirs