Last updated 2026-07-09
TL;DR
Under federal law (18 USC 2511), you can record a phone call if at least one party to the call consents, which can be you. But 11 states require all parties to consent. If you make outbound calls across state lines, you need to know both layers. Violations can trigger criminal charges and civil suits with statutory damages up to $10,000 per violation.
What does federal law actually say about recording phone calls?
The core federal rule sits in the Electronic Communications Privacy Act of 1986, specifically 18 USC 2511. [1] The statute makes it a federal crime to intentionally intercept any wire, oral, or electronic communication. The exception that saves most businesses is consent: 18 USC 2511(2)(d) says interception is lawful when "one of the parties to the communication has given prior consent."
That single sentence is the whole ballgame for most outbound sales teams. You are a party to your own calls. So if you record a call you are personally on, you satisfy the one-party consent requirement under federal law without telling the other person anything. Lawyers call this the participant exception.
A few things that rule does not cover. It does not let you secretly record calls you are not on. It does not shield you from state law, which often runs stricter. And it does not address the FCC's separate beep-tone notification rule, which applies to telephone companies, not to businesses recording their own calls. [2]
The federal penalty for violating 18 USC 2511 includes up to five years in prison plus civil damages of the greater of actual damages or $100 per day of violation, with a $10,000 minimum per violation. [1] That $10,000 floor matters. One improperly recorded call can cost more than you think.
What is the difference between one-party and all-party consent?
One-party consent means only one person on the call needs to know about and agree to the recording. That person is usually you, the one doing the recording. Simple.
All-party consent (sometimes called two-party consent, though it really means every party) means every person on the call must agree before you hit record. If you are on a three-way call in an all-party state, all three people have to consent.
Federal law sets the floor at one-party consent. States can and do go higher. Eleven states currently require all-party consent: California, Connecticut, Florida, Illinois, Maryland, Massachusetts, Michigan, Montana, New Hampshire, Oregon, and Washington. [3] Pennsylvania is sometimes counted as all-party too, though its courts have split on the question, so treat it as all-party to stay safe. See our full breakdown of pa call recording laws.
The practical problem for outbound teams is that you almost never know where your contact is sitting when they answer. A prospect with a 212 area code might be on a couch in Los Angeles. The law that controls is the law of the state where the call is recorded or received, and courts in different jurisdictions disagree on how to apply that when the parties sit in different states.
Safe default: if you call anyone in a state on the all-party list, treat that call as requiring all-party consent.
Which states require all-party consent for recorded calls?
Eleven states require all-party consent, and Pennsylvania is a twelfth you should treat that way. Here is a quick reference table. States not listed follow the federal one-party default, though you should verify current local law before assuming that.
| State | Consent standard | Statute |
|---|---|---|
| California | All-party | Penal Code 632 |
| Connecticut | All-party | CGS 52-570d |
| Florida | All-party | F.S. 934.03 |
| Illinois | All-party | 720 ILCS 5/14-2 |
| Maryland | All-party | Cts. & Jud. Proc. 10-402 |
| Massachusetts | All-party | MGL c. 272 s.99 |
| Michigan | All-party | MCL 750.539c |
| Montana | All-party | MCA 45-8-213 |
| New Hampshire | All-party | RSA 570-A:2 |
| Oregon | All-party | ORS 165.540 |
| Washington | All-party | RCW 9.73.030 |
| Pennsylvania | All-party (treat as) | 18 Pa. C.S. 5703 |
For state-specific breakdowns, check out maryland call recording laws, georgia call recording law, new york call recording law, and texas call recording laws.
Georgia and New York follow the one-party federal standard, but their laws carry nuances around group calls and recorded announcements. Arizona is one-party too, with its own twist on consent notification that trips up some auto-dialers. See arizona call recording laws and georgia recording consent law group audio call for those specifics.
Indiana is one-party but worth a separate look if you run high-volume auto-dialing in the Midwest. Indiana call recording laws covers that ground. The broader landscape of telephone call recording laws across all 50 states pairs well with this article.
Does federal law require you to tell callers they are being recorded?
Federal law by itself does not require you to announce a recording to the other party, as long as you satisfy the one-party consent rule by being on the call yourself. [1] No beep, no disclosure, no warning needed under ECPA alone.
There is one carve-out worth knowing. The FCC has a rule, codified at 47 CFR 64.501, requiring telephone companies to provide a beep tone or verbal notification when the phone company itself monitors or records calls. [2] That rule binds common carriers and telephone utilities, not businesses recording their own calls on their own equipment or cloud platforms.
Here is where it gets messy. Many state all-party consent laws are effectively satisfied by announcing the recording at the start of the call and continuing if the other party stays on the line. California Penal Code 632.7, for example, allows recorded calls as long as everyone is notified. So the announcement requirement is usually a state law issue, not a pure federal one.
Practical advice: record a verbal disclosure at the top of every call anyway. It costs you nothing, it satisfies most state all-party requirements, and it protects you if a prospect later claims they were secretly recorded. Something like "This call may be recorded for quality and training purposes" at the start of your introduction is enough in most jurisdictions. Most legally-reviewed sales scripts already do this.
What are the federal penalties for illegal call recording?
Criminal penalties under 18 USC 2511 run up to five years in federal prison. [1] Federal prosecutors rarely bring criminal cases against businesses for routine recording violations, but the statute is there and it has been used.
Civil damages under 18 USC 2520 are where businesses actually get hurt. The statute sets civil liability at the greater of: (a) actual damages plus any profits from the violation, or (b) statutory damages of $100 per day of violation with a $10,000 minimum. [1] Attorneys' fees go to the winning plaintiff on top of that.
State penalties layer on. California's Invasion of Privacy Act lets private plaintiffs sue for $5,000 per violation or three times actual damages, whichever is greater. [3] Illinois' eavesdropping statute allows civil suits too. Florida's Security of Communications Act provides for actual damages or liquidated damages of $100 per day, minimum $1,000.
Class actions are the real danger. A single call center recording thousands of calls without proper consent can face class exposure in the millions. California all-party consent claims have driven multiple seven-figure settlements against companies that recorded customer calls without notice. That risk shows up even when the underlying conduct looks routine.
The TCPA itself (47 USC 227) [4] does not directly regulate call recording, but TCPA lawsuits often ride alongside recording claims when a plaintiff builds a case around an outbound call program. For how these statutes interact, see our overview of tcpa law.
How does the TCPA relate to call recording rules?
The Telephone Consumer Protection Act (47 USC 227) [4] and the call recording statutes are separate bodies of law. The TCPA governs how you initiate calls: auto-dialers, prerecorded messages, Do Not Call compliance, consent to be called. It says nothing about whether you can record those calls.
The two frameworks still collide constantly in litigation. When a plaintiff sues over an improperly recorded call, their lawyer almost always combs the call records for TCPA violations too, and the reverse happens just as often. A single complaint can allege violations of 18 USC 2511, the relevant state wiretapping statute, and the TCPA at once.
The FCC has addressed consent in the TCPA context at length. Its 2023 order tightening one-to-one consent requirements for lead generation [5] made the documentation burden heavier, which means companies now need cleaner records of both calling consent and any recording consent given at opt-in.
Bottom line: you cannot treat call recording compliance as a separate silo from your TCPA program. They share the same consent infrastructure.
What are the call recording rules in Canada?
Canada follows a one-party consent model close to U.S. federal law. Phone call recording is governed federally by the Criminal Code (RSC 1985, c C-46), specifically sections 183 and 184. [6] A person who is a party to a private communication may record it without notifying anyone else. Section 184(2)(a) is the operative exception.
Canada's federal telecom regulator, the CRTC, adds notification expectations for businesses. The CRTC's general approach, set out in its guidelines on call centre practices, asks that callers be notified when calls are recorded for business purposes. [12] That is a regulatory expectation, not a criminal law requirement, but companies that ignore it invite complaints and CRTC scrutiny.
Quebec adds a layer. Quebec's Act respecting the protection of personal information in the private sector (Law 25, updated significantly in 2022 and 2023) [7] treats recorded calls as personal information and imposes collection, consent, and retention obligations beyond the federal Criminal Code. If you call Quebec residents, you need to disclose recording, state a purpose, and keep a retention policy.
For U.S.-based teams calling Canadian numbers, the safest approach is to announce the recording on every call, consistent with CRTC expectations and Quebec law. Criminal exposure under the Code for one-party violations is low, since you are a party to your own calls. The regulatory and privacy exposure under Quebec's Law 25 is the part that bites.
Canada call recording rules are not identical to U.S. rules, but the practical gap is smaller than many teams assume. The bigger cross-border risk is CASL (Canada's Anti-Spam Legislation) compliance rather than recording law, and that is a separate topic.
What are the call recording rules in Australia?
Australian recording law starts with the Telecommunications (Interception and Access) Act 1979 (Cth). [8] Section 7 prohibits intercepting a communication passing over a telecommunications system, but the Act carries a party-to-communication exemption similar to the U.S. and Canadian one-party model. A participant who records a call for their own use, without distributing it to others, generally does not violate the federal Act.
The states add their own listening devices laws, and these vary. In New South Wales, the Surveillance Devices Act 2007 lets a party to a conversation record it without others' consent, as long as the purpose is not to communicate it to a non-party. Victoria, Queensland, South Australia, and Western Australia run their own Surveillance Devices Acts with similar party-to-communication exceptions.
For businesses calling into Australia, the split between recording and distributing matters. Recording a call for your own quality review is generally fine. Sharing that recording, using it in litigation, or publishing it can trigger liability depending on the state.
The Australian Communications and Media Authority (ACMA) also expects businesses to follow the Telecommunications Consumer Protections (TCP) Code, which treats notification of recording as standard practice. [9] Like Canada's CRTC expectations, that is a code obligation, not a criminal statute, but ACMA can act against companies that systematically ignore it.
For a U.S. sales team calling Australian leads: announce the recording, store it securely, and limit distribution to people with a business need to hear it. That covers your exposure under both the federal Act and the state surveillance device laws.
How should outbound sales teams set up a legally compliant recording policy?
Here is a practical framework, not a legal opinion. Talk to a lawyer before you finalize your policy.
First, pick a universal notification standard. Say something on every call before you start your pitch. Make it a script line, not optional. Something like "This call may be recorded for quality purposes." It also improves your call reviews, because reps behave when they know recordings exist.
Second, map your contact list by state. If your lead list includes California, Florida, Illinois, or any all-party state, mark those records. Your dialer or CRM should tag them automatically. Build a workflow that runs the recording disclosure before any substantive conversation on those calls.
Third, document consent in your CRM. If your disclosure is verbal, make sure your recording system timestamps when it played. If you collect recording consent at opt-in (inbound web leads, for example), save that consent record tied to the lead.
Fourth, review your cloud phone platform's settings. Most business VoIP and contact center platforms have a recording notification feature, sometimes labeled a beep or a recorded announcement. Turn it on globally. Annoying a few prospects costs less than one class action.
Fifth, set a retention policy and keep to it. State privacy laws and CRTC and ACMA guidelines all expect one. Holding recordings forever is a liability if something goes wrong. Ninety days to one year is a common range for sales calls, longer for regulated industries.
LeadCompliant has a free compliance kit at leadcompliant.com with a call recording policy template and a state-by-state consent quick-reference to build your workflow around.
For a checklist of whether specific recording scenarios are legal in your context, the is it against the law to record phone calls guide pairs well with this one. The recorded phone call laws article goes further on how individual states treat secretly recorded calls in civil litigation.
What happens when the caller and recipient are in different states?
This is the most common source of confusion, and the most common source of liability, for outbound teams. When a caller in a one-party state calls someone in an all-party state, courts in most circuits apply the law of the state with the most significant relationship to the recording. In practice that usually means the state where the recorded party sits, which is the state you may not know about when you dial.
The Ninth Circuit, covering California, has held that California's all-party consent requirement (Penal Code 632) applies when either party to the call is in California at the time of the call. [10] That is a broad reading. A call from a New York office to a California phone number is governed by California law for recording, even when California has nothing to do with the company's operations.
Illinois courts take a similar view. The Illinois Eavesdropping Act applies when an Illinois resident is a party to a recorded call, no matter where the recorder is. [3]
The conservative and correct approach: assume that any call to a phone number in an all-party state requires all-party consent notice, regardless of where your office is. You cannot know where your prospect is physically located even if you know their area code. Build the announcement into every call as standard practice.
This is not paranoia. It is how class action lawyers find their cases. They look for recordings from companies that assumed their home state's one-party rule controlled, then show that a chunk of that call volume went to California or Florida residents.
Are there any exemptions from federal call recording rules?
Yes, a few narrow ones in 18 USC 2511. None of them is the broad "we're a business" pass people wish existed.
Law enforcement can intercept communications with a valid court order under Title III of ECPA. [1] Not relevant for businesses.
The FCC allows service observing by telephone companies to monitor calls for service quality without notifying customers, but only under specific technical conditions and only by the carrier itself. [2] Also not relevant for typical businesses.
Provider monitoring exemptions let communications service providers monitor the traffic they carry for network management. If you are a cloud phone provider, this matters to you. If you are a business customer of that provider, it grants you nothing extra.
The most practically relevant exemption is the consent-based business recording exemption. Businesses record calls for quality assurance and training under the consent exception every day. The catch is that consent has to be obtained before the recording starts, not after.
There is no general business-purposes exemption that overrides consent requirements. That is a common misconception. Recording for internal training does not waive the other party's right to know.
One more exemption worth knowing cuts the other way. The FTC's Telemarketing Sales Rule [11] requires telemarketers to disclose that calls may be recorded at the start of the call, and separately tracks consent for billing authorization calls. So a seller subject to the TSR already carries a federal affirmative disclosure duty layered on top of ECPA.
How do automated and AI call recording tools change your compliance risk?
AI transcription tools, conversation intelligence platforms, and auto-dialers with built-in recording have grown fast. The legal framework has not moved to accommodate them, and that gap is where teams get hurt.
The core problem is that AI tools often record automatically, without the user manually hitting record. If a rep never notices the feature is on, calls get recorded with no announcement. If any of those calls reached California or Florida residents, you have an all-party consent problem across your whole book.
A second problem: AI transcription services often store recordings on third-party servers, sometimes outside the U.S. If you call Canadian or Australian leads, you may have data residency duties under Quebec's Law 25 [7] or Australia's Privacy Act 1988 [9] that require personal information (recorded voice counts) to sit domestically or under equivalent protection.
Practical steps for teams using AI tools: audit your recording settings before your first call, confirm your platform plays a recording notification automatically, check where recordings are stored, and read the vendor's data processing agreement to see what they can do with your call audio.
LeadCompliant's free TCPA and recording compliance checkers at leadcompliant.com help you spot gaps in your current setup before they turn into complaints.
Frequently asked questions
Is it legal to record a phone call without telling the other person?
Under federal law (18 USC 2511), yes, if you are a party to the call. You satisfy the one-party consent requirement yourself. But in the 11 all-party states (California, Connecticut, Florida, Illinois, Maryland, Massachusetts, Michigan, Montana, New Hampshire, Oregon, and Washington), you must notify every party. Recording without notice in those states can mean civil liability of $5,000 or more per call.
Does federal law require a beep tone when recording calls?
The FCC's beep-tone rule at 47 CFR 64.501 applies to telephone companies, not to businesses recording their own calls. Federal law does not require a beep tone for ordinary business call recording. State laws in all-party consent states functionally require notification, though, and a verbal disclosure or beep tone is the standard way to satisfy that. Most counsel recommends using one on every call regardless.
What is the federal penalty for recording a call without consent?
Under 18 USC 2520, civil damages are the greater of actual damages or statutory damages of $100 per day of violation, with a $10,000 minimum per violation. Criminal penalties under 18 USC 2511 can reach five years in federal prison. Attorney's fees go to the prevailing plaintiff in civil suits. State law penalties add to this, with California allowing $5,000 per violation.
Can I record calls with customers in California if I'm based in another state?
No, not without notifying them first. California's Penal Code 632 applies when any party to the call is in California, regardless of where you are. The Ninth Circuit has consistently upheld this reading. Before any substantive conversation, you must tell the person the call will be recorded. Being in a one-party consent state yourself does not protect you from California liability.
What does Canadian law say about recording phone calls?
Canada's Criminal Code (sections 183 and 184) follows a one-party consent model, so you can record calls you participate in. But Quebec's Law 25 treats voice recordings as personal information and requires disclosure of the recording purpose, a stated retention policy, and data protection safeguards. CRTC guidelines also expect businesses to announce call recording to consumers at the start of the call.
What does Australian law say about recording phone calls?
The Telecommunications (Interception and Access) Act 1979 prohibits intercepting calls, but participants in a call can record it under the party-to-communication exemption. State surveillance device laws generally follow the same approach. The ACMA's TCP Code expects businesses to notify callers of recording. Sharing recorded calls outside the business can trigger liability under both federal and state surveillance device laws.
Do I need all-party consent if I am using an auto-dialer?
The type of dialing equipment does not change the recording consent rules. If any party is in an all-party state, all parties must consent to recording, whether the call was placed manually or by an auto-dialer. Automated systems that record without playing a notification first create systematic violations across every call placed to all-party states, which is exactly the pattern class action lawyers look for.
Does the FTC Telemarketing Sales Rule say anything about recording calls?
Yes. The FTC's Telemarketing Sales Rule (16 CFR Part 310) requires telemarketers to disclose material information about the call, and specifically for billing authorization calls, the call must be recorded and that recording must capture the customer's informed consent. This adds a federal affirmative disclosure layer on top of ECPA's consent exception for companies doing outbound telemarketing.
How long do I have to keep recorded calls?
Federal law sets no universal retention minimum for business call recordings, though specific regulated industries (financial services, healthcare, broker-dealers) have their own requirements. The FTC's TSR requires billing authorization recordings to be kept for 24 months. Best practice for general sales teams is 90 days to one year. Longer retention raises liability exposure if recordings are later sought in litigation.
What is the difference between recording and monitoring a call?
Recording creates a stored copy of the call. Monitoring means a third party listens in real time without storing the audio. Federal and state wiretapping laws treat both similarly: both require the same consent standards. Live monitoring by a manager on a sales call is still an interception under 18 USC 2511 unless at least one party (usually the rep) has consented, or unless all parties are notified.
Can employees sue their employer for recording calls without notice?
Yes, in all-party consent states. Employees in California, Illinois, Maryland, and other all-party states can bring private claims under those states' wiretapping and privacy statutes if their calls were recorded without notice, even internal business calls. Several California cases have involved employees as plaintiffs rather than customers. Internal quality assurance recording programs need to satisfy the same state consent rules as customer calls.
Does GDPR affect call recording for U.S. companies calling Europe?
Yes. If you call people in the EU, GDPR treats recorded voice data as personal data. You need a lawful basis for processing (usually legitimate interest or explicit consent), must include call recording in your privacy notice, and have obligations around data subject access requests. Recording without any disclosure likely violates both the lawful basis requirement and GDPR's transparency principle. Fines can reach 4% of global annual revenue.
What is the safest policy for a small outbound team recording calls in multiple states?
Play a recorded announcement on every outbound call before the conversation starts, regardless of the state. Something like 'This call may be recorded for quality purposes' takes three seconds and satisfies the notification requirement in every all-party state. Store recordings securely, limit access to people with a business reason, set a written retention policy, and audit your dialer or AI recording tool settings quarterly.
Sources
- U.S. Department of Justice, Justice Manual, Electronic Communications Privacy Act (18 USC 2511 and 2520): Federal law prohibits interception of wire communications; one-party consent exception in 2511(2)(d); civil damages minimum $10,000 per violation under 2520
- National Conference of State Legislatures, State Wiretapping and Electronic Surveillance Laws: Eleven states require all-party consent for call recording, including California Penal Code 632 and Illinois 720 ILCS 5/14-2; California allows $5,000 per violation in civil suits
- Cornell Legal Information Institute, Telephone Consumer Protection Act, 47 USC 227: The TCPA governs auto-dialers, prerecorded messages, and Do Not Call compliance; does not directly regulate call recording
- Government of Canada, Criminal Code RSC 1985 c C-46, sections 183-184: Canada follows one-party consent for call recording; section 184(2)(a) exempts participants from interception liability
- Commission d'acces a l'information du Quebec, Law 25 personal information protection requirements: Quebec's Law 25 (updated 2022-2023) treats recorded voice calls as personal information requiring disclosure of purpose and retention policy
- Federal Register of Legislation (Australia), Telecommunications (Interception and Access) Act 1979 (Cth): Australia's federal law prohibits intercepting communications but exempts participants recording calls; governs Australian recording phone call requirements
- Office of the Australian Information Commissioner, Privacy Act 1988 guidance: ACMA's TCP Code expects businesses to notify callers that calls are being recorded; Privacy Act 1988 applies to voice recordings as personal data
- Justia, Kearney v. Salomon Smith Barney, Inc., 39 Cal. 4th 95 (2006): California all-party consent requirement applies when any party to the call is in California, regardless of where the recording party is located
- FTC, Telemarketing Sales Rule, 16 CFR Part 310: TSR requires billing authorization calls to be recorded capturing customer consent; recordings must be retained 24 months
- Canadian Radio-television and Telecommunications Commission (CRTC), homepage: CRTC expects businesses to notify callers when calls are recorded; regulatory expectations for Canadian call recording