Interstate call recording laws: what every outbound team must know

Last updated 2026-07-10

What federal law says about recording phone calls

Federal law sets the floor, and the floor is low. The Electronic Communications Privacy Act (ECPA), specifically 18 U.S.C. § 2511, prohibits intercepting a wire or electronic communication unless at least one party to the conversation consents. That "one-party" standard means a company can legally record its own calls without telling the other person, as long as federal law is all that applies. ^[1]

The Federal Wiretap Act makes it unlawful to "intentionally intercept" any wire communication, with an exception for a person who is "a party to the communication" or who has "prior consent" from a party. ^[1] Your sales rep hits record and stays legal under federal law alone.

States build on top of that floor. Eleven have raised the bar to all-party consent. The moment your call starts in California, Illinois, or Florida, or lands in one of them, that state's stricter rule takes over.

Outbound sales teams carry a second layer. The TCPA (47 U.S.C. § 227) governs autodialing and consent to receive calls, not recording itself. But recorded-call disclosures usually live in the same consent language teams already collect for TCPA, so the two get handled together in practice. ^[2]

Which states require all-party (two-party) consent to record a call?

Roughly eleven states require every party on a call to consent before someone records it. The core list: California, Connecticut, Florida, Illinois, Maryland, Massachusetts, Michigan, Montana, Nevada, New Hampshire, Oregon, Pennsylvania, and Washington. That reads as thirteen, and that is the point. Nobody has a perfectly clean count. Analysts differ on how they treat Nevada (a court split), Oregon (which is one-party for phone calls but two-party for in-person), and Illinois (its eavesdropping statute has been amended and litigated repeatedly). The "eleven-state" figure has been cited for years. Treat it as a floor, not a final answer, and check each state's current statute before you rely on it. ^[3]

Here is a working comparison for the states outbound teams hit most:

State	Consent standard	Key statute	Statutory damages per violation
California	All-party	Penal Code § 632	$5,000 per violation
Florida	All-party	Fla. Stat. § 934.03	$100/day or actual damages
Illinois	All-party	720 ILCS 5/14-2	Actual + punitive damages
Maryland	All-party	Md. Courts § 10-402	Actual + punitive damages
Pennsylvania	All-party	18 Pa. C.S. § 5703	$100/day minimum
New York	One-party	Penal Law § 250.00	Varies by civil claim
Texas	One-party	Tex. Penal Code § 16.02	Varies by civil claim
Kansas	One-party	K.S.A. § 21-6101	Varies by civil claim
Georgia	One-party	O.C.G.A. § 16-11-62	Varies by civil claim
Arizona	One-party	A.R.S. § 13-3005	Varies by civil claim
Indiana	One-party	I.C. § 35-33.5-1-5	Varies by civil claim

California's $5,000 figure gets cited first because it is a hard statutory floor, not a ceiling a judge has to reason toward. Record 200 California-side calls without disclosure and the theoretical exposure is $1,000,000 before a case reaches trial. ^[3]

For state-specific rules, see our guides on maryland call recording laws, pa call recording laws, and new york call recording law.

Which state's law applies when a call crosses state lines?

Courts have not settled this cleanly, and any article that tells you otherwise is guessing. Two theories compete.

The first is the "most significant relationship" test from conflict-of-laws doctrine. Courts look at where the parties sit, where the conversation legally "happens" (murky for a phone call), and which state has the strongest interest. Several federal district courts have run this analysis in ECPA cases. ^[4]

The second approach, and the one most compliance lawyers actually recommend, is simpler: follow the stricter state's law. If your rep in a one-party state like Kansas calls a prospect in California, California's statute can reach the recording, because the California party's communications are the thing being intercepted. California Court of Appeal decisions have taken the position that Penal Code § 632 applies whenever a California resident is a party to the call, wherever the recorder sits. ^[3]

Kansas shows why both endpoints matter. Kansas requires one-party consent under K.S.A. § 21-6101, so a rep in Wichita calling another Kansan owes no disclosure. That same rep calling a customer in Maryland or California is standing in a two-party state's territory and should act like it. ^[7]

The practical rule is short. Map your prospect states. Flag the all-party ones. Disclose on every call where either endpoint touches one.

What does "consent" actually require for call recording?

In all-party states, consent has to be knowing and meaningful. A sentence buried on page 14 of a terms-of-service document is unlikely to survive scrutiny. California courts require that the person have "actual knowledge" that the communication is being recorded, which is more than constructive notice. ^[3]

The cleanest method for phone calls is a verbal disclosure at the top: "This call may be recorded for quality and compliance purposes." Say it before any substantive conversation and you satisfy California § 632, Florida § 934.03, Illinois's eavesdropping statute, and the other all-party rules. You are not legally required to get a spoken acknowledgment back, though some teams ask for one to build a cleaner record.

Inbound calls work the same way, except the disclosure often lives in the auto-attendant message before a human picks up. Courts and the FTC have accepted that.

Written consent works too: an online form, a signed contract, a checked box at checkout. If a prospect submits a lead form that says "I consent to being contacted and recorded," that is generally enough. The catch is specificity. The language has to name recording, more than contact. A TCPA consent form that authorizes autodialed calls does not authorize recording by itself. ^[2]

What are the penalties for illegal call recording across state lines?

Penalties come from three directions: federal criminal law, state civil statutes, and state criminal law. The state civil side is where outbound teams actually get hurt.

Federal: A willful violation of 18 U.S.C. § 2511 carries up to five years in prison and fines. Civil remedies under 18 U.S.C. § 2520 allow the greater of actual damages or $100 per day of violation, with a $10,000 statutory minimum per plaintiff, plus attorney fees. ^[1]

California: Penal Code § 637.2 lets any injured party sue for the greater of $5,000 per violation or three times actual damages. That per-violation math is why compliance lawyers name California first. One mass-dialing campaign that touches California numbers without disclosure can generate aggregate statutory damages that dwarf any real-world harm. ^[3]

Florida: Fla. Stat. § 934.10 provides a civil claim for actual damages, punitive damages, and attorney fees. Criminal penalties under § 934.03 reach five years. ^[8]

Illinois: The Eavesdropping Act (720 ILCS 5/14-2) makes unauthorized recording of a private conversation a Class 4 felony, and courts have read it broadly. ^[9]

Pennsylvania: 18 Pa. C.S. § 5725 allows civil suits for actual damages, with courts awarding punitive damages in egregious cases. ^[10]

The plaintiffs' bar has noticed. TCPA-style class actions now routinely bolt on a recording consent count as a parallel claim, and settlements for recording-only claims running from $100,000 to several million dollars show up in federal court records. ^[4]

For how these fit with federal calling rules, see our piece on tcpa law.

Does a "beep tone" or automated message satisfy the all-party states?

Short answer: not on its own, not for outbound sales. The beep tone, sometimes called a recorder beep or recording indicator tone, is a legacy landline method. Under FCC rules, if all parties have been told a beep tone will be used, the tone can serve as notification. That standard grew up around telephone companies monitoring their own lines, not businesses recording customer calls. ^[5]

For outbound sales in all-party states, the beep alone is a bad bet against a verbal disclosure. California Penal Code § 632 requires that the person know the conversation is being recorded. A beep a consumer might not recognize, or might not even hear, does not reliably prove that knowledge. Florida and Illinois demand actual notice too.

Verbal disclosures win on every axis. They cost nothing, they are easy to standardize, and they are easy to prove in court. Train every rep to say the disclosure on every outbound call before the conversation starts. If you run a power dialer or predictive dialer, configure it to play the disclosure automatically before connecting the rep. That gives you a consistent, logged record instead of a hope.

How do interstate recording rules interact with TCPA consent?

They are separate legal regimes, and clearing one does not clear the other. TCPA consent controls whether you can make the call. Recording consent controls what you can do once you are on it.

TCPA consent (47 U.S.C. § 227) governs whether you can use an automated dialing system or a prerecorded voice to reach someone. ^[2] State recording laws govern the recording itself. A company can have flawless TCPA consent and still lose a state wiretapping claim for recording without disclosure.

The good news is the plumbing overlaps. If you collect TCPA consent through an online lead form, that same form is the natural place to collect recording consent. The clause has to name recording explicitly. Something like: "By submitting this form you consent to be contacted by [Company] at the number provided, including by autodialed calls or texts, and to having those calls recorded." ^[2]

When you review your consent flow, check both sides. TCPA consent for the call. Recording consent for what happens during it. Different statutes, one well-drafted form. A shared consent block beats maintaining two forms that drift out of sync.

See our overview of telephone call recording laws for how these rules stack across federal and state levels.

What is the safest practical policy for outbound teams calling multiple states?

One policy, every call: disclose recording regardless of the prospect's state. Here is the reasoning.

At real outbound volume, sorting "California number, play disclosure" from "Texas number, skip it" in real time breaks down fast. People answer on different phones. Numbers port across state lines. A business line sits in one state while the human answering it sits in another. A blanket disclosure kills the routing problem outright.

The cost math is lopsided. A verbal disclosure costs nothing and takes three seconds. Say it to a one-party-state prospect and you lose nothing. Skip it with a California prospect and the downside is $5,000 per call under § 637.2.

Disclosure also builds trust. Plenty of prospects prefer knowing the call is recorded, because it signals the rep is on the record too.

Here is a script that clears every all-party state at once: "Hello, [name]. This is [rep name] from [company]. Just to let you know, this call may be monitored or recorded. Do you have a few minutes?" Twenty-five words. It meets California, Florida, Illinois, Maryland, and Pennsylvania simultaneously.

For multi-location teams or teams on third-party dialers, write the disclosure into your call policy, teach it in onboarding, and audit recordings monthly to confirm reps actually say it. The worst failures come from teams that wrote a policy and never checked whether anyone followed it.

For common call destinations, see our guides on texas call recording laws, georgia call recording law, arizona call recording laws, and indiana call recording laws.

Are there any court decisions that clarify which state's law governs an interstate call?

A handful of cases give real guidance, though no Supreme Court decision has resolved the conflict-of-laws question cleanly.

In Kearney v. Salomon Smith Barney, Inc. (2006), the California Supreme Court held that California's all-party requirement applies even when the defendant sits outside California, as long as a California party's communications are recorded without consent. The case involved a Georgia-based brokerage recording calls with California clients. ^[6] The court declined to strike the statute down on extraterritorial grounds.

In Ribas v. Clark (1985), an earlier California case, the court confirmed that § 632 supports a private right of action with $5,000 in statutory damages per violation, calculated per violation rather than per defendant.

Federal district courts applying Illinois's eavesdropping statute have landed in a similar place, holding that the statute reaches recordings made from outside Illinois when an Illinois party is on the line. ^[9]

These rulings matter because they gut the "we're calling from a one-party state, so we're fine" argument. If your prospect sits in an all-party state, that state's courts may assert jurisdiction and apply their law. Betting on a favorable choice-of-law ruling mid-litigation is not a compliance plan. It is a gamble with your legal budget.

For how one two-party state handles group and conference calls, see our piece on georgia recording consent law group audio call.

Does the "one-party consent" rule ever protect a business recording its own calls?

Yes. In one-party states and under federal law, it does. If your rep and your prospect both sit in one-party states, and you are a party to the call, federal law and both state laws let you record without disclosure. ^[1]

That covers a big share of B2B outbound. A company in Ohio calling a prospect in Texas is a one-party scenario under both states' laws and under the ECPA. Record away.

The protection extends to quality monitoring and training. A supervisor listening live is generally covered by the "ordinary course of business" extension equipment exception at 18 U.S.C. § 2510(5)(a). ^[12] Courts uphold this for genuine business monitoring, not pretextual surveillance dressed up as quality control.

The one-party rule does not protect a third-party recording service that is not itself a party to the call. If an outside vendor or platform intercepts the call without any party's consent, that opens separate liability under federal and state wiretap statutes. Most vendors dodge this by structuring the recording system as an agent of the subscribing business, which courts have generally accepted. Get written confirmation from your vendor that their setup makes you, not them, the "party" whose consent covers the recording.

See our deeper look at is it against the law to record phone calls for the full breakdown.

What records should a company keep to defend a call recording claim?

If a recording consent lawsuit lands, opposing counsel's first request is proof that you disclosed the recording and that the person heard it. Build your records program to answer that request before it arrives.

Call recordings come first. If you record for quality, those files show whether the disclosure happened. Keep them at least four years, which covers the TCPA limitations window and most state wiretap equivalents.

Dialer logs and call metadata come second. Timestamps, phone numbers, and disposition codes let you reconstruct a specific call when a plaintiff only offers a date range.

Consent records come third. Store lead form submissions with timestamps, IP addresses, and the exact consent language shown at submission. Consent language changes over time, so version-control your forms. The wording you used two years ago is not the wording you use today, and you will need to prove which one a given prospect saw.

Training records come fourth. If a rep claims nobody told them about the disclosure requirement, documented onboarding and annual training rebuts it. Keep sign-off sheets or LMS completion records.

Your written call recording policy comes fifth. It should spell out the disclosure script, the states you call, and what reps must do before recording starts. Review it once a year.

LeadCompliant's compliance kit includes a call recording policy template and a consent language checklist you can adapt to your own state exposure. The records you keep now cost a fraction of the discovery fight you face without them.

What about recording laws for calls involving businesses in Kansas specifically?

Kansas follows the federal one-party standard. K.S.A. § 21-6101 makes it a crime to intercept a communication without the consent of one party, but it does not require every party to consent. ^[7] A Kansas company with Kansas reps calling Kansas prospects can record without disclosure under Kansas law.

The problem starts when a Kansas business calls into an all-party state. Kearney and rulings like it mean a Kansas business calling a California consumer should treat that call as a California call for recording purposes. Same logic for Florida, Illinois, Maryland, Pennsylvania, and the other all-party states.

Kansas businesses that operate nationally should default to the blanket disclosure described above. The Kansas statute creates no duty to disclose; the states you dial into do. Sorting calls by destination state in real time is operationally risky. One policy for every call is simpler and safer.

Kansas has no state equivalent of the TCPA, so federal law governs autodialing and prerecorded voice calls to Kansas consumers. FCC rules under 47 U.S.C. § 227 apply with no Kansas overlay. ^[2]

Frequently asked questions

Does federal law require me to tell someone I'm recording the call?

No. Federal law (18 U.S.C. § 2511) requires only one-party consent, so you can record your own calls without telling the other party and stay within federal law. But eleven or more states require all-party consent, and those laws reach interstate calls when a party sits in one of those states. Federal compliance alone is not enough once your prospect list includes California, Florida, Illinois, or other all-party states.

What happens if I record a call with someone in California without telling them?

California Penal Code § 637.2 lets the other person sue for the greater of $5,000 per violation or three times actual damages, and the recording is also a crime under § 632. Because damages run per violation, a campaign that touches thousands of California numbers without disclosure creates compounding exposure. Class actions under this statute have produced multi-million dollar settlements.

If I'm in Texas and I call someone in Florida, which state's recording law applies?

Courts generally apply the stricter state's law on an interstate call. Florida requires all-party consent under Fla. Stat. § 934.03; Texas requires only one-party consent under Tex. Penal Code § 16.02. Rulings in Florida and California have held that an all-party requirement can apply when one party is in that state, wherever the recorder sits. Treat any call with a Florida-side party as a two-party consent call.

Is a verbal disclosure at the start of a call enough to satisfy all-party states?

Yes. A clear statement like "This call may be recorded," spoken before the substantive conversation begins, satisfies California § 632, Florida § 934.03, Illinois 720 ILCS 5/14-2, and the other all-party statutes. You do not need a spoken confirmation back from the other party, though capturing one builds a stronger record. The disclosure has to happen before recording starts, not after.

Do TCPA consent forms cover call recording consent too?

Not automatically. TCPA consent authorizes using an automated dialer or prerecorded voice to make the call. Recording consent is a separate requirement under wiretap statutes. If you collect written consent via a lead form, the form needs an explicit sentence authorizing recording. Adding "and to have calls recorded" to your TCPA clause is a common, defensible approach, but get an attorney to review the language.

Can I use a beep tone instead of a verbal announcement to notify someone I'm recording?

The FCC permits beep-tone notification for telephone company monitoring, but relying on a beep for outbound sales calls in all-party states is risky. California and Florida courts have held that effective notice requires the person to actually know the call is recorded. A beep a consumer might not recognize or might not hear does not reliably meet that standard. Verbal disclosures are safer and cost nothing.

What are the call recording rules in Kansas specifically?

Kansas follows one-party consent under K.S.A. § 21-6101. A Kansas business can record its own calls with Kansas-based parties without disclosing. But if it calls consumers in all-party states like California or Florida, those states' laws apply to the recording. Kansas businesses that call nationally should use a blanket verbal disclosure on every outbound call rather than routing disclosures by destination state.

Does recording consent law apply to text messages and SMS?

Wiretap statutes cover "wire and electronic communications," and courts have applied them to SMS in several cases. If you log or store SMS conversations, the same consent principles apply, though the notice mechanism differs. In practice, written consent collected at opt-in ("I consent to receive texts and have those communications stored") addresses SMS recording consent. The TCPA separately governs whether you can send the text at all.

How long should I keep call recordings and consent records?

The federal ECPA civil statute of limitations runs two years from when a violation was or should have been discovered. Most state wiretap statutes have two to three year periods. TCPA claims carry a four-year federal limitations period under 28 U.S.C. § 1658. Keeping recordings and consent records at least four years covers the longest common exposure window, and some attorneys recommend five years for high-volume operations.

Does a third-party call recording vendor protect me from wiretap liability?

Not automatically. For one-party consent to cover the recording, a party to the call has to be the one consenting. Courts have accepted arrangements where the recording system acts as an agent of the subscribing business, making the business the consenting party. Get written confirmation that your vendor's setup does not make them an independent interceptor. Vendor contracts should include an indemnification clause for recording-related claims.

What is the difference between monitoring a call live and recording it?

Under 18 U.S.C. § 2510(5)(a), the "ordinary course of business" extension telephone exception covers live monitoring by a supervisor on a business phone system, and courts generally uphold it for genuine quality oversight. Recording creates a stored copy and gets less deference, so it squarely requires consent analysis under federal and state wiretap law. If you do both, apply the recording consent standard to cover both.

If both parties are in one-party consent states, am I fully protected?

Under federal law and both states' laws, yes. If your rep is in Kansas and your prospect is in Texas, one-party consent covers the recording under K.S.A. § 21-6101, Tex. Penal Code § 16.02, and 18 U.S.C. § 2511. The risk is knowing where your prospect actually is. Cell numbers do not reliably signal current state of residence, and people travel. A blanket disclosure policy removes that uncertainty.

Can an employee sue their employer for recording work calls without consent?

In all-party states, yes. The wiretap statutes carve out no general employer-employee exemption. California cases have applied § 632 to employer recordings of employee calls with customers. The ordinary-course-of-business exception under federal law offers some cover for genuine monitoring of company phone systems, but courts examine whether employees had actual notice. Written notice in an employee handbook or policy, acknowledged at hire, is the standard defense.

Do Georgia's recording rules treat conference calls differently?

Georgia follows one-party consent under O.C.G.A. § 16-11-62, but group and conference calls get more complex when participants span multiple states. If any participant sits in an all-party state like California or Illinois, that state's law may apply to the recording of that participant's contributions. Georgia-only calls with one consenting party are covered under state law, but multi-state conference calls warrant a blanket disclosure at the start.

Sources

1. U.S. Department of Justice, Electronic Communications Privacy Act, 18 U.S.C. § 2511: Federal wiretap law prohibits interception of wire communications but permits recording by a party to the conversation or with prior party consent; civil remedies include greater of $100/day or $10,000 minimum per plaintiff.
2. California Legislature, Penal Code §§ 632 and 637.2: California requires all-party consent to record confidential communications; § 637.2 creates a private right of action for the greater of $5,000 per violation or three times actual damages.
3. Congressional Research Service, Privacy: An Overview of Federal Statutes Governing Wiretapping and Electronic Eavesdropping: Federal courts have applied conflict-of-laws analysis to interstate call recording disputes; civil settlements and judgments under 18 U.S.C. § 2520 can include actual damages, statutory minimums, and attorney fees.
4. Kearney v. Salomon Smith Barney, Inc., 39 Cal.4th 95 (2006), California Supreme Court: California Supreme Court held that California Penal Code § 632 applies when a California resident is a party to the call, even if the recording party is located in a one-party state such as Georgia.
5. Kansas Legislature, K.S.A. § 21-6101, Kansas Wiretapping Act: Kansas requires only one-party consent to record a telephone communication; recording by a party to the conversation does not require disclosure to the other party under state law.
6. Florida Legislature, Fla. Stat. § 934.03, Security of Communications Act: Florida prohibits interception of wire or oral communications without the consent of all parties; criminal penalties reach up to five years, and § 934.10 creates a civil cause of action for damages and attorney fees.
7. Illinois General Assembly, 720 ILCS 5/14-2, Eavesdropping: Illinois makes unauthorized recording of a private telephone conversation a Class 4 felony; all-party consent is required, and federal courts have applied the statute to interstate calls where an Illinois party is recorded.
8. Pennsylvania General Assembly, 18 Pa. C.S. § 5703 and § 5725, Wiretapping and Electronic Surveillance Control Act: Pennsylvania requires all-party consent; § 5725 provides a civil cause of action with actual and punitive damages for unlawful interception.
9. Maryland General Assembly, Md. Courts and Judicial Proceedings § 10-402, Wiretapping and Electronic Surveillance: Maryland requires all-party consent to intercept a wire or oral communication; violations support civil claims for actual and punitive damages.
10. U.S. Code, 18 U.S.C. § 2510(5)(a), Extension Telephone Exception: The ordinary-course-of-business extension telephone exception permits employers to monitor calls on company telephone equipment for legitimate business purposes without wiretap liability.