Last updated 2026-07-09
TL;DR
Federal law lets you record a call as long as one party consents, and that party can be you. But roughly 13 U.S. states require all-party consent, meaning everyone on the line has to agree first. If your call touches one of those states, the stricter rule wins. California statutory damages run $5,000 per recorded call. Know which standard governs before you hit record.
What is one-party consent for call recording?
One-party consent means only one person on the call has to agree to the recording, and that person can be you. You don't have to tell the other party, ask permission, or play a beep tone. The federal wiretap statute, 18 U.S.C. § 2511(2)(d), lets a person intercept a wire, oral, or electronic communication where that person is a party and no criminal or tortious purpose exists. [1] Plain English: record your own calls freely.
Most of the country runs on this standard. About 38 states plus the District of Columbia default to one-party consent for private calls. If your rep is in a one-party state calling a prospect in a one-party state, the compliance answer is short. You own the recording. No disclosure needed.
'Simple' isn't the same as 'safe.' Guess wrong about where your prospect actually is, or catch them sitting in a two-party state at the moment of the call, and the one-party rule stops protecting you. What matters is location at the time of the call, not the area code.
What is all-party (two-party) consent and which states require it?
All-party consent, often called two-party consent even with three or more people on the line, requires every participant to know about and agree to the recording before it starts. Silence or staying on the line after a disclosure counts as implied consent in most states, but the notice has to come before any recording begins.
As of 2025, these states have statutes requiring all-party consent for phone call recordings: California, Connecticut, Delaware, Florida, Illinois, Maryland, Massachusetts, Michigan, Montana, Nevada, New Hampshire, Oregon, Pennsylvania, and Washington. [2] That's about 13 to 14 states depending on how courts read Delaware and Montana. The count moves around based on whether a court has applied an in-state requirement, so verify with an attorney for the state you're targeting.
California call recording laws are the most litigated in the country. California Penal Code Section 632 prohibits recording a confidential communication without all parties' consent. [3] The state's position is that the law applies whenever a California resident is a party, no matter where the other caller sits. See california attorney general recording phone calls consent law for that guidance.
Florida is nearly as aggressive. Florida Statute Section 934.03 tracks the federal wiretap act in many ways but requires all-party consent for in-state calls. [4] Full breakdown at florida call recording law two-party consent statute 934.03.
Michigan and Arizona need their own analysis. Michigan reads as an all-party state. Arizona follows one-party rules with a few wrinkles. Check both before you build a recording workflow. See michigan call recording laws and arizona call recording law one party consent.
Which law applies when calls cross state lines?
This is the question that trips up outbound teams more than any other. There's no single nationwide rule, but courts have generally applied the stricter state's law when a call crosses state lines. [5]
Say your rep is in Texas (one-party) and calls a prospect in California (all-party). Most courts and practitioners treat California's law as controlling, because a California resident is on a call they reasonably expect to be private. The California Supreme Court in Kearney v. Salomon Smith Barney (2006) held that California's recording law reaches calls made into California even by out-of-state businesses. [3]
The safe operating rule is blunt: if a call can reach an all-party state, apply that state's consent standard to it. Skipping a two-second disclosure to save time is a bad trade when the downside is $5,000 per California call.
One note on area codes. A prospect's area code tells you their original phone number, not where they're standing right now. A 312 (Chicago) number could be in Miami when you dial. Most programs combine the CRM-stated address with the area code as a best-effort proxy. It isn't legally airtight, but it's the reasonable standard most businesses use.
Does the TCPA cover call recording consent specifically?
No. The Telephone Consumer Protection Act (47 U.S.C. § 227) governs autodialers, prerecorded messages, and do-not-call rules. [6] It says nothing about whether you have to disclose that a live call is being recorded.
Federal recording consent comes from the Electronic Communications Privacy Act (ECPA), specifically the federal wiretap statute at 18 U.S.C. § 2510 et seq. [1] State wiretap and eavesdropping laws stack on top of that.
The FCC has issued rules under the TCPA requiring artificial or prerecorded voice calls to identify the caller, but those rules don't touch real-time recording of live conversations. [7] So a real compliance program runs two frameworks side by side: TCPA and FCC rules for how you initiate and automate calls, and federal-plus-state wiretap law for whether and how you can record them.
For robocall-specific consent under the TCPA, see robocall consent requirements federal law.
What are the penalties for recording a call without proper consent?
They're real and they stack. At the federal level, the ECPA allows civil damages of the greater of actual damages or $100 per day, up to $10,000, plus punitive damages and attorney's fees. [1] Criminal penalties reach five years in prison for intentional violations.
State penalties run wider and often bite harder than federal law in practice. California Penal Code § 637.2 gives the injured party a private right of action for $5,000 per violation or three times actual damages, whichever is greater. [3] Since each recorded call is typically one violation, a team that recorded 200 California calls without consent faces $1,000,000 in statutory damages before any punitive multiplier.
Florida Statute § 934.10 allows civil suits for $100 per day or $1,000 per violation. [4] Illinois, under the Illinois Eavesdropping Act (720 ILCS 5/14), treats certain unauthorized recording as a Class 1 felony, though the Illinois Supreme Court's 2014 People v. Melongo decision narrowed some of the criminal exposure. [8]
Plaintiff's attorneys like recording claims because the damages are statutory. You don't have to prove you were harmed. That's the same dynamic that makes TCPA suits popular, and it's why recording class actions get filed regularly in California and Florida.
The table below shows penalty ranges across the most common jurisdictions:
How do you give proper notice that a call is being recorded?
Two methods dominate: a verbal disclosure and an automated beep tone.
The verbal disclosure is the line you hear on every customer service call. 'This call may be recorded for quality and training purposes.' Spoken clearly before any substantive conversation, it satisfies the disclosure requirement in most all-party states once the other party keeps talking. Implied consent from continuing the conversation is generally accepted, though some practitioners add 'by remaining on the line, you consent to this recording' for extra clarity.
A beep tone is a short audible tone that repeats every 15 seconds or so during recording. It's an older method, and some state laws still accept it as valid notice. California has recognized it under PUC General Order 107-B, though verbal disclosure is the more common practice now. [12]
Timing is everything. The disclosure has to land before recording starts. If your system auto-records the instant the call connects and the disclosure plays two seconds later, you've got a gap. Confirm with your telephony vendor that recording starts only after the disclosure audio finishes, or build in a short delay.
If you run a dialer or call center platform, get written confirmation from the vendor that the system supports consent-first recording. Don't assume it does.
Do call recording laws apply to text messages and voicemails?
Voicemails are generally treated as stored communications under the Stored Communications Act (18 U.S.C. § 2701), not as live interceptions. [9] Accessing someone else's voicemail without authorization is illegal, but leaving a voicemail doesn't trigger real-time recording consent, because you're creating the stored message rather than intercepting anyone's communication.
Text messages sit in the same stored-communication bucket. The ECPA's wiretap provisions cover interception in transit; SMS sitting in an inbox falls under the SCA. Most wiretap-based consent statutes don't govern retaining your own outbound texts, since those are records you made.
Monitoring or capturing a consumer's inbound texts without authorization is a different animal and can run into the SCA or state privacy law. Logging a two-way SMS conversation in your CRM is generally fine, because you're a party to the exchange. Intercepting someone else's SMS thread is not.
For outbound teams, the short version: standard logging of your own outbound and inbound messages is fine. Recording live voice calls carries the consent requirements described in this article.
How does this apply to international calls, like UAE or Algeria?
U.S. recording consent laws apply to U.S. persons and U.S.-based calls. Once your team dials internationally, the destination country's laws come into play.
The UAE has strict telecommunications and privacy rules. Recording a phone call without the other party's consent is generally illegal under UAE federal law and can expose both the recorder and anyone who receives the recording to criminal liability. [10] See uae law recording phone calls without consent illegal for the specific provisions.
Algeria handles recording and admissibility differently again. algeria law recording phone call without consent admissible evidence covers whether a recording made without consent can even be used in a legal proceeding there, which changes how businesses document disputes.
For most U.S.-based outbound teams, international recording is a niche problem. If you run offshore call centers or have reps dialing into the Middle East or North Africa, get local counsel before you record anything.
What should your call recording policy actually look like?
Most compliance officers land on the same answer: treat every call as if all-party consent applies. Segmenting by state is a lot of overhead, the location data is imperfect, and the cost of getting California or Florida wrong is brutal.
A workable policy has four parts.
First, a standard verbal disclosure at the start of every outbound call. Write one sentence, drop it into the dialer script, and train every rep to say it before anything else. 'This call is being recorded' is enough in most states. Some teams prefer 'This call may be recorded' because it covers calls where recording fails. Either works for consent.
Second, a recording start delay. Set your telephony system so recording begins only after the disclosure audio completes. Write this down in your technical documentation.
Third, a state routing flag. Even under a uniform all-party standard, tag calls by the prospect's state of record so you can audit and pull recordings fast when a complaint lands.
Fourth, an annual review. Recording laws change. Illinois has amended its statute more than once. State attorneys general issue new guidance. Set a calendar reminder to review the policy and your vendor's setup every year.
LeadCompliant's free compliance kit includes a call recording disclosure checklist and a state-by-state consent reference you can hand your ops team without paying for a full legal review.
Are there exceptions to all-party consent requirements?
Yes, and they matter for a few specific industries.
Law enforcement exceptions are common. Police and federal investigators can record calls under court-authorized wiretap orders without the parties' consent. That doesn't touch sales teams, but it's why all-party statutes carry carve-outs.
Financial services and broker-dealers are often required by FINRA and SEC rules to record and retain calls. FINRA Rule 3170 (the taping rule) requires certain broker-dealers to record all telephone conversations. [11] Courts have held that industry-specific recording mandates can preempt or provide a defense against state all-party claims, but that's not guaranteed and it varies by jurisdiction.
Emergency and 911 calls are typically exempt from consent requirements.
Consent buried in terms of service is a gray area. Some businesses argue a prospect who once signed a form saying 'calls may be recorded' has already consented. Courts are skeptical of using prior written consent as blanket authorization for all future calls, especially in California. Don't lean on it.
Calls between two business entities sit in a different posture, particularly in states where the privacy expectation for B2B calls is lower. But California has applied Section 632 to B2B calls involving individual employees, so commercial context doesn't erase the requirement.
What's the single biggest mistake outbound teams make with call recording?
Assuming the disclosure plays. Sounds mundane. It's the source of most real exposure I've seen described in complaints and lawsuits. The disclosure language sits in the script. The dialer is supposed to play it. Then someone upgrades the telephony software, the recording-start trigger shifts, and for three months every call records from the first ring with no disclosure. Nobody catches it until a plaintiff's attorney sends a demand letter.
The fix is operational, not legal. Test your recording disclosure on a live call at least monthly. Have someone call in from a personal cell and confirm they hear the disclosure before any agent speaks. Log the test. Date it.
The second biggest mistake is having no written policy at all. If you're sued, the first discovery request asks for your written call recording policy, your training records, and your consent architecture documentation. 'We told reps verbally' is not a policy. A one-page document, signed off by whoever owns compliance, showing you have a process, is meaningful evidence of good faith.
LeadCompliant's tools include a free state consent status checker at leadcompliant.com that maps your prospect list's states before you build a disclosure workflow.
Frequently asked questions
What is the difference between one-party and two-party consent for call recording?
One-party consent means only one person on the call needs to agree to the recording, and that person can be you. Two-party (all-party) consent means every person on the call must know and agree before recording starts. About 13 states use all-party consent. The federal default under 18 U.S.C. § 2511(2)(d) is one-party. When a call crosses into an all-party state, that stricter standard typically controls.
Can I record a phone call in California without telling the other person?
No. California Penal Code Section 632 prohibits recording a confidential communication without the consent of all parties. A single unannounced recording can expose you to $5,000 per violation under Section 637.2, plus civil lawsuits. You must disclose and get consent, or at minimum play a clear disclosure before the conversation and document that the party continued the call afterward.
Which states require all-party (two-party) consent for call recording?
As of 2025, the all-party consent states include California, Connecticut, Delaware, Florida, Illinois, Maryland, Massachusetts, Michigan, Montana, Nevada, New Hampshire, Oregon, Pennsylvania, and Washington. The exact count can shift based on court interpretations and statutory amendments, so verify current status for any state where you run a high-call-volume program.
Does TCPA require you to disclose that a call is being recorded?
No. The TCPA (47 U.S.C. § 227) regulates autodialers, prerecorded messages, and do-not-call compliance. It does not contain a call recording disclosure requirement. Recording consent is governed by the federal Electronic Communications Privacy Act (18 U.S.C. § 2510 et seq.) and by individual state wiretap statutes, which vary significantly by state.
What happens if I record a call in a two-party state without consent?
Exposure is significant. In California, each violation carries up to $5,000 in statutory damages. In Florida, damages run $100 per day or $1,000 per violation. Federal ECPA claims allow $10,000 per violation plus attorney's fees. Illinois classifies certain violations as a Class 1 felony. Plaintiff attorneys file these as class actions frequently because damages are statutory and don't require proof of actual harm.
If I call from a one-party state into a two-party state, which law applies?
Generally the stricter state's law applies. The California Supreme Court ruled in Kearney v. Salomon Smith Barney (2006) that California's all-party consent requirement applies to calls made into California even by out-of-state businesses. Most compliance practitioners apply the all-party standard whenever one party is in an all-party state, regardless of where the caller is located.
Does a beep tone count as consent for call recording?
In some states, yes. A repeating audible beep tone during a call has historically been accepted as notification of recording in several states, including under California PUC General Order 107-B. However, a verbal disclosure before the call begins is the more widely accepted and legally cleaner method. Either way, notification must precede any actual recording of substantive conversation.
Do call recording consent laws apply to recorded voicemails I leave for prospects?
No. Voicemails you leave are stored communications you created, governed by the Stored Communications Act rather than wiretap statutes. The real-time interception rules that require recording consent don't apply to leaving a voicemail message. That said, accessing someone else's stored voicemail without authorization is a separate violation under the SCA.
Is it legal to record a business-to-business call without consent?
It depends on the state. Some states apply consent requirements only to calls where a party has a reasonable expectation of privacy, which courts have sometimes found lower in formal business settings. But California has applied Section 632 to B2B calls involving individual employees. Treating every call as subject to all-party consent standards is the only safe operating posture for teams that can't segment by call type.
How should I disclose that a call is being recorded to comply with all-party consent states?
Play or say a clear verbal disclosure before any recording starts, ideally as the first thing heard after connection. A statement like 'This call is being recorded' or 'This call may be recorded for quality purposes' satisfies the requirement in most all-party states when the other party continues the conversation. Configure your telephony system so recording begins only after the disclosure completes.
Can terms of service serve as advance consent for call recording?
Courts, especially in California, are skeptical. Prior written consent in a terms-of-service document from a separate transaction is generally not considered valid blanket consent for all future calls. For each recorded call, you should have a contemporaneous disclosure that the specific call is being recorded. Relying solely on ToS consent is a litigation risk in all-party states.
Do FINRA or SEC rules create exceptions to state call recording consent requirements?
FINRA Rule 3170 requires certain broker-dealers to record all telephone conversations, and courts have found that mandatory industry recording requirements can provide a defense against state all-party claims in some contexts. This exception is narrow, jurisdiction-specific, and not guaranteed. Broker-dealers should confirm with legal counsel whether their mandatory recording obligations preempt applicable state consent laws.
What records should I keep to prove call recording consent compliance?
Keep your written call recording policy, training records showing reps received disclosure training, telephony configuration documentation showing recording starts after disclosure, and periodic test logs confirming the disclosure plays correctly. If a complaint comes in, these four document types are exactly what discovery requests will ask for first. Date everything and store it for at least four years.
Does Arizona require all-party consent for call recording?
Arizona is generally a one-party consent state. Arizona Revised Statutes § 13-3005 prohibits the interception of wire or electronic communications without the consent of at least one party. So a participant recording their own call is lawful under Arizona law. However, if the other party is in an all-party consent state, that state's law may still apply. See the full analysis at arizona call recording law one party consent.
Sources
- Cornell Legal Information Institute, Electronic Communications Privacy Act (18 U.S.C. § 2510 et seq.): 18 U.S.C. § 2511(2)(d) allows a party to a communication to record it without notifying other parties, provided no criminal or tortious purpose exists; civil damages under § 2520 include the greater of actual damages or $100/day up to $10,000 plus punitive damages and attorney's fees
- National Conference of State Legislatures, Recording Phone Calls and Conversations: Lists U.S. states that require all-party consent for phone call recording, including California, Connecticut, Delaware, Florida, Illinois, Maryland, Massachusetts, Michigan, Montana, Nevada, New Hampshire, Oregon, Pennsylvania, and Washington
- California Legislative Information, Penal Code § 632 and § 637.2: California Penal Code § 632 prohibits recording a confidential communication without all parties' consent; § 637.2 provides a private right of action for $5,000 per violation or three times actual damages; the California Supreme Court in Kearney v. Salomon Smith Barney (2006) held the law applies to calls made into California by out-of-state businesses
- Florida Legislature, Florida Statute § 934.03 and § 934.10: Florida Statute § 934.03 requires all-party consent for recording in-state calls; § 934.10 allows civil damages of $100 per day or $1,000 per violation
- Reporters Committee for Freedom of the Press: When a call crosses state lines, courts have generally applied the stricter state's law; the committee's recording guidance documents this split-jurisdiction analysis across U.S. states
- Cornell Legal Information Institute, Telephone Consumer Protection Act (47 U.S.C. § 227): The TCPA governs autodialers, prerecorded messages, and do-not-call rules but does not directly regulate contemporaneous recording consent for live calls
- Illinois General Assembly, Illinois Eavesdropping Act (720 ILCS 5/14): Illinois classifies certain unauthorized recording violations as a Class 1 felony; the Illinois Supreme Court's 2014 People v. Melongo decision addressed constitutional limits on the statute's scope
- Cornell Legal Information Institute, Stored Communications Act (18 U.S.C. § 2701 et seq.): Voicemails and stored text messages are governed by the Stored Communications Act rather than the real-time wiretap interception provisions that require recording consent
- FINRA, Rule 3170 (Tape Recording of Registered Persons by Certain Firms): FINRA Rule 3170 requires certain broker-dealer firms to record all telephone conversations with customers; courts have found mandatory industry recording requirements can provide a defense against some state all-party consent claims
- California Public Utilities Commission, General Order 107-B: California PUC General Order 107-B has historically accepted a repeating audible beep tone as a valid notification mechanism for call recording under California law