Is It Illegal to Record a Phone Call Without Consent?

The short answer

Recording a phone call in the United States comes down to one legal question: how many people on that call have to agree to it. Federal law, the Electronic Communications Privacy Act (18 U.S.C. § 2511), only requires one participant's consent, and since you are a participant on your own business calls, your consent alone covers you across most of the country. Twelve states raise that bar and require every participant to agree before recording starts. Get the wrong state's rule wrong and the exposure ranges from a civil lawsuit to, in Pennsylvania, a third-degree felony carrying up to seven years [18 Pa.C.S. § 5703].

This page covers the phone-call version of the rule specifically, not in-person recording or workplace surveillance. Several states apply a different, sometimes opposite, standard once the conversation happens in a room instead of over a line, and Oregon below is the clearest example of why that distinction matters.

One-party vs. all-party consent, in plain terms

One-party consent means a call can legally be recorded as long as one person on it, and that can be the person doing the recording, knows about it and agrees. You do not have to tell the other person and you do not need their permission. That is the default rule under federal law and in 38 other states and the District of Columbia [Reporters Committee for Freedom of the Press, Reporter's Recording Guide, 2026].

All-party consent, often shortened to "two-party consent" even though the same rule applies once a call has three or more people on it, means every participant needs to know the call is being recorded and has to actually agree, not just be told after the fact. Twelve states apply this stricter rule to phone calls specifically. Running a support or sales team that calls into any of them without a disclosure step is a real legal exposure, not a theoretical one.

The 12 states that require everyone to agree

This list cross-checks the Reporters Committee for Freedom of the Press's Reporter's Recording Guide against individual state statute text on Justia, and against the court opinions cited below for the two states, Nevada and Delaware, where the statute's plain wording does not match how it is actually enforced [RCFP, 2026; Justia state statute pages, 2026].

Two states that get miscategorized constantly

Michigan and Oregon show up on most "two-party consent" lists a quick search turns up. For phone calls specifically, neither one belongs there, and getting this wrong is the most common mistake we found while researching this page.

Michigan's eavesdropping statute, MCL 750.539c, reads like an all-party law, but the Michigan Court of Appeals held in Sullivan v. Gray (1982) that a participant recording their own conversation is not "eavesdropping" under the statute's own wording, since eavesdropping means listening in on someone else's conversation. Michigan's attorney general asked a federal court to send that question back to the state's Supreme Court in 2020 (AFT Michigan v. Project Veritas); the Michigan Supreme Court declined to answer it in 2021, so Sullivan still controls [Varnum LLP, 2026; Butzel Long, 2026]. If your business is a participant on the call, which it always is when you are recording your own support line, Michigan functions as a one-party state.

Oregon splits its rule by format, it does not get stricter across the board the way some guides imply. Phone calls fall under ORS 165.540(1)(a), which needs only one participant's consent. In-person conversations fall under a separate subsection, 165.540(1)(c), which does require telling everyone in the room before recording starts. A guide that lists Oregon as all-party is describing the in-person rule and applying it to phone calls, where it does not belong.

Vermont has no dedicated recording-consent statute. Without one, courts default to the federal one-party baseline for phone calls, which is why we do not list Vermont among the twelve above, though a handful of cautious guides still flag it as all-party based on the state's separate constitutional privacy case law rather than any actual consent statute.

Nevada's rule reads one-party and works like all-party

Nevada deserves its own explanation because it runs backward from Michigan and Oregon: a statute that reads as one-party and gets enforced as all-party.

Nevada's wiretapping statute, NRS 200.620, never actually uses the words "one party" or "all parties." In Lane v. Allstate Insurance Co. (1998), the Nevada Supreme Court compared it to the state's separate in-person conversation statute, NRS 200.650, which explicitly allows one-party consent, and concluded the legislature left that language out of the phone-call statute on purpose, meaning phone calls require every participant's consent. That ruling has not been overturned and the statute has not been amended since, so Nevada still functions as an all-party state for phone recording even though the statute's plain text suggests otherwise [Lane v. Allstate Ins. Co., 114 Nev. 1176 (1998)].

Calling across state lines

Support and sales calls rarely stay inside one state, and the consent rule that applies is not always your own state's rule.

The practical standard, followed by courts and recommended by the Reporters Committee for Freedom of the Press, is that the stricter state's law controls. If your call center operates out of a one-party state but the person on the other end is in California, treat the call as if California's all-party rule applies to it. Assuming your own state's rule travels with you wherever your customers are is the single most common way support teams end up out of compliance without realizing it [RCFP Reporter's Recording Guide, 2026].

What this means for your recorded-line disclosure

None of this changes if you already play a message before every call: "This call may be recorded for quality and training purposes." That line, played and acknowledged before the recording actually captures anything, satisfies all-party consent in every state on this list, because staying on the line after hearing it counts as agreeing to it.

The mistakes that create real exposure are more specific than skipping the message entirely: recording starts a few seconds before the disclosure finishes playing, the message reaches inbound callers but outbound sales or collections calls skip it, or a call transfers to a second recorded system that never repeats the notice. Any team using a decision-tree or AI-prompted script for the rest of the call, covered in our customer service scripts guide, should still treat the recording disclosure as the one line that stays fixed and word-for-word, even where everything else on the call is flexible.

The platform setting worth checking is where the disclosure sits in the call flow, not just whether it exists. A message built into the IVR greeting, before the call reaches a live agent, satisfies consent as long as it finishes before recording starts. A message an agent reads after the call connects works too, provided the platform's recording indicator confirms capture had not begun before the caller heard it. What most often goes wrong is not that a business skips the disclosure entirely; it is that recording is toggled on per queue or per agent, a call transfers from a disclosed queue into an undisclosed one, and the second leg records with no announcement attached to it at all.

Consent and retention are separate questions, and getting the first one right does not settle the second. All-party consent law governs whether you can record a call at all. A separate set of rules, ranging from state data-retention statutes to sector-specific requirements like the CFPB's recordkeeping rules for debt collection calls, governs how long you can keep that recording and who inside your company can access it. A fully disclosed, fully consented recording can still create liability if it is kept longer than a state's privacy law allows or reaches employees who had no reason to hear it.

Two of our other guides touch this same ground from a narrower angle. Our call center software for real estate teams guide flags consent requirements for brokerages doing multi-state outreach, and our call center software for insurance agencies guide covers the same issue for agents licensed across state lines. This page is the fuller reference both of those point back to.

Frequently asked questions