OMNI LAW
Call Recording Compliance for Businesses
The legal baseline: one-party, all-party, and why the difference decides everything
Your company records its sales calls and its support calls. Your customers are in forty states. No single federal rule settles whether those recordings are lawful, because recording consent is set state by state and federal law is only the floor. That is where the problem starts. A call placed from a one-party-consent state can connect to a customer sitting in a state that requires consent from everyone on the line.
This guide explains which rules apply to a company that records across state lines, how most multistate businesses answer the question through the strictest-state approach, and what a compliant recording configuration looks like day to day. It covers customer calls, employee monitoring, what exposure looks like when a company gets it wrong, and a checklist your operations and technology teams can work from. Reviewing recording practices and updating them as a company adds states is part of the ongoing compliance work this firm handles as outside general counsel.
Start with federal law. Under 18 U.S.C. § 2511, specifically § 2511(2)(d), a person who is a party to a communication may record it unless the recording is made for a criminal or tortious purpose. That is one-party consent. It is a floor rather than a ceiling, so states are free to demand more, and a group of them do.
Most states track the federal one-party rule. A minority require the consent of every participant. The common shorthand is two-party consent, but all-party consent is the accurate term, because a conference call or a support escalation can carry more than two participants and each one counts. The all-party jurisdictions a multistate recording program has to plan around, with the operative statute for each:
California: Cal. Penal Code § 632, which reaches confidential communications recorded without the consent of all parties.
Florida: Fla. Stat. § 934.03, the state wiretap provision, discussed further in our note on Florida’s recording law.
Illinois: 720 ILCS 5/14-2, the eavesdropping statute, which since its 2014 amendment reaches private conversations recorded in a surreptitious manner without the consent of all parties.
Maryland: Md. Code, Cts. & Jud. Proc. § 10-402.
Massachusetts: M.G.L. c. 272, § 99, which addresses secret interception.
Michigan: Mich. Comp. Laws § 750.539c — often grouped with the all-party states, though Michigan courts have read the statute more narrowly for participants in the conversation; the cautious course is to treat Michigan as all-party.
Montana: Mont. Code Ann. § 45-8-213, framed as a notification requirement.
Nevada: Nev. Rev. Stat. § 200.620, which addresses telephone calls.
New Hampshire: N.H. Rev. Stat. Ann. § 570-A:2.
Oregon: Or. Rev. Stat. § 165.540, which treats the two settings differently — telephone and other telecommunications may be recorded with one participant’s consent, while in-person conversations require that all participants be specifically informed. Obtaining consent for both is still the safe course for a multistate program.
Pennsylvania: 18 Pa. Cons. Stat. § 5704, the consent exception to the state wiretap prohibition.
Washington: Wash. Rev. Code § 9.73.030.
The point that matters for a business is this: the applicable rule can turn on where the participants are located, not only on where the company is based. A company headquartered in a one-party state that records a call with a customer in California or Florida may be operating under an all-party rule. Our state-by-state consumer guide covers the individual recording question separately.
The strictest-state standard: how multistate businesses actually solve this
The operational answer most companies reach is to apply the all-party standard everywhere. One configuration, one script, one policy. The reason is practical. Routing consent rules per call by geography assumes you know where each participant is sitting, and callers move, port numbers, use mobile lines, forward calls, and join from hotels and airports. Area code is not location.
In practice, all-party compliance looks like a short list of moving parts. A recorded-line announcement at the start of the call, before substantive conversation, in plain words such as this call may be recorded for quality and training purposes. An interactive voice response disclosure on every recorded inbound line, delivered before the caller reaches an agent. Consent treated as given when the caller hears the notice and stays on the line — the approach most compliance programs rely on, though states vary in how they treat it. For employment and vendor settings, written consent captured through a signed policy acknowledgment or a contract clause rather than an audio notice alone.
The alternative is geographic targeting: recording only calls involving one-party states, or applying different disclosures by caller location. Compliance programs generally reject it, for reasons worth stating plainly. It depends on location data that is often wrong, it breaks when a customer travels or when a call is transferred to a second agent, it produces inconsistent recordings that are harder to defend later, and it multiplies the number of scripts and platform settings that have to stay in sync. Applying one strict standard costs less to run and is far easier to prove.
Recording employees: meetings, monitoring, and the workplace
Employee recording is a separate question from customer recording, and companies often solve the customer side while leaving the employee side undocumented. Two different consents are in play on a monitored customer-service call: the customer’s and the employee’s. A recorded-line announcement addresses the first. The second usually comes from a written policy the employee has acknowledged, supported by the same announcement on the line. Quality-assurance listening, live coaching, and barge-in features count as monitoring too, so the policy should name them rather than describing recording alone.
Internal meetings raise the same issue without the announcement. Meeting platforms record video, audio, transcripts, and in some configurations automated summaries. A host clicking record does not by itself resolve consent for the other participants, particularly where any participant is in an all-party state. The workable habit is a spoken notice at the start of the meeting, the platform’s recording indicator left on, and a policy that says which meetings are recorded and why.
Remote and distributed workforces sharpen the problem. If your policy assumed a single-state office and your engineers now work from California, Washington, and Pennsylvania, the one-party assumption baked into an older handbook no longer matches the map. A recording and monitoring policy should say what is recorded, on which systems, for what purpose, who can access recordings, how long they are kept, and how an employee raises a question about them. Keep the acknowledgment on file with the date. This section is the framework and the documents; the state-specific analysis belongs with counsel who can look at your actual footprint.
What happens when a company gets it wrong
Exposure comes from more than one direction. State wiretap and eavesdropping statutes carry criminal penalties, and they are not all misdemeanors. In Florida, interception in violation of Fla. Stat. § 934.03 is charged as a felony under the terms of that section. Illinois eavesdropping is addressed at 720 ILCS 5/14-2, and Washington’s prohibition sits at Wash. Rev. Code § 9.73.030. Enforcement against businesses is uncommon, but the criminal framing shapes how these statutes are read.
Private litigation is the more likely path. California provides a private right of action with statutory damages under Cal. Penal Code § 637.2, and Florida provides a civil remedy under Fla. Stat. § 934.10. Statutes of that kind let a plaintiff proceed without proving out-of-pocket loss, which is what makes recording claims attractive to plaintiffs’ counsel and workable as class actions.
There is also an evidentiary cost. A recording obtained outside the applicable consent rule may be subject to a suppression or admissibility challenge, so the call you most want to show a factfinder can be the one you cannot use. Separately, a wave of claims under the California Invasion of Privacy Act, which includes Cal. Penal Code § 632 and related sections, has targeted business technologies rather than classic wiretaps: session-replay and analytics scripts on websites, chat widgets staffed or read by vendors, and call recording paired with third-party analytics. The recurring theory is that a vendor listening alongside the business is a third party to the communication. Treat that pattern as a reason to inventory tools, not as a prediction about any particular claim.
The compliance checklist
Work through these in order. Each item is one decision or one document.
Where a lawyer fits
Recording practices shift every time a company adds a state, swaps phone systems, or turns on a new analytics tool. Reviewing those practices, drafting the consent scripts and the monitoring policy, and keeping both current as the footprint grows is recurring work rather than a one-time project. That is the kind of ongoing legal support handled under an outside general counsel engagement, where the same lawyers already know your systems, your vendors, and your contracts. Omni Law P.C. serves companies in nine states, with attorneys admitted in each; bar admissions and registration numbers are listed on our attorney credentials page, and matters outside those states involve local counsel. A first conversation usually covers what you record today, which states your callers are in, and which documents are missing. To have your recording setup reviewed, call Omni Law P.C. at (844) 354-1234.
Omni Law Team
Omni Law P.C. boasts a team of seasoned legal professionals.
Contact Omni Law P.C. for Transactional, Business, and
Corporate Legal Services.
Seeking knowledgeable guidance for your business? Omni Law P.C. focuses on providing flexible and affordable legal services to businesses, executives, and founders across various industries. Our experienced attorneys have a deep understanding of corporate transactions, intellectual property, commercial agreements, and emerging technologies We offer businesses the outside counsel they need to succeed.
Whether you require assistance with contract negotiation, trademark registration, or mergers and acquisitions, we provide strategic legal advice tailored to your unique needs. Contact us today at (844) 354-1234 to see how we can provide the legal support to help you achieve your business objectives.
Frequently Asked Questions
Does my business need consent to record calls?
Yes, at minimum the consent of one party to the call, and in a group of states the consent of everyone on it. Federal law permits a party to record under 18 U.S.C. § 2511(2)(d), while states such as California (Cal. Penal Code § 632) and Washington (Wash. Rev. Code § 9.73.030) require all parties to consent.
Do we have to tell customers the call is recorded?
In any state that requires all-party consent, yes, and a clear announcement at the start of the call is the usual way to do it. Because customers call from everywhere, most multistate companies announce recording on every line rather than sorting calls by state. Montana frames its rule as a notification requirement at Mont. Code Ann. § 45-8-213.
Is one disclosure enough in every state?
One well-built disclosure can work nationwide, but only if it reaches every participant on every recorded path. A single IVR prompt is not enough when transfers, outbound dialers, callbacks, and meeting recordings bypass it. Employment and vendor settings usually call for written consent as well as the audio notice.
Can we record employee calls and meetings?
Often yes, with disclosure and a written policy, and with more care when an employee sits in an all-party state such as Pennsylvania (18 Pa. Cons. Stat. § 5704). Monitoring customer-service calls generally relies on the recorded-line announcement plus an acknowledged handbook policy. Internal meetings need a spoken notice and the platform’s recording indicator left visible.
What happens if a company records illegally?
Exposure runs three ways: criminal penalties under state wiretap statutes, private suits with statutory damages under provisions such as Cal. Penal Code § 637.2 and Fla. Stat. § 934.10, and evidentiary challenges to the recording itself. Florida treats interception under Fla. Stat. § 934.03 as a felony.
Attorney Advertising. This page provides general information and is not legal advice. Reading it or contacting Omni Law P.C. does not create an attorney-client relationship. Prior results do not guarantee a similar outcome. Statutes cited are current as of the “Last updated” date and may change; confirm current law before acting.
Publishable copy ends above this line.