Call Recording Laws for Home Service Businesses: A State-by-State Guide
Launch365 is a software company, not a law firm. Everything below is general information to help you ask your attorney better questions. It is not legal advice, and recording law changes — sometimes through legislatures, more often through courts. Before you turn recording on across your call flow, have counsel licensed in the states you operate in confirm what applies to your business.
Why this matters more for contractors than most businesses
If you run an HVAC, plumbing, electrical, or roofing company, recorded calls are how you coach CSRs on booking rate, settle “that’s not what your tech quoted me” disputes, and feed transcripts into scoring and follow-up. That value is real. So is the exposure: recording someone who never agreed to it can be a criminal offense in some states, and in others it creates a private right of action — meaning the customer, or a plaintiff’s firm trolling for them, can sue you directly.
The good news is that the fix is almost always trivial. Play a notice at the start of the call, and the overwhelming majority of your compliance problem disappears.
The two rules, and the one that actually governs you
Federal baseline. The Electronic Communications Privacy Act (18 U.S.C. § 2511) permits recording when at least one party to the conversation consents. If you’re on the call, you’re that party.
State law on top. States can be stricter than the federal floor, and a meaningful number are. In an all-party consent state, everyone on the line has to agree — not just you. “Two-party consent” is the phrase you’ll hear more often, but it’s misleading on a three-way call with a homeowner and their spouse. All-party is the accurate term.
The rule that decides it. When participants sit in different states — a Georgia dispatch office calling a homeowner in Florida, say — courts have not settled on a single answer, and different cases have come out different ways. The defensible operating assumption is that the strictest applicable state’s law governs. For a company that takes calls from anywhere, that means building your call flow to the all-party standard and stopping there. It is simpler, it is cheaper than litigating, and it costs you nothing but a five-second announcement.
How many all-party states are there?
You’ll find published lists claiming eleven, twelve, thirteen, and fifteen. They’re not contradicting each other so much as drawing the line in different places, because several states are genuinely mixed: the statute says one thing, the case law says another, or the rule changes depending on whether the conversation is by phone or face to face.
Here’s the honest breakdown as of September 2026:
Clearly all-party for phone calls, by statute or controlling case law (11): California, Delaware, Florida, Illinois, Maryland, Massachusetts, Montana, Nevada, New Hampshire, Pennsylvania, Washington.
Mixed, contested, or medium-dependent (4): Connecticut, Michigan, Oregon, Vermont.
Everything else (35 states plus D.C.): one-party consent.
For a contractor running a single call-handling policy across a footprint, the practical answer is to treat all fifteen as all-party. The distinction only matters if you have a specific reason to record without notice, and very few home service businesses do.
State-by-state reference
Current as of September 2026. Statutory citations are provided so your attorney can verify quickly. Note that a citation being current does not mean the courts’ reading of it is.
| State | Consent standard for phone calls | Notes |
|---|---|---|
| Alabama — Ala. Code §§ 13A-11-30 to 13A-11-37 | One party | |
| Alaska — Alaska Stat. §§ 42.20.300 to 42.20.390 | One party | |
| Arizona — A.R.S. §§ 13-3001 to 13-3012 | One party | |
| Arkansas — Ark. Code Ann. § 5-60-120 | One party | |
| California — Cal. Penal Code §§ 631, 632 | All parties | The most aggressively litigated state in the country. § 632 covers “confidential communications,” and California courts have read that broadly. Also the source of the CIPA wave now hitting website chat widgets and session-replay tools — see the note below. |
| Colorado — Colo. Rev. Stat. §§ 18-9-301 to 18-9-305 | One party | |
| Connecticut — Conn. Gen. Stat. § 52-570d | Treat as all parties | Mixed. The criminal eavesdropping statute is one-party; § 52-570d creates civil liability unless you give notice — verbal warning at the start of the call, a recorded announcement, or an audible beep tone. Notice satisfies it. |
| Delaware — 11 Del. C. §§ 1335, 2402 | Treat as all parties | Two statutes that don’t line up. The privacy provisions in the criminal code require all parties’ consent to intercept a private communication; the wiretap statute permits a participant to record. Because the conflict is unresolved, assume the stricter reading. |
| District of Columbia — D.C. Code § 23-542 | One party | |
| Florida — Fla. Stat. § 934.03 | All parties | Chapter 934 also carries a private right of action, which is why Florida shows up in wiretapping suits against businesses. |
| Georgia — O.C.G.A. §§ 16-11-62, 16-11-66 | One party | |
| Hawaii — HRS § 803-42 | One party | |
| Idaho — Idaho Code § 18-6702 | One party | |
| Illinois — 720 ILCS 5/14-2, 5/14-3 | All parties | |
| Indiana — Ind. Code § 35-31.5-2-176 | One party | |
| Iowa — Iowa Code §§ 727.8, 808B.2 | One party | |
| Kansas — K.S.A. 21-6101 | One party | |
| Kentucky — KRS §§ 526.010, 526.020, 526.070 | One party | |
| Louisiana — La. R.S. 15:1303 | One party | |
| Maine — 15 M.R.S.A. §§ 709, 710, 712 | One party | |
| Maryland — Md. Code, Cts. & Jud. Proc. § 10-402 | All parties | One of the strictest. Maryland courts have generally required actual consent rather than treating continued conversation after a notice as agreement. |
| Massachusetts — M.G.L. c. 272, § 99 | All parties | The statute turns on secret recording, and Massachusetts draws a hard line between actual and implied consent. Get an affirmative yes. |
| Michigan — MCL §§ 750.539a, 750.539c, 750.539g | Treat as all parties | The statute reads all-party, but Michigan courts have recognized a participant exception since 1982, reaffirmed in federal court as recently as 2026. Defensible either way, which is exactly why you don’t want to be the test case. |
| Minnesota — Minn. Stat. § 626A.02 | One party | |
| Mississippi — Miss. Code Ann. §§ 41-29-501, 41-29-531, 41-29-535 | One party | |
| Missouri — R.S. Mo. § 542.402 | One party | Phone calls only; the statute does not squarely address in-person conversations. |
| Montana — Mont. Code Ann. § 45-8-213 | All parties, unless you give notice | A clear recording announcement satisfies the statute. |
| Nebraska — Neb. Rev. St. § 86-290 | One party | |
| Nevada — NRS 200.620 | All parties | The statute reads like one-party consent, but the Nevada Supreme Court has construed it to require all parties’ consent for non-emergency calls even when a participant is the one recording. Follow the case law, not the plain text. |
| New Hampshire — N.H. RSA 570-A:2 | All parties | |
| New Jersey — N.J.S.A. 2A:156A-2 to 2A:156A-4 | One party | |
| New Mexico — NMSA 1978, § 30-12-1 | One party | |
| New York — N.Y. Penal Law §§ 250.00, 250.05 | One party | |
| North Carolina — N.C.G.S. § 15A-287 | One party | |
| North Dakota — N.D.C.C. § 12.1-15-02 | One party | |
| Ohio — Ohio R.C. 2933.52 | One party | |
| Oklahoma — Okla. Stat. tit. 13, §§ 176.3, 176.4 | One party | |
| Oregon — Or. Rev. Stat. § 165.540 | One party for phone calls | Split by medium. Phone calls are one-party under § 165.540(1)(a). In-person conversations require that all participants be specifically informed before recording starts — upheld by the Ninth Circuit en banc in January 2025. Relevant if your techs record at the home. |
| Pennsylvania — 18 Pa. C.S.A. §§ 5703, 5704 | All parties | |
| Rhode Island — R.I. Gen. Laws § 11-35-21 | One party | |
| South Carolina — S.C. Code Ann. §§ 17-30-10 to 17-30-35 | One party | |
| South Dakota — SDCL 23A-35A-20, 23A-35A-21 | One party | |
| Tennessee — T.C.A. §§ 39-13-601, 40-6-303 | One party | |
| Texas — Tex. Penal Code Ann. § 16.02 | One party | |
| Utah — Utah Code § 77-23a-4 | One party | |
| Vermont | Treat as all parties | No wiretapping statute at all. The Vermont Supreme Court has held that surreptitious recording in a home can violate common-law privacy, so the absence of a statute is not permission. |
| Virginia — Va. Code Ann. §§ 19.2-61, 19.2-62 | One party | |
| Washington — RCW 9.73.030 | All parties, unless you give notice | Notice must be announced in a way that’s recorded as part of the call itself — the statute is specific about this. |
| West Virginia — W. Va. Code § 62-1D-3 | One party | |
| Wisconsin — Wis. Stat. § 968.31 | One party | |
| Wyoming — Wyo. Stat. Ann. § 7-3-702 | One party |
What this means for the way you actually run phones
Your after-hours and overflow answering service. If a third-party answering service records on your behalf, your policy has to cover their call flow too. Michigan in particular distinguishes between a participant recording and a third party recording — a vendor recording your calls is not obviously the same thing as you recording them. Ask what announcement they play.
AI voice agents and automated receptionists. An AI agent answering and transcribing a call is still a recording under most of these statutes. The technology is new; the wiretap laws are not, and courts have generally applied them without much sympathy for “but it’s an AI.” Announce it the same way you’d announce a human recording.
Transcription is recording. If you’re generating transcripts for CSR scoring or pulling call content into follow-up automation, that’s covered. Turning off audio storage but keeping the transcript does not change the analysis.
Your techs in the field. Oregon’s in-person rule, and the general patchwork around face-to-face recording, is a different question from your office phone lines. If techs record at the home — for damage documentation, or to capture a verbal approval — that needs its own policy.
Your website, not just your phones. California’s CIPA and Florida’s Chapter 934 are being used right now against businesses over website chat widgets, session-replay scripts, and ad pixels — the theory being that a third-party script listening in on a visitor’s session is an intercepted communication. If you’re tightening up call recording, it’s worth auditing what’s running on your site at the same time.
Turning on the recording announcement in Launch365
Launch365 can play an announcement automatically at the start of inbound and outbound calls, so consent is captured on every call without your CSRs having to remember.
Go to Settings → Phones and confirm the recording announcement is enabled for both inbound and outbound. We include a default announcement; you can upload your own if you’d rather match your brand voice or cover something specific your attorney wants said.
One catch: the announcement setting only appears once recording and transcription are already turned on. If you don’t see it, enable recording first.
Internal note — confirm this navigation path against the current Launch365 UI before publishing. I’ve written it generically; swap in the exact menu labels and add a screenshot.
Practices worth adopting regardless of your state
Announce it everywhere, not just where it’s required. Running one policy across your whole footprint means nobody has to think about where the caller is. It also removes the single most common way this goes wrong — a CSR making the judgment call in the moment and getting it wrong.
Make the announcement plain. “This call is recorded” is better than “this call may be monitored or recorded for quality and training purposes.” Ambiguity is what gets litigated. The stricter states care whether the person actually understood.
Get the announcement into the recording. Washington requires it, and in every other state it’s your evidence. If the notice plays before the recording starts, you can’t prove it played.
Have people identify themselves on multi-party calls. When a homeowner loops in a spouse, a property manager, or an insurance adjuster mid-call, everyone new needs to have heard the notice — and you want the recording to show who was on the line.
Speak clearly and confirm the important things out loud. Recordings earn their keep at the moment a customer disputes a quote. Restating the price, scope, and approval verbally makes the transcript actually useful.
Write the policy down. Document when you record, who can access recordings, how long you keep them, and what triggers deletion. Retention is its own liability — recordings you no longer need are recordings that can be subpoenaed.