Call Recording Laws: Two-Party Consent States (2026)

Your CSR handles forty calls a day. You suspect half the missed-call details are getting lost, the estimate follow-ups aren't happening, and the "we'll call you back" promises evaporate. Recording calls would fix all of it — coaching material, accountability, a record of what was actually promised. But the moment you hit "record," you're in the territory of wiretapping law, and the rules change at every state line. Here's how to do it legally.

This is a Hub post in the 8-system framework — the compliance foundation for recording calls across Pillar A: Capture Every Lead, Pillar B: Turn Estimates Into Signed Jobs, Pillar C: 5-Star Review Engine, and Pillar D: Full & Calm Calendar. This is general information about the law, not legal advice.

One-party vs. two-party: the only distinction that matters

US call-recording law splits states into two camps:

• One-party consent states (the majority): only one person on the call needs to know it's being recorded — and that person can be you. If you're a party to the call and you consent to your own recording, you're compliant. Roughly 35+ states plus DC work this way.
• Two-party (all-party) consent states: everyone on the call must consent to the recording. Recording without the other party's knowledge can be a criminal offense, not just a civil violation. This is the list you need memorized.

The critical detail: the stricter state's law generally applies when a call crosses state lines. If you're in a one-party state and your customer is in a two-party state, record as if you're in the two-party state. For contractors near state borders — and anyone with customers who kept their old area codes — this matters constantly.

The two-party consent states (2026)

The states generally understood to require all-party consent for recording calls include:

• California — the big one. Strict all-party consent, and aggressively enforced.
• Florida — all-party consent; also the strictest texting-law state, so Florida contractors live under tight rules on both channels.
• Pennsylvania — all-party consent with criminal penalties.
• Washington — all-party consent; announced recording with continued conversation can imply consent, but announce explicitly.
• Illinois — all-party consent (with some case-law nuance around reasonable expectation of non-privacy; don't rely on nuance — get consent).
• Maryland, Massachusetts, Connecticut, Montana, New Hampshire — all-party consent states with varying enforcement histories.
• Delaware, Nevada (in some contexts) — additional states often listed with all-party requirements or important caveats.

This list is a high-level summary, not a legal reference — states amend these laws, courts reinterpret them, and some states have exceptions (e.g., for certain business contexts). Verify your specific states before you record anything. The cost of being wrong here is criminal liability, not a fine you can expense.

The announcement script that covers you everywhere

The beautiful thing about the announcement approach: it works in both one-party and two-party states. If you announce recording on every call, you never need to know which state the caller is in. Here's the script:

Three requirements make the announcement legally effective:

• It plays before the conversation starts. On your phone system's auto-attendant or as the first thing your CSR says. A mid-call announcement is too late for the part already recorded.
• It's audible and clear. Not mumbled, not buried in a 45-second greeting. The standalone sentence above, delivered plainly.
• Continuing the call counts as consent. In most all-party states, when a caller hears the announcement and stays on the line, that's consent. (This is the widely relied-upon mechanism — "this call may be recorded" + they keep talking = consent.)

Put the announcement in your phone system's greeting so it's automatic — don't rely on humans remembering. Humans forget; the auto-attendant doesn't.

What you're allowed to do with recordings (and what you're not)

• Do: coach your team. The #1 legitimate use — play calls in training, score them against your phone script, catch the moments where leads leak.
• Do: resolve disputes. "You said the estimate included the disposal" — the recording settles it. Keep recordings long enough to cover your warranty and dispute window.
• Do: capture details. Addresses, gate codes, customer requests — the recording is the backup when the CSR's notes are incomplete.
• Don't: share recordings publicly. Never post a customer's call audio anywhere — not as a "funny customer" clip, not as a testimonial, not ever. That's a privacy violation and a reputation nuke.
• Don't: record calls you're not a party to. One-party consent means you must be on the call. Recording other people's conversations that you're not part of is a different (and much more serious) legal question.
• Don't: keep them forever without a policy. Set a retention period (e.g., 90 days, or through the warranty period for job-related calls) and delete on schedule. Indefinite storage of customer conversations is a breach waiting to happen.

Setting up compliant recording (the practical build)

1. Enable recording in your phone system. Most VoIP systems (RingCentral, Dialpad, and similar) have call recording as a toggle — often with the announcement message built in. Turn on both together.
2. Write the announcement into your greeting. Add the "this call may be recorded" line to your auto-attendant or CSR opening script. Test it by calling your own number.
3. Set storage and retention. Decide where recordings live (your phone system's cloud storage is fine for most shops), who can access them (you and the office manager — not the whole team), and when they auto-delete.
4. Document the policy. One page: why you record (training, quality, dispute resolution), the announcement mechanism, who can access recordings, retention period. Keep it with your other setup guides.
5. Tell your team. Your CSRs and techs should know calls are recorded, why, and that recordings are for coaching — not surveillance. The team that understands the purpose cooperates; the team that discovers it doesn't.

The coaching payoff (why this is worth the trouble)

Recorded calls are the highest-ROI training material in a home-service business, because the phone is where money is won and lost. One recorded week typically reveals:

• The exact phrases where callers go quiet (usually price, usually mishandled).
• Missed-call details the CSR didn't write down — the second issue the customer mentioned that never made it to the work order.
• Follow-up promises ("I'll call you back this afternoon") that nobody kept.
• Your best CSR's techniques, captured and teachable to everyone else.

Review two calls per CSR per week. Score them against a simple checklist (greeting, need identified, appointment offered, details captured). That's a coaching system built on reality instead of vibes.

Compliance note

This post is general information about call-recording law concepts as of 2026, not legal advice. State lists here are high-level summaries — laws change, exceptions exist, and interstate calls add complexity. Before recording calls, verify the current law for every state where you do business and consider confirming your setup with an attorney. The announcement-on-every-call approach described here is the conservative path that works across both one-party and two-party states.

Related guides in this series

Recorded calls feed every pillar: they reveal where Pillar A: Capture Every Lead leaks, how Pillar B: Turn Estimates Into Signed Jobs conversations actually go, and what Pillar D: Full & Calm Calendar scheduling sounds like from the customer's side. Pair this with the state texting-law overview for the full communications-compliance picture.

The done-for-you version

This post is part of the Leveraged Owner 8-system framework from the Starter Pack — the done-for-you version with the phone-script setup guides, the call-scoring checklist, the recording policy template, and complete setup guides for all 8 systems.

No industry statistics were used in this post. State-law summaries are high-level and change — verify current law for your states and consult an attorney before recording.

Keep building your systems

Related guides from the Leveraged Owner blog: