Every State Has Different Call Recording Laws. Here's What Service Business Owners Need to Know.

# Every State Has Different Call Recording Laws. Here's What Service Business Owners Need to Know.

"This call may be recorded for quality assurance purposes."

That one sentence - or the absence of it - is the difference between a compliant AI receptionist and a legal liability sitting inside your phone system right now.

If you've deployed a voice AI to answer your business calls, you need to read this. Not because it's interesting compliance trivia. Because your vendor probably didn't tell you this when they set you up. And because if they got it wrong, the exposure is yours - not theirs.

Why This Matters More Than You Think

Every major voice AI platform records calls. That's not a feature - it's a necessity. The AI needs audio to transcribe, transcription to interpret, and recordings for the quality review that keeps the system improving. Recording isn't optional. It's structural.

What's not universal is the legal requirement around *disclosing* that recording to the person on the other end of the line.

And this is where the laws diverge sharply by state - in ways that most service business owners have never been told about.

One-Party vs. All-Party Consent: The Only Two Categories That Matter

US federal law, under the Electronic Communications Privacy Act of 1986, operates on a one-party consent standard. That means only one person in a conversation - you, or your AI, acting as an agent of your business - needs to consent to the recording. Federal law doesn't require you to *tell* the caller that the call is being recorded.

But federal law is the floor. States can - and do - set a higher bar.

One-party consent states (the majority): You can record the call without disclosing it to the other party. You or your system are a party to the call. Your consent is enough. No announcement required.

All-party consent states (the minority, but the consequential one): Everyone on the call must consent to it being recorded. The practical implementation of this is a disclosure at the start of the call. If you record without one, you've potentially violated the state wiretapping statute - a law originally written for wire fraud, now applied to phone recordings.

The penalties in all-party consent states aren't regulatory slaps. They're civil causes of action. Callers can sue.

The 13 All-Party Consent States

Here are the states where your AI *must* include a disclosure before recording a call:

1. California
2. Connecticut
3. Florida
4. Illinois
5. Maryland
6. Massachusetts
7. Michigan
8. Montana
9. Nevada
10. New Hampshire
11. Oregon
12. Pennsylvania
13. Washington

If your business operates in any of these states - meaning your callers are located in these states - the recording consent rules apply. "Where my business is incorporated" is not the relevant question. "Where the person picking up the phone is standing" is closer to the relevant question, though the analysis can get nuanced.

Let me walk through a few states where the rules or the enforcement history are particularly notable.

California - The Strictest, and the One Everyone Should Know

California's Invasion of Privacy Act (Penal Code § 630 et seq.) is widely considered the most aggressive all-party consent statute in the country.

It requires all parties to a confidential communication to consent to recording. "Confidential" has been interpreted broadly - and courts have generally sided with plaintiffs when businesses failed to disclose.

The civil penalty is actual damages, punitive damages, and attorney's fees. There are California Penal Code violations that attach criminal liability too, though civil suits are the more common mechanism for business-related recording violations.

If you operate any service business in California - HVAC, dental, law firm, staffing agency, moving company - and your AI is recording without a disclosure, you are operating outside what California law requires.

California businesses, or businesses that take California callers, need a disclosure. Full stop.

Florida - The One That Surprises People

Florida Statute § 934.03 is Florida's all-party consent law. What surprises operators who know California law but not Florida is that Florida is frequently included in the same risk tier.

Florida has been enforced. There's case law. There are plaintiffs' firms that specifically pursue recording violations. Florida's business environment - insurance agencies, real estate, contractor services, healthcare - produces high call volumes across industries that are rapidly adopting voice AI.

If you're a Florida service business deploying an AI receptionist and your vendor didn't mention this to you, that's a problem. Ask them directly.

Illinois - BIPA Adjacent, But Different

Illinois has the Eavesdropping Act (720 ILCS 5/14-1 et seq.), which requires all-party consent. Illinois is also the state that brought us BIOMETRICS in the form of BIPA - the Biometric Information Privacy Act - which set a national precedent for aggressive privacy litigation.

The litigious environment around privacy in Illinois is well-documented. If you're an Illinois business - a Chicago staffing agency, a Springfield contractor, a suburban dental practice - and your AI is recording calls without a disclosure, you're operating in a state that has shown it will enforce privacy statutes.

The Others - Don't Underestimate Them

Montana, New Hampshire, Oregon, and Nevada don't generate the case law headlines that California does, but their statutes exist and carry civil liability. Maryland and Massachusetts are active jurisdictions with established plaintiffs' bars. Michigan, Connecticut, Pennsylvania, and Washington complete the list.

The common thread: all-party consent means all parties must have the opportunity to consent - and the practical mechanism for that consent in an automated inbound call system is a verbal disclosure at the start of the call.

What a Compliant Disclosure Actually Sounds Like

Here's an example of compliant opening disclosure language:

> *"Thank you for calling [Business Name]. This call may be recorded for quality assurance and service improvement purposes. If you do not wish to be recorded, you may request to speak with a team member or call back during staffed hours."*

That's it. It doesn't have to be long. It doesn't have to be legalistic. It has to be *present*, delivered before the call's substantive content begins, and audible to the caller.

Some businesses prefer a shorter version:

> *"Thank you for calling [Business Name]. Please note this call is being recorded. How can I help you today?"*

Both work. The key elements are: (1) disclosure happens before the call's content, (2) the caller is informed the call is being recorded, and (3) there's no deception about it.