Business owner starting a recorded call

37 States Allow One-Party Recording: U.S. Call Rules for SMBs

You can legally record a phone call in most of the United States with just your own consent, but not everywhere. A majority of states and the District of Columbia follow one-party consent rules, while a smaller group of states demands that everyone on the line agree before a recording starts. The safe default, especially for a business fielding calls from customers in different states: assume the strictest applicable law governs, announce the recording, and get explicit consent before you hit record. Federal law under 18 U.S.C. § 2511 sets the floor, not the ceiling, and states are free to require more.


TL;DR:

  • Vermont has no specific wiretap statute for phone recording, and courts apply a reasonable expectation test based on common law.
  • Nevada’s statute suggests all-party consent, but the state’s Supreme Court has historically applied a one-party standard in practice.
  • The federal baseline permits recording by any party, but most states impose stricter rules requiring all-party consent, especially in certain situations.
  • In interstate calls, courts tend to prioritize the stricter state’s law, making it safer to treat all calls as all-party consent unless confirmed otherwise.
  • Implementing automatic disclosure notifications and secure, logged storage can significantly reduce legal risks for businesses making cross-state recordings.

Talkroute
Manage Calls With More Confidence
Talkroute helps small businesses manage calls, texts, voicemail, and team communications across devices with professional business features.

Explore Talkroute

Table of Contents

Call Recording Laws by State: The Quick Summary

Most callers assume the rules are the same everywhere. They aren’t, and the split matters more than people think.

Roughly 37 states plus D.C. use one-party consent, meaning any single participant in the call, including the person doing the recording, can legally hit record without telling anyone else. A smaller cluster of states require all-party consent, sometimes called two-party consent, where every person on the call has to agree first. A handful of others sit in a gray zone: hybrid statutes, disputed case law, or language that courts have interpreted differently depending on the circumstances.

Here’s the breakdown that matters for anyone making or receiving calls across state lines:

  • One-party consent states: The majority of the country, including Texas, New York, Ohio, and Georgia.
  • All-party consent states: A smaller group including California, Florida, Illinois, Pennsylvania, and Washington.
  • Hybrid or disputed states: States like Connecticut, Delaware, Hawaii, Michigan, Nevada, and Oregon apply different rules depending on whether the call is in-person, over the phone, or intercepted electronically.

Pro Tip: If you run a business that takes calls from anywhere in the country, build your policy around the strictest state you might reach, not the state where your office sits.

The practical policy for individuals and small businesses is simple: when in doubt, say something. A short, spoken notice at the start of a call, paired with the other party staying on the line, resolves the vast majority of legal exposure. Exceptions exist too. Recordings made to document a crime in progress, to protect personal safety, or by law enforcement under a warrant often fall outside the standard consent requirements, though the specifics vary by state statute.

The legal mechanics behind these two models come down to a single question: who has to agree before a recording is lawful?

Federal law answers that question first. 18 U.S.C. § 2511(2)(d) permits any party to a call to record it, as long as the recording isn’t made “for the purpose of committing any criminal or tortious act.” That’s the federal baseline, and it applies nationwide unless a state passes a stricter rule. Congress built in an important limit: consent doesn’t shield you if you’re recording to blackmail someone, harass them, or build a fraud scheme. The consent exception protects ordinary recording, not recording used as a weapon.

States that mirror the federal standard are called one-party consent states. If you’re on the call, you can record it, full stop, no notice required. That’s the law in Texas, New York, Ohio, Georgia, and roughly three dozen other states.

All-party consent states raise the bar. Every person on the call has to agree, not just the one doing the recording. California’s statute is the most cited example:

California Penal Code § 632 makes it a crime to record a “confidential communication” without the consent of all parties, and courts have applied this broadly to phone calls where at least one party has a reasonable expectation of privacy.

Florida, Illinois, Pennsylvania, and Washington apply similar logic, though the statutory language and penalties differ. Illinois, for instance, rewrote its eavesdropping statute after the state supreme court struck down an earlier version as unconstitutionally broad, which is a reminder that these laws aren’t static.

A few recurring exceptions show up across nearly every state’s statute:

  • Personal safety: Some states allow recording without consent if there’s a reasonable belief the call involves a threat of violence.
  • Public officials acting in an official capacity: Recordings of on-duty police or government employees performing public functions often fall outside consent requirements.
  • Implied consent: Courts in several states have found that continuing a call after hearing an automated recording disclosure can count as consent, even without a verbal “yes.”
  • No expectation of privacy: Calls made in public, or where the circumstances make privacy unreasonable, sometimes fall outside the statute entirely.

Courts also narrow or widen these statutes over time. Justia’s 50-state survey notes that exceptions and enforcement patterns shift as new case law comes down, which is exactly why a policy written in 2020 might not hold up today.

Call Recording Laws by State: The Full Reference Table

Every state statute uses slightly different language, and a handful have case law that complicates a simple one-party or all-party label. Consult the cited statute directly, and loop in counsel for anything involving litigation, evidentiary use, or ongoing government inquiries.

You are critically reviewing LanguageTool suggestions for a English passage.

For each suggestion below, decide whether it is a REAL error in context. Apply a suggestion ONLY when you are confident it fixes a genuine typo, grammar, agreement, or punctuation mistake.

Do NOT apply a suggestion when:

  • It capitalizes an ordinary word mid-sentence (LanguageTool often mistakes verbs/nouns for proper names, e.g. “mark” → “Mark” in “assess and mark damaged boards”)
  • It changes specialized/domain vocabulary that is already correct
  • It alters meaning, tone, or wording beyond the specific error
  • You are unsure — leave the original wording unchanged

Minimum changes only. If no suggestion should be applied, return the passage unchanged.
Return ONLY the passage (corrected or original).

Suggestions:

  1. “Neb” → likely “New” (Possible spelling mistake)

Passage:

State Consent Rule Governing Statute Practical Note
Alabama One-party Ala. Code Standard federal-aligned rule.
Alaska One-party Alaska Stat. No unusual carve-outs.
Arizona One-party Ariz. Rev. Stat. Follows federal model closely.
Arkansas One-party Ark. Code No unusual carve-outs.
California All-party Cal. Penal Code § 632 Applies to any “confidential communication”; strict enforcement history.
Colorado One-party Colo. Rev. Stat. No unusual carve-outs.
Connecticut Hybrid Conn. Gen. Stat. All-party for phone calls; one-party for in-person recordings.
Delaware Hybrid/Disputed Del. Code Statute language has produced conflicting court interpretations.
Florida All-party Fla. Stat. Applies when parties have a reasonable expectation of privacy.
Georgia One-party Ga. Code No unusual carve-outs.
Hawaii Hybrid Haw. Rev. Stat. One-party for calls, but adds restrictions on hidden recording devices in private settings.
Idaho One-party Idaho Code No unusual carve-outs.
Illinois All-party Illinois Stat. Rewritten after prior version was ruled unconstitutional.
Indiana One-party Ind. Code No unusual carve-outs.
Nevada Disputed Nev. Rev. Stat. Statute suggests all-party, but state supreme court has applied a one-party standard in practice.
New Hampshire All-party N.H. Rev. Stat. Criminal penalties for violations.
New Jersey One-party N.J. Stat. No unusual carve-outs.
New Mexico One-party N.M. Stat. No unusual carve-outs.
New York One-party N.Y. Penal Law No unusual carve-outs.
North Carolina One-party N.C. Gen. Stat. No unusual carve-outs.
North Dakota One-party N.D. Cent. Code No unusual carve-outs.
Ohio One-party Ohio Rev. Code No unusual carve-outs.
Oklahoma One-party Okla. Stat. No unusual carve-outs.
Oregon Hybrid Or. Rev. Stat. All-party for in-person conversations; one-party generally applied to phone calls.
Pennsylvania All-party Pa. Cons. Stat. Among the strictest civil remedy provisions in the country.
Rhode Island One-party R.I. Gen. Laws § 11-35-21 No unusual carve-outs.
South Carolina One-party S.C. Code § 17-30-30 No unusual carve-outs.
South Dakota One-party S.D. Codified Laws § 23A-35A-20 No unusual carve-outs.
Tennessee One-party Tenn. Code § 39-13-601 No unusual carve-outs.
Texas One-party Tex. Penal Code § 16.02 No unusual carve-outs.
Utah One-party Utah Code § 77-23a-4 No unusual carve-outs.
Vermont One-party (no statute) Common law standard Vermont has no specific wiretap statute for phone recording; courts apply a common-law reasonable expectation test.
Virginia One-party Va. Code § 19.2-62 No unusual carve-outs.
Washington All-party Wash. Rev. Code § 9.73.030 Requires announcement at the start of the call in most cases.
West Virginia One-party W. Va. Code § 62-1D-3 No unusual carve-outs.
Wisconsin One-party Wis. Stat. § 968.31 No unusual carve-outs.
Wyoming One-party Wyo. Stat. § 7-3-702 No unusual carve-outs.
District of Columbia One-party D.C. Code § 23-542 Federal enclave rules generally track the federal standard.

Interstate Calls: Whose Law Applies?

Nothing in this list matters if you’re not sure which state’s law governs a given call, and that question gets complicated fast once callers are in different states.

The leading case is Kearney v. Salomon Smith Barney, decided by the California Supreme Court. A brokerage firm based in Georgia (a one-party state) was recording calls with California clients (an all-party state) without disclosure. The court held that California’s stricter consent law applied to protect its residents, even though the company was calling from a one-party jurisdiction. The practical result: courts often side with the state offering the greater privacy protection when a call crosses state lines.

Not every court follows Kearney the same way, and outcomes vary depending on where a lawsuit gets filed and which state’s contacts are strongest. That inconsistency is exactly why a safe operational rule beats trying to predict how a judge in a specific jurisdiction might rule.

The rule most compliance-minded businesses adopt: if any party to the call might be located in an all-party consent state, treat the entire call as if all-party consent is required. A few practical steps make that workable:

  • Ask for or confirm a caller’s state during account setup, especially for recurring business relationships.
  • Use area codes and billing addresses as a rough proxy when direct confirmation isn’t practical, understanding they’re not foolproof.
  • Build a consistent recorded announcement into your call flow so consent capture doesn’t depend on a live agent remembering to say it.
  • Log the date, time, and method of consent for every recorded call, not just the ones that feel legally sensitive.

A Practical Compliance Checklist for Businesses

Turning these rules into daily practice takes more than a one-line policy buried in an employee handbook. It takes a documented, repeatable system that holds up if someone ever asks you to prove it.

  1. Define scope. Decide exactly which calls get recorded (sales, support, all inbound, all outbound) and write it down.
  2. Assign recording authority. Specify who can turn recording on or off, and whether it’s automatic or manual.
  3. Build a consent script. A short line at the start of every call covers most exposure: “This call may be recorded for quality and training purposes.” Outbound calls need the same treatment, not just inbound.
  4. Capture consent evidence. Log a timestamp showing when the disclosure played and whether the other party continued the call, which several states treat as implied consent.
  5. Set a retention schedule. Decide how long recordings are kept and delete them on a fixed schedule rather than indefinitely.
  6. Control access. Limit who inside your organization can listen to or export recordings, and keep an access log.
  7. Train your team. Make sure every employee taking calls understands the policy, not just the ones who set it up.
  8. Set escalation triggers. Define when to involve legal counsel, such as calls tied to litigation, government subpoenas, or safety threats.

Pro Tip: Encrypt stored recordings at rest and in transit, and treat access logs the same way you’d treat financial records. A recording policy without secure storage is a policy in name only. Tools like Talkroute’s call recording storage build encryption and retention controls into the platform instead of leaving them to manual IT work.

Why This Guide Comes From a Business Communications Provider

Talkroute builds the systems that businesses use to run their phones, which puts compliance in a different light than a purely legal reference would. Talkroute’s call recording feature automatically applies notification settings, so a business can configure a compliant disclosure once rather than relying on every employee to remember it on every call.

That matters because the biggest compliance failures aren’t usually about ignorance of the law. They’re about inconsistency: one employee announces the recording, another forgets, and the business ends up with a mixed compliance record across thousands of calls. A platform-level control removes that variance. Pairing recording with Talkroute’s auto-attendant also means the same system that routes a call can also deliver the consent disclosure before the call ever reaches a live person, which closes a common gap in ad hoc recording setups.

How These Laws Shape Call Centers and Telemarketing

Call centers face a version of this problem at scale that a solo business owner never will: hundreds or thousands of calls a day, often crossing dozens of state lines before lunch.

That volume is exactly why call centers were early adopters of the “announce every call” approach, regardless of which state a customer happens to be calling from. It’s cheaper and safer to disclose recording on every single call than to build real-time state-detection logic that might fail on a fraction of a percent of calls, and that fraction is where lawsuits come from. Telemarketing operations carry extra exposure because they’re often making outbound calls into states where the recipient never opted into anything, which is a different legal posture than an inbound customer service line where the caller initiated contact.

Regulatory attention on this space hasn’t slowed down. Call centers operating without a documented, applied-to-every-call consent process are the ones most likely to face class-action exposure, because a single missed disclosure at scale isn’t a one-off mistake. It’s a pattern across thousands of calls that plaintiffs’ attorneys can point to as systemic. Outsourced call centers add another layer: the business hiring the vendor is often still liable for how that vendor’s agents handle disclosure, so contracts and vendor audits need to spell out recording consent requirements explicitly rather than assuming the vendor already has it covered.

Group calls multiply the compliance problem, because every additional participant is another person whose location, and whose state’s law, potentially matters.

The safest approach treats a conference call the same way it treats an interstate two-person call: assume the strictest participant’s state law applies. A few practices make that manageable rather than paralyzing:

  • Play a recorded disclosure automatically when any participant joins, not just at the start of the call, since people dial into conference lines at different times.
  • Require an explicit verbal or digital acknowledgment for calls involving sensitive business matters, such as legal discussions or HR proceedings, rather than relying on implied consent through silence.
  • Name the recording status out loud during the call itself (“as a reminder, this call is being recorded”) for meetings that run long or where participants join late.
  • Keep a participant log alongside the recording, showing who joined, when, and whether they received the disclosure.

Video meeting platforms complicate this further, since a meeting host may be in one state, attendees in several others, and the recording stored in a fourth. Talkroute’s video meeting feature and similar tools that combine calling, messaging, and meetings under one system make it easier to apply one consistent consent workflow across every format instead of managing separate policies for phone calls, conference lines, and video meetings.

Technology That Makes Compliance Easier to Manage

Manual compliance tracking, sticky notes on a phone, a verbal reminder to new hires, doesn’t scale past a handful of employees. Software closes that gap.

Modern business phone platforms build consent disclosure directly into the call flow, so the announcement plays automatically before a human ever picks up. That removes the single biggest point of failure: an employee simply forgetting. Automated timestamp logging solves a second problem, proving when consent was given rather than relying on someone’s memory months later if a dispute arises. Encrypted, access-controlled storage handles a third layer entirely separate from the recording law itself: data security. A recording obtained with perfect legal consent still creates liability if it leaks because of weak storage practices.

The most effective setups combine three things: automatic disclosure, timestamped consent logging, and encrypted retention with a defined deletion schedule. Businesses trying to patch this together with separate recording apps, spreadsheets for consent tracking, and generic cloud storage tend to have gaps precisely where the gaps are most expensive: at the seams between systems that were never designed to talk to each other.

Automated call compliance workflow stages

Recent Shifts Worth Watching in State Call Recording Law

The state-by-state map isn’t frozen. A few trends are worth tracking heading into 2026.

Illinois’ eavesdropping statute remains a cautionary tale: the state supreme court struck down an earlier version as unconstitutionally overbroad, and the legislature had to rewrite it to survive further challenge. That kind of rewrite can happen again in other states, particularly ones with older statutes drafted before smartphones made recording effortless. Michigan and Nevada continue to see disputed application, where the statute’s plain text and how courts actually apply it don’t fully match, and that gap tends to widen rather than close until a state’s highest court issues a definitive ruling.

Remote work and distributed teams have also pushed more businesses into accidental interstate recording exposure. A support team based in a one-party state, taking calls from customers across the country, is effectively an interstate recording operation whether the business thinks of itself that way or not. That reality is pushing more SMBs toward the conservative all-party-by-default policy described earlier in this guide, not because the law changed, but because the geography of who’s calling changed. Expect that pressure to keep building as remote customer service becomes the norm rather than the exception.

What Actually Matters Here, and What Doesn’t

Most guidance on this topic treats all 50 states as equally uncertain, and that’s the wrong lens. The one-party versus all-party split is genuinely simple for the vast majority of calls. The real risk sits almost entirely in the interstate gray zone, and in businesses that skip disclosure because they assume their home state’s rule is the only one that counts.

The conventional advice, “check your state’s law and you’re covered,” undersells how often a modern business call actually stays inside one state. A support line, a sales call, a scheduling call: any of these can cross into an all-party state without anyone on the call thinking about it. That’s the gap worth closing first, not memorizing 50 statute citations.

If you’re a business owner reading this looking for the one action to take this week, it’s not researching every state. It’s turning on an automatic recording disclosure for every call, inbound and outbound, regardless of where you think the other party is sitting. That single habit resolves the overwhelming majority of legal exposure this entire topic creates, and it costs nothing but a few seconds of call time.

— Paul

Getting call recording compliance right shouldn’t require a law degree or a patchwork of separate apps for recording, storage, and consent tracking. Talkroute builds the disclosure, the recording, and the secure storage into one system, so a small business can apply a consistent policy across every call without hiring outside compliance help for routine setup.

Talkroute

The platform’s call recording feature lets you automatically record calls with configurable notification messages, so your auto-attendant delivers the same disclosure every time, on every call, whether it’s the first call of the day or the five hundredth. Recordings are stored with the security controls a defensible policy requires, and access stays limited to the people you designate. None of this replaces legal counsel for genuinely high-stakes situations, like active litigation or a government inquiry, but for the day-to-day reality of running a business phone line across state lines, it removes the guesswork. If you want to see how it fits your call volume and team size, you can explore Talkroute’s communication tools and start a trial today.

Where to Verify These Rules Yourself

For the controlling legal text, go straight to the primary sources rather than relying on any single guide, including this one.

Consult a licensed attorney in your state for anything involving active disputes, litigation, or evidentiary use of a recording.

This article is general information, not a substitute for advice from a qualified lawyer. Consult a qualified legal professional about your own circumstances before acting on anything here.

Sources

FAQ

Can someone record a call without your permission?

In one-party consent states, yes, any participant can legally record without telling the others. In all-party states like California or Florida, recording without everyone’s consent is generally illegal.

Can I sue someone for recording me without permission?

In all-party consent states, unauthorized recording can create civil liability, including statutory damages and attorney fees in some cases, as outlined under statutes like Florida’s wiretap law. In one-party states, a recording made by a participant is typically lawful and doesn’t support a civil claim.

Do you legally have to tell someone the call is being recorded?

Only in all-party consent states, where disclosure and agreement from everyone on the call is required by law. In one-party states it’s good practice, and Talkroute’s auto-attendant can deliver that disclosure automatically, but it isn’t legally mandatory there.

California, Florida, Illinois, Maryland, Massachusetts, New Hampshire, Pennsylvania, and Washington require all-party consent, with several other states applying hybrid rules depending on the type of communication.

Stephanie

Stephanie is the Marketing Director at Talkroute and has been featured in Forbes, Inc, and Entrepreneur as a leading authority on business and telecommunications.

Stephanie is also the chief editor and contributing author for the Talkroute blog helping more than 200k entrepreneurs to start, run, and grow their businesses.

Stephanie37 States Allow One-Party Recording: U.S. Call Rules for SMBs