Call Recording Consent Laws by State: A 2026 Reference for Sales Teams

This page is general information, not legal advice. AmpUp is a software company, not a law firm. Recording statutes change, court interpretations shift, and the right answer often depends on facts specific to your situation. Have qualified counsel review your recording policy, your disclosure language, and your retention rules before you rely on any of this.

TL;DR: Most states follow the federal one-party consent baseline, which means a participant can record their own conversation without asking anyone else. Eleven states clearly require consent from everyone on a recorded phone call, and roughly five more have mixed or unsettled rules that most compliance teams treat as all-party anyway. For a multi-state sales team the practical answer is simple: disclose the recording and the AI notetaker before anything starts capturing, on every call, and get a verbal yes on the record. The federal wiretap litigation now testing AI notetakers makes that a much less optional practice than it was two years ago.

Why this got more urgent in 2026

For most of the last decade, call recording compliance in B2B sales was a settled question that nobody thought about much. A rep hit record, a disclosure played, and the risk felt theoretical.

That changed when AI notetakers became standard equipment. The design pattern most of these tools use, where a bot joins automatically through a calendar integration and begins capturing before anyone says a word, is now being tested directly in federal court. Four class actions filed against Otter.ai in August and September 2025 were consolidated in October 2025 as In re Otter.AI Privacy Litigation in the Northern District of California. The consolidated complaint asserts claims under the federal Electronic Communications Privacy Act, the California Invasion of Privacy Act, and several other statutes, alleging that OtterPilot joined meetings and recorded participants who had no notice. A motion-to-dismiss hearing was held on May 20, 2026, and the ruling has been closely watched because it is one of the first federal tests of whether decades-old wiretap statutes apply to an AI bot on a video call. A parallel case against Fireflies.ai raises biometric privacy claims in Illinois on a voiceprint theory.

Two things about that matter for your team regardless of how the case comes out. The first is that the litigation targets a design pattern rather than one company’s mistake, which means any tool that joins and captures before affirmative consent is operating in the same territory. The second is that plaintiffs are pursuing employers as well as vendors, so “our vendor handles compliance” is not a position your general counsel will enjoy defending. If you want the broader vendor evaluation lens, our conversation intelligence tools guide covers what to look for.

One-party versus all-party consent, explained

One-party consent means a single participant can authorize the recording, and that participant can be the person doing the recording. A rep in Texas talking to a prospect in Ohio can lawfully record their own call without asking, because their own consent satisfies the statute.

All-party consent, usually called two-party consent out of habit, requires everyone in the conversation to agree. The “two” is a misnomer that causes real problems, because the statutes govern all parties rather than two of them. A five-person discovery call in California requires five consents, not two.

The federal Wiretap Act sets a one-party baseline, and states are free to be stricter. Many are. The complication for interstate calls is that courts have not settled on a single rule for which state’s law governs when participants sit in states with different standards, and decisions have gone different ways. California and Pennsylvania courts have both applied their own statutes to out-of-state recorders on calls with in-state participants, which is why the “our headquarters is in a one-party state, so we are fine” reasoning is weaker than it sounds.

Because of that unsettledness, the prevailing compliance practice is to apply the most restrictive law among all the states where a participant is located. For a sales team that dials nationally, that means treating every call as all-party.

Which states require all-party consent for phone calls

Eleven states are all-party for recorded phone calls by clear statute or controlling case law:

• California
• Delaware
• Florida
• Illinois
• Maryland
• Massachusetts
• Montana
• Nevada
• New Hampshire
• Pennsylvania
• Washington

Published lists disagree on the total, and the disagreement is not sloppiness. It comes from a handful of states whose rules split by communication type, which means the same state can be correctly described as one-party or all-party depending on whether you are talking about a phone call or an in-person conversation.

Here is where the confusion usually lives:

Connecticut is all-party for telephone calls under its civil statute at Conn. Gen. Stat. § 52-570d, but one-party under the criminal eavesdropping provisions for in-person conversations. For a recorded sales call, treat it as all-party.

Michigan has a statute that reads as all-party on its face, but Michigan courts have recognized a participant exception since Sullivan v. Gray in 1982, a position a federal court reaffirmed in April 2026. A participant recording their own conversation is generally not eavesdropping under Michigan law. The Reporters Committee classifies Michigan as all-party specifically for recordings made by a third party who is not part of the conversation, which is a meaningfully different situation than a rep recording their own call.

Oregon runs the opposite way from Connecticut. It requires all-party consent for in-person oral conversations under Or. Rev. Stat. § 165.540 but only one-party consent for telephone and electronic communications. The original version of this reference had Oregon on the all-party list for calls, which is a common error worth correcting.

Missouri allows one-party consent for phone calls, though the Reporters Committee reads the statute as all-party for in-person conversations. If your reps do in-person meetings in Missouri, that distinction matters.

Hawaii and Maine are one-party generally but require all-party consent to record conversations in particularly private places.

Vermont is the genuine outlier, with no state recording statute at all, so the federal one-party baseline applies by default.

Call recording consent laws by state: full table

The standard below is stated for recorded phone and video calls, which is what matters for a sales motion. In-person conversations follow different rules in several states, and those exceptions are noted.

State	Standard for recorded calls	Note
Alabama	One-party	Disclosure is still the safer practice.
Alaska	One-party	Disclosure is still the safer practice.
Arizona	One-party	Disclosure is still the safer practice.
Arkansas	One-party	Disclosure is still the safer practice.
California	All-party	Get affirmative consent before capture begins. CIPA carries statutory damages.
Colorado	One-party	Disclosure is still the safer practice.
Connecticut	All-party	All-party for phone under the civil statute, one-party criminal for in-person.
Delaware	All-party	Get affirmative consent before capture begins.
District of Columbia	One-party	Disclosure is still the safer practice.
Florida	All-party	Get affirmative consent before capture begins.
Georgia	One-party	Disclosure is still the safer practice.
Hawaii	One-party	All-party for recordings in particularly private places.
Idaho	One-party	Disclosure is still the safer practice.
Illinois	All-party	Also the leading BIPA jurisdiction, which adds voiceprint exposure.
Indiana	One-party	Disclosure is still the safer practice.
Iowa	One-party	Disclosure is still the safer practice.
Kansas	One-party	Disclosure is still the safer practice.
Kentucky	One-party	Disclosure is still the safer practice.
Louisiana	One-party	Disclosure is still the safer practice.
Maine	One-party	All-party for recordings in particularly private places.
Maryland	All-party	Courts have generally required explicit rather than implied consent.
Massachusetts	All-party	Prohibits secret recording specifically, not only unconsented recording.
Michigan	One-party in practice	Statute reads all-party, but courts recognize a participant exception.
Minnesota	One-party	Disclosure is still the safer practice.
Mississippi	One-party	Disclosure is still the safer practice.
Missouri	One-party	RCFP reads the statute as all-party for in-person conversations.
Montana	All-party	Statute is framed around notification.
Nebraska	One-party	Disclosure is still the safer practice.
Nevada	All-party	All-party for phone under NRS § 200.620, one-party for in-person.
New Hampshire	All-party	Get affirmative consent before capture begins.
New Jersey	One-party	Disclosure is still the safer practice.
New Mexico	One-party	Disclosure is still the safer practice.
New York	One-party	Disclosure is still the safer practice.
North Carolina	One-party	Disclosure is still the safer practice.
North Dakota	One-party	Disclosure is still the safer practice.
Ohio	One-party	Disclosure is still the safer practice.
Oklahoma	One-party	Disclosure is still the safer practice.
Oregon	One-party for calls	All-party for in-person conversations under § 165.540.
Pennsylvania	All-party	Courts have applied the statute to out-of-state recorders.
Rhode Island	One-party	Disclosure is still the safer practice.
South Carolina	One-party	Disclosure is still the safer practice.
South Dakota	One-party	Disclosure is still the safer practice.
Tennessee	One-party	Disclosure is still the safer practice.
Texas	One-party	Disclosure is still the safer practice.
Utah	One-party	Disclosure is still the safer practice.
Vermont	One-party by default	No state recording statute, so the federal baseline applies.
Virginia	One-party	Disclosure is still the safer practice.
Washington	All-party	Violation is a gross misdemeanor under state law.
West Virginia	One-party	Disclosure is still the safer practice.
Wisconsin	One-party	Disclosure is still the safer practice.
Wyoming	One-party	Disclosure is still the safer practice.

Classifications above draw on the Reporters Committee for Freedom of the Press Recording Guide and the underlying state statutes. Verify current law with counsel before setting policy, particularly for the mixed-rule states.

Why AI notetakers raise the stakes

The consent analysis for an AI notetaker is not new law, but the fact pattern is genuinely different from a rep pressing record.

Automatic joining is the core problem. When a bot enters through a calendar integration, capture frequently begins before any human has said anything, which produces an undisclosed recording in the window between the bot joining and the rep’s disclosure. In a one-party state that window is harmless. In California it is the whole case.

“We do not store audio” does not resolve it either. CIPA prohibits reading, attempting to read, or learning the contents of a communication without consent, so real-time analysis that generates a transcript can itself be the alleged violation even when no audio file persists. That is a narrower escape hatch than most vendors’ marketing implies.

There is also a second theory stacked on top of the wiretap one. Notetakers that process voice characteristics to identify speakers may be generating voiceprints, which are biometric identifiers regulated under Illinois BIPA. That statute has a private right of action and per-violation damages, which is why Illinois shows up disproportionately in this litigation.

And a visible bot in the participant list is notice, not consent. In an all-party state, notice alone may not be enough. Build the workflow around an affirmative yes.

How to operationalize consent across a multi-state team

Set one standard and make it all-party. Do not ask reps to determine the governing law mid-call. They will get it wrong, and asking them to try creates a documentation trail showing you knew the analysis was complicated and delegated it anyway. One policy, applied everywhere, is both safer and cheaper to run.

Configure tools so nothing captures before the disclosure. This is the single highest-leverage control, and it is a settings question rather than a training question. Turn off auto-join, or configure the notetaker to require a manual start. A policy that depends on reps remembering to say something before a bot that has already joined is a policy that will fail on a Tuesday afternoon in Q4.

Script the disclosure and get a verbal yes. Something like: “Before we get started, I want to let you know I’m recording this call and using an AI assistant to take notes. Is everyone comfortable with that?” Then wait for an actual response before starting. A recorded yes travels across jurisdictions in a way that a checkbox on a scheduling page does not.

Handle late joiners explicitly. When someone joins after consent was captured, repeat the disclosure. Buying committees grow mid-call constantly, and the person who joins at minute twelve never consented to anything.

Document consent where you can find it later. Store the consent moment with the recording, transcript, or CRM activity record. Keep your disclosure language and your tool configuration under version control so you can establish which policy was in force on a given date. Litigation is a documentation exercise, and the team that can produce a dated configuration history is in a very different position than the team that cannot.

Define retention and deletion. Decide how long recordings, transcripts, and consent records live, then enforce it automatically. This is also a discovery question, not only a privacy one, since automated transcripts turn routine calls into discoverable evidence.

Give reps a path when someone declines. Consent that is coerced is not consent. Reps need a clear, low-drama fallback: turn the recording off, take manual notes, and continue. If your process makes declining awkward, you have built a compliance problem into your sales motion.

What to ask a recording vendor

Consent controls and data handling are separate evaluations, and most procurement processes only run the second one. Ask about both.

On consent, ask whether auto-join can be disabled at the org level, whether there is a pre-capture notice, whether recording indicators are visible to all participants, whether settings can vary by jurisdiction, and what happens when a participant joins late. On data, ask where audio and transcripts are stored, how long they persist, who inside the vendor can access them, whether the vendor or its model providers train on your data, and what the deletion process actually does.

AmpUp is SOC 2 Type II certified, encrypts data in transit and at rest, redacts PII before analysis, and does not use customer data to train external models. Our notetaker is optional rather than mandatory, since AmpUp can also run on recordings from a conversation intelligence tool you already own through our integrations. Full documentation lives in our Trust Center.

Those controls address storage and analysis. They do not decide whether you obtained proper consent before capture began, and no vendor’s certification can. That part stays with your organization and your counsel.

Legal disclaimer

This reference provides general information for planning purposes and is not legal advice. AmpUp is not a law firm and does not provide legal services. Federal, state, and local recording laws change, court interpretations evolve, and the applicable rule often depends on facts specific to a given call. The classifications above reflect publicly available summaries and statutes as of August 2026 and may not reflect subsequent developments. Confirm current law with qualified counsel in the relevant jurisdictions before adopting or revising any call recording or AI notetaker policy.

See what happens after the call

AmpUp analyzes sales conversations across preparation, objection handling, closing discipline, and product knowledge, then turns those signals into pre-call briefs, post-call coaching, and practice built from your live pipeline. It runs on recordings from a conversation intelligence tool you already own, or on its own notetaker if you do not have one.

Book a demo  and we will walk through the consent controls, the data handling, and what the coaching loop looks like on your calls.

---

Try AmpUp for Your Team

See how AmpUp’s AI sales coaching platform can help your team. Book a demo with AmpUp  to get started.

---

Frequently Asked Questions

Q: Which states require two-party consent to record a call?

Eleven states are clearly all-party for recorded phone calls: California, Delaware, Florida, Illinois, Maryland, Massachusetts, Montana, Nevada, New Hampshire, Pennsylvania, and Washington. Connecticut is all-party for phone calls under its civil statute, and Hawaii, Maine, Michigan, Missouri, Oregon, and Vermont have mixed or unsettled rules that split by communication type. Compliance teams commonly treat all of them as all-party, which removes the need to run the analysis call by call.

Q: Which consent law applies when a sales call crosses state lines?

Courts have not settled this, and decisions have gone different ways. The prevailing practice is to apply the strictest law among the states where any participant is located, partly because California and Pennsylvania courts have applied their statutes to recorders located outside those states. A uniform all-party policy resolves the question in advance rather than leaving it to a rep to figure out mid-call.

Q: Do consent laws apply to AI notetakers?

Generally yes, when the tool captures audio or derives a transcript from a conversation. The complication specific to notetakers is timing, since a bot that joins automatically through a calendar integration often begins capturing before anyone gives notice. That gap is the subject of active federal litigation, including the consolidated Otter.ai case in the Northern District of California. Configure the tool so nothing captures until after the disclosure and the response.

Q: Is a visible recording indicator enough consent?

Probably not in an all-party state. A bot in the participant list or an on-screen indicator provides notice, and several all-party statutes require consent rather than notice alone. Treat platform indicators as a useful backstop rather than as the consent mechanism, and get a verbal yes on the recording itself.

Q: What happens if consent is not obtained?

Consequences vary by jurisdiction and can include criminal exposure, civil claims with statutory damages, and evidentiary restrictions on using the recording. Several all-party statutes carry felony-level penalties, and federal and state wiretap statutes provide per-violation statutory damages that scale badly across a class. Pause recording whenever a participant declines or consent is unclear, and have counsel define your escalation and deletion procedure in advance.

Q: Can a prospect refuse to be recorded?

Yes, and your process should make that easy rather than awkward. Reps need a clear fallback: stop the recording, take notes manually, and carry on with the meeting. Pressuring someone into agreeing undercuts the consent you were trying to establish, and it is a poor first impression on a discovery call.