The 12 States Where Your Sales Rep Can't Legally Record a Call Without Telling You

One-party vs all-party consent, the states that break the tidy list, and why a national sales motion is an all-party motion. Not legal advice.

2026-07-20 · SARA — KEEL'S AI DEAL ASSISTANT · GETKEEL.IO

The deal is with a hospital group in Seattle, the AE is dialing from Austin, and the sales ops playbook says every call gets recorded. Nobody on the revenue team has read Washington's consent statute. The customer's counsel has. Somewhere in the second week of the evaluation, a deputy general counsel asks, pleasantly, whether the vendor's calls have been recording Washington employees — and the deal acquires a problem that has nothing to do with the product.

One thing before the map: this is an operator's orientation, not legal advice. The statutes move, the case law moves more, and your counsel — not a blog post — should bless your recording policy.

"One-party" and "all-party" decide whose permission the recording needs

The mechanics are simple. Federal law and most states follow one-party consent: a conversation can be recorded if any one participant agrees — and the person hitting record counts as that participant. Your rep can lawfully record their own calls in these states without saying a word.

All-party consent states flip it: everyone on the call has to consent. That's what people mean by "two-party consent states" for sales calls — though "two-party" undersells it, since a five-person Zoom needs five consents, not two.

For a sales team, the difference is the whole game. In one-party states, recording is a private choice. In all-party states, it's a disclosure — the beep, the banner, the "this call is being recorded" — or it's a violation.

The count is 11, 12, or 13 — and the fuzziness is the first lesson

Ask how many all-party consent states exist and you'll get a different number from different trackers. The Reporters Committee's 50-state recording law guide counts eleven; other reputable lists say twelve or thirteen. Nobody is wrong. The states themselves are ambiguous, and how you count the edge cases decides your total.

Eight states are unambiguous all-party territory: California, Florida, Illinois, Maryland, Massachusetts, New Hampshire, Pennsylvania, and Washington. Record a call with someone there without their consent and you're on the wrong side of a statute.

Then come the four that break the tidy list. Nevada requires all-party consent for phone calls but not in-person conversations. Oregon runs the same split in reverse — all-party for in-person, one-party for phones. Connecticut is one-party for criminal purposes but exposes you to civil liability for recording phone calls without everyone's consent. And Montana requires that all parties be notified, which functions like consent with different paperwork.

Add Michigan if you like your ambiguity vintage: the statute reads all-party, but its courts have held that participants in a conversation can record it. That's how eight becomes eleven, twelve, or thirteen — and why "the 12 states" is less a fixed list than a warning label.

The unambiguous eight, one line each

California is the state your policy should be written for: the best-known consent statute in the country, a private right of action, and the source of a steady stream of recording lawsuits against companies — including ones whose only California contact was the person on the other end of the phone.

Florida and Pennsylvania both run criminal wiretap statutes with civil exposure alongside — and both host enough corporate headquarters that B2B reps call into them constantly without thinking of them as "strict states."

Illinois has the most instructive history: its original eavesdropping law was struck down in court, and the legislature promptly rewrote and re-enacted an all-party regime for private conversations. The lesson for a sales team is that this body of law regenerates — it doesn't fade.

Massachusetts is among the strictest in practice; its statute targets secret recording, which means the quiet-toggle approach — record now, disclose never — is precisely the behavior the law was written to catch.

Maryland, New Hampshire, and Washington round out the eight, and Washington deserves special respect from tech vendors: it's home to enough enterprise buyers that "we don't sell much into all-party states" is rarely true for anyone selling software.

None of this is a reason to panic. It's a reason to stop treating the recording toggle as a default instead of a decision.

Your AI notetaker is a recording device, and the law knows it

A common blind spot: teams that would never secretly record a phone call think of the AI notetaker as something else. It isn't. A bot that captures audio from a Zoom is recording a conversation, and consent law doesn't care that the output is a summary instead of an MP3.

The visible bot in the participant list functions as disclosure — which is why vendors put it there. But the disclosure works on the customer exactly like the beep does: it announces that this conversation has an audience and an afterlife. And when the bot gets ejected from the meeting by a cautious buyer, which any enterprise rep has now seen happen, you're watching consent law operate in real time.

What's actually at stake if you get it wrong

The exposure comes in layers, and the statutory one is only the first. Depending on the state, unconsented recording can mean criminal liability, civil damages, or both — and recordings made unlawfully have a way of surfacing at the worst procedural moment.

The second layer is commercial, and it's the one that fires more often: the deal where the customer's counsel asks the question our Seattle hospital group asked. Nothing needs to reach a courtroom for a recording policy to cost you a seven-figure relationship. Trust, once the question is raised, doesn't fully reset.

Does the beep actually count as consent?

Generally, clear notice plus continued participation is treated as consent — that's the legal architecture under every "this call may be recorded" script. Silence without notice is not consent anywhere.

But note what the mechanism requires: the customer must be plainly warned, every time, on every channel that's captured. The legal fix and the candor problem are the same event. There is no version of compliant recording in an all-party state that the customer doesn't know about — which means there's no version that doesn't change what the customer says.

The state that matters is the one you're calling into

Here's the trap that catches sales teams: reps assume their own state's law governs. The rep sits in Texas — one-party, easy — so the recording toggle stays on.

But the customer is in California. Which state's law applies to an interstate call is exactly the kind of question that produces expensive litigation, and courts have not answered it uniformly. The only operationally safe rule is the one every compliance team lands on: apply the most restrictive state on the call.

Now do the math on a mid-market territory. An AE carrying 8–20 deals across a national patch is calling into California, Florida, Illinois, Massachusetts, Pennsylvania, and Washington on any given week — six of the unambiguous eight. For practical purposes, a national sales motion is an all-party-consent motion, whatever your home state says.

Disclosure solves the legal problem and creates the sales problem

The standard fix is the one you've heard a thousand times: announce the recording. Consent by continued participation. Legal is satisfied.

But walk through what the disclosure does to the conversation itself. The customer now knows there's a permanent, shareable record. Their counsel has trained them on what recorded lines are for. The vendor-side rep knows the call is being scored as well as stored. Both sides shift, in the same direction: toward the official version.

We named that shift in the Gong anxiety piece — reps performing for the scorecard while the honest conversation migrates to stairwells and cell phones. The consent laws just add teeth: the same red light that makes reps guarded is, in a dozen states, also the law making sure the customer is warned enough to be guarded too.

The deals most affected are the ones in the most careful industries — healthcare, financial services, anywhere the buyer's legal team is good. Which is to say: the deals worth the most.

Regulated verticals aren't even having this debate

It's worth noticing who never installed the recording stack in the first place. Med device reps in hospital systems. Financial services AEs whose clients' compliance departments would end the relationship over an unconsented recording. Pharma reps in a world of sunshine laws and audit trails.

In those verticals, the answer to "can we record the customer?" was always no — so the most important conversations happen at site visits, dinners, and hallway run-ins, and the rep's memory is the only system of record. We've written the full argument in what call recording can't capture: the unrecorded conversation isn't the exception in these motions. It's the motion.

The consent-state map tells the rest of the market the same thing, just more slowly and with statutes.

What a compliant-by-design workflow looks like

There's a version of this problem that never touches a consent statute, because nothing is ever recorded.

The rep takes the call or the meeting with no recording running — nothing to disclose, nothing to store, no most-restrictive-state analysis. Afterward, the rep debriefs privately: what was said, what was promised, what felt off. The knowledge survives; the recording never existed.

It also survives procurement. Security questionnaires increasingly ask vendors how customer conversations are recorded, stored, and retained — a question that gets harder to answer every year the recording archive grows. "We don't record customer conversations" is a one-line answer that ends the section, and more buyers notice it than you'd think.

For the rep, the day looks like this: call ends, no beep ever happened, and the two minutes that used to go to checking the recording toggle go to the debrief instead — the champion's exact wording on timeline, the pause after the pricing question. Ten states or fifty, the workflow is identical.

That's not a compliance hack. It's what the reps who hate being recorded already figured out — the value was never the audio file. It was the thinking that happens around the conversation: prep before, honest processing after. Both work from memory and notes, and neither requires anyone's consent, in any state.

The audio-first workflow puts a legal question in the middle of every customer relationship. The memory-first workflow doesn't have a legal layer at all.

Quick reference: how to read your own territory

If your accounts cluster in the unambiguous eight — California, Florida, Illinois, Maryland, Massachusetts, New Hampshire, Pennsylvania, Washington — treat every call as all-party. Disclose or don't record.

If you sell nationally, adopt the most-restrictive rule and assume all-party everywhere; the alternative is asking reps to run a conflicts-of-law analysis before every dial. If you're in Nevada, Oregon, Connecticut, Montana, or Michigan, read your specific statute with counsel, because your state is one of the reasons the count won't sit still. And wherever you are, remember the disclosure's second effect: a legally clean recording is still a psychologically loud one.

Two habits keep a team out of trouble regardless of geography. First, make recording an explicit per-call decision with a named owner, not a workspace-wide default someone set during onboarding. Second, put the consent map on the same page of the playbook as the disclosure script — reps follow rules they can see, and almost nobody can name the all-party states from memory.

The map changes, too. States amend wiretap statutes, and courts reinterpret them — Michigan's gap between statute and case law is a standing example. A recording policy is not a set-and-forget document.

The law and the psychology agree

Recording consent law looks like a compliance chore, but read the dozen-state map next to the research on observation and a pattern appears: the legal system and human behavior both treat the recorded conversation as a different kind of conversation. One regulates it. The other guards it.

If your customers are in any of the 12 all-party-consent states, recording is a legal liability — not a coaching tool. The reps who've already figured this out are using tools that work without recording. Sara was built for them. Founders Club is invite-reviewed. Apply at getkeel.io/founders.

Sara is a 24/7 AI deal assistant with no recording anywhere in the product — you text or call her after the conversation, and she helps you think it through and remember what mattered. No consent question has ever applied to a rep thinking about their own deal.

Keep this model: the consent map isn't telling you where recording is inconvenient. It's telling you where the law has decided that conversations belong to everyone in them. Build your workflow on that assumption everywhere, and the map stops mattering.

By the team at Keel. We're building Sara, an AI deal assistant for the moments that don't get recorded.