Last updated: September 12, 2026
This page explains a rule and is not legal advice. Your own situation belongs to your counsel.
What one party consent means
One party consent means a recording is lawful when a single participant on the call agrees, and the participant who agrees can be you. Being on the call is what makes you eligible. Two things get missed: the rule ends at the state line, and permission to record is separate from permission to use the recording.
The operational version is shorter than the legal one. You are on the call, so you can record the call, and the consent the statute wants is your own. Nobody else has to be told.
Both misses matter. A standard that protects you at your desk does not travel to whoever picked up on the other end. Being a party earns you the right to make the recording and says nothing about who you can play it for later, which is where the money usually goes and not where the search traffic on this phrase is pointed.
The federal floor
One party consent starts with the party exception in the federal wiretap statute at 18 USC 2511(2)(d). The text, the criminal or tortious proviso on it, and the penalty behind the section are quoted on whether it is illegal to record a phone call, so reprinting them here would split one explanation across two pages.
Federal law sets a floor, states are free to build higher, and the stricter of the two rules is the one you have to satisfy.
Why most states landed in the same place
Most state wiretap statutes contain an exception for a person who is on the call, which is why one party consent is the standard in the majority of states. Row by row detail, including the citation for each state, sits on the state law page.
The states that went further treat a participant as capable of invading privacy too, so they ask for agreement or notice from everybody on the line. Both positions are still on the books, which is why the map stays mixed.
What counts as being a party
A party is somebody actually on the call. Ownership of the phone, the account, or the building has nothing to do with it.
Your agents are parties to every call they handle, which is the entire federal answer for a business recording its own customers. A supervisor who joins a live call is on it as well. Somebody who leaves a device running in a room and walks out sits in the other category, where most of the criminal cases here come from.
The clean version holds until you try it on a call with five people, one of them dialed in from a car with a passenger listening, and the definition does less work than it looked like it would. An extension left off hook raises the same problem. Both belong with a lawyer rather than with a QA vendor.
We build software that scores calls after they end, and a transcript has nothing to say about who was authorized to be on the line. Audio tells you who spoke. Authority over the line is a fact about your phone system and your policies, and you will not find it in the recording.
The rule stops at the state line
Whatever standard you rely on describes your state. The person who answered is sitting somewhere else, possibly under a statute that wants more than your agreement.
Nothing printable decides which state governs when the two ends disagree, and courts have not landed in one place on it. What operators do is work to the strictest state touching the call, which costs a sentence at the front and retires the routing problem. Branching by area code is the shortcut people reach for, and it stopped being reliable once people started keeping their cell numbers when they moved.
Recording it and using it are two different permissions
Federal law carries separate prohibitions on disclosing and on using the contents of a communication, at 18 USC 2511(1)(c) and (d). Both attach to a person who acts "knowing or having reason to know that the information was obtained through the interception of a wire, oral, or electronic communication in violation of this subsection." An unlawful recording therefore produces fresh exposure every time it gets forwarded or acted on.
A lawful recording looks like the opposite, and people assume it comes with no strings, which is wrong in a boring way rather than a dramatic one. What you may do with the file comes out of your agreements instead of the wiretap statute: the client contract that says who owns recordings of calls taken in their name, the business associate agreement behind a medical account, the retention schedule governing how long the audio lives. HIPAA and recorded calls sits on top of a perfectly legal recording, and so does call recording retention.
How it shows up is mundane. Somebody clips thirty seconds of a customer call into a sales deck, or a supervisor emails a recording to a client to win an argument about a message, and the consent standard had no opinion about either move.
Which states use the one party rule
Each state's standard lives in one place, every row carrying a statute citation and the date somebody last read it, in call recording laws by state. What you want from it is one row, or the handful covering the states your floor dials into.
No count of all party states appears on that page, on purpose, since published counts disagree depending on how a couple of statutes get read. A number that moves with the reader is worse than no number when a compliance officer is the one asking.
Frequently asked questions
What does one party consent mean?
A recording is lawful under the statute when one participant agrees to it, and you count as that participant when you are on the call. So you can record a call you are part of without announcing it, subject to what the states touching the call require.
Can you record if you are in a one party state and the other person is not?
No clean rule answers that, and courts have gone different directions on which state's law applies. Anyone making these calls regularly works to the strictest state touching the call.
Does one party consent let you share the recording?
Recording and sharing get governed separately. Consent law says whether the recording could lawfully be made, and contracts, privacy rules, and your own policies decide who may hear it.
How many states are one party consent states?
Published counts disagree, which is why no count appears here or on the state table. A few statutes turn on whether the recording was secret rather than on counting participants, and sources split on where those belong. Check the specific states you call into instead.
The version of this question a business actually has
A company recording customers at scale ends up reading a disclosure on every call no matter which column its own state sits in. Some fraction of callers are in all party states, an account script cannot branch on that reliably, and the line costs about four seconds. Once it is on every call, the consent standard where your office sits stops being the thing you manage, and an evidence question takes its place. Knowing the disclosure is written into the account script tells you nothing about the calls already sitting in storage.
Say eight agents take 1,100 calls a month each, so 8,800 calls, and the line is missing from three percent of them. That is 264 calls where your written policy and your stored audio tell different stories, and two scored calls per agent per week will never find them.
A required phrase is the kind of criterion a machine checks reliably against a transcript, with a timestamp on the moment the agent read it or the silence where it belonged, which is why a missing disclosure sits on a scorecard as a critical fail rather than a few points off. Scoring anything that turns on tone stays shakier, and no QA tool has an opinion on whether the wording you picked is lawful where you dial. The five versions of the line live in your recording disclosure script.
One person with one call and no script to manage is done at the table plus a conversation with a lawyer. For the floor version, a call review runs six months of your own recordings against the disclosure wording you approved and hands back every call missing it, at a fixed pilot price.
Sources
- 18 USC 2511(2)(d), the consent exception for a party to the communication. Read on uscode.house.gov on 2026-09-12. Verified from primary text.
- 18 USC 2511(1)(c) and (d), the disclosure and use prohibitions. Read on uscode.house.gov on 2026-09-12. Verified from primary text.
- State consent standards and citations for all 50 states and DC. Held on the state law page, each row with its own review status.
- Published counts of all party consent states. Secondary sources, disputed, so no count appears here.
- Party exception language in most state wiretap statutes. Summarized from the state law page, where each row carries its own citation and review status.
- The strictest state practice on an interstate call. General operator practice, unverified, routed to counsel.
- Rule based criteria scoring more reliably than criteria turning on tone. Third party, unverified.