Meeting Recording Laws by State: The Compliance Map Nobody Cares About (But Should)

Here's the thing nobody tells you about recording laws: the rules are clear, but the tools don't make compliance easy.

Your sales rep in California records a Zoom call with a prospect in Illinois. California requires all-party consent. Illinois does too. Both states agree, so no problem, right? Now change that prospect's location to New York (one-party consent) while your rep stays in California. Suddenly the rules conflict. Your rep needs everyone's permission. The prospect doesn't. Who controls?

Most companies recording meetings have never asked this question. They turned on the recording feature, maybe saw a notification pop up, and assumed that was enough. It isn't. The legal rules around recording conversations vary state by state, and a single call between two states can create real liability.

This guide lays out what the law actually says so you can make informed decisions about your recording setup. It's not legal advice. Consult counsel for your specific situation.

One-party vs two-party consent

Federal law (18 U.S.C. 2511) sets the floor: you need the consent of at least one party to record a conversation. If you're a participant, you count as that one party. This is called one-party consent, and it means you can legally record your own calls under federal law without telling anyone.

States can be stricter. Thirteen states require the consent of all parties to a conversation before anyone can record it. Despite the common label "two-party consent," this really means every participant must know about and agree to the recording. A five-person call in California needs five people's consent, not two.

The consequences for getting it wrong range from misdemeanors to felonies. In Pennsylvania, illegal wiretapping is a third-degree felony carrying up to seven years in prison. In Illinois, it's a Class 4 felony with one to three years and fines up to $25,000. California imposes fines up to $2,500 per violation plus potential civil liability. These aren't theoretical risks; individuals and companies have been sued under these statutes.

States that require all-party consent

The table below covers the 13 all-party consent states plus Nevada (which splits its rules). All other states follow federal one-party consent rules, meaning you can record your own calls without notifying the other party.

All other states (Alabama, Alaska, Arizona, Arkansas, Colorado, D.C., Georgia, Hawaii, Idaho, Indiana, Iowa, Kansas, Kentucky, Louisiana, Maine, Michigan, Minnesota, Mississippi, Missouri, Nebraska, New Jersey, New Mexico, New York, North Carolina, North Dakota, Ohio, Oklahoma, Rhode Island, South Carolina, South Dakota, Tennessee, Texas, Utah, Vermont, Virginia, West Virginia, Wisconsin, Wyoming) follow federal one-party consent rules. Table last reviewed April 2026. Laws change. Always verify current law with legal counsel.

Your SDR in Portland records a call with a CFO in Miami. Both Oregon and Florida require all-party consent. If nobody announced the recording, both sides may have committed a felony. That's not a hypothetical. It's what happens every day on sales teams that haven't thought about this.

Cross-state calls: which rule applies?

This is where it gets messy. When a caller in Texas (one-party) joins a meeting with someone in California (all-party), which state's law governs the recording?

The short answer: nobody knows for sure. Courts have been inconsistent. Some apply the law of the state where the recording was made. Others apply the law of any state where a participant is located. A few have applied the stricter standard.

In Kearney v. Salomon Smith Barney (2006), the California Supreme Court ruled that a Georgia company recording calls with California residents had to follow California's all-party consent law, even though Georgia only requires one-party consent. The court held that California's privacy protections extend to its residents regardless of where the recording happens.

The practical takeaway: if any participant on the call is in an all-party consent state, treat the entire call as if all-party consent is required. This is the conservative approach, and it's the one most corporate legal teams recommend. Getting consent from everyone costs you nothing. Getting it wrong can cost you a lawsuit.

For companies with distributed teams, this often means every call should be treated as an all-party consent situation. If you have employees or customers in California, Florida, Pennsylvania, Illinois, or any of the other all-party states, your recording policy needs to account for that.

How meeting tools handle consent

Recording tools vary widely in how they notify participants. Some make compliance easy. Others leave it entirely to you. We dug into the specifics so you can see exactly what each tool does (and doesn't do) automatically. If you're also weighing the privacy trade-offs of free tools, we covered that in our analysis of free notetaker privacy policies.

Zoom shows a notification banner to all participants when recording starts. Participants see "Recording in progress" and can choose to leave. For cloud recordings, Zoom can be configured to require explicit consent (a pop-up each participant must click). This is one of the better built-in approaches. Zoom also lets admins customize the recording notification text, so you can include specific consent language mentioning state laws or your company's recording policy. The default text is generic, though, and most companies never change it. If you're in an all-party state, customizing that message with explicit consent language is worth the five minutes it takes.

Microsoft Teams displays a recording indicator in the meeting controls and sends a notification to all participants. The notification appears in chat and as a visual banner. Teams also announces the recording in the meeting transcript. Starting May 2026, Teams is adding bot detection that labels third-party recording bots as non-human participants, which adds another layer of visibility.

Google Meet shows a red recording indicator and notifies all participants. External participants (those outside the organizer's Google Workspace) see a consent dialog they must accept to join a recorded meeting. This is a strong compliance feature for external calls.

Gong offers the most configurable consent flows of any tool we reviewed. You can set up automatic email notifications before calls, require verbal consent at the start of recordings, and customize the consent language by region. Gong's admin panel lets you configure different consent workflows per state or per team, so your California reps can have stricter consent automation than your Texas reps. Gong also provides compliance dashboards to track consent status across all recorded calls. For revenue teams in regulated industries, this level of control matters. The setup takes time, but once configured it runs without manual intervention.

Otter.ai, Fireflies.ai, and Fathom join meetings as bot participants. The bot's name typically includes a recording indicator (e.g., "Otter.ai Notetaker" or "Fireflies.ai Notetaker"). Participants can see the bot in the attendee list, which serves as implicit notification. Fathom's bot announces itself by name in the meeting when it joins, which is slightly more visible than a silent attendee-list entry. That said, relying on a bot name or a brief announcement for legal consent is thin. Most legal teams would not consider "a bot named Otter.ai joined" as sufficient consent in an all-party state. None of these tools offer configurable per-state consent flows the way Gong does.

Krisp, Bluedot, and Jamie record locally without joining as a bot participant. Other meeting attendees have no way to know the recording is happening unless the user tells them. These tools put the consent burden entirely on the person recording. If you use desktop-level recording, your team needs clear training on when and how to announce it.

The pattern is clear: platform-native recording (Zoom, Teams, Meet) generally handles notification better than third-party tools. Third-party bots provide some visibility through their presence in the meeting. Desktop-based tools provide none. The compliance burden shifts to you as the tools become less visible.

What to do about it

Here are five concrete steps to reduce your legal risk around meeting recordings.

1. Map your states. List every state where your team members work. List every state where your customers and prospects are located. If any of those states require all-party consent, your recording policy needs to account for it. For most companies with remote employees, this means at least one all-party state is in the mix.

2. Configure your recording tool to announce itself. Turn on every notification and consent feature your tool offers. In Zoom, enable the consent dialog for cloud recordings and customize the notification text. In Teams, ensure recording notifications are active (they are by default, but check). If you use a third-party tool like Gong, configure the pre-call consent notifications. Don't rely on default settings.

3. Add a recording notice to meeting invites. For recurring meetings and any meeting that will be recorded, add a line to the calendar invite: "This meeting will be recorded and transcribed. By joining, you consent to the recording." This isn't bulletproof legally, but it establishes a paper trail of notification. Some legal teams include this language in email signatures as well.

4. Train your team. Your sales reps, customer success managers, and anyone who records calls needs to know the rules. The training doesn't need to be long. Cover: which states require all-party consent, how to verbally announce recording at the start of a call, and what to do if someone objects. A five-minute briefing and a one-page reference sheet are usually enough.

5. Audit your tool's compliance features. Every six months, review what your recording tool offers for consent management. These tools update frequently. Zoom, Teams, and Gong all ship compliance-related features on a regular basis. New state laws pass. Court decisions shift the rules. A quick review twice a year keeps you current.

The goal isn't to stop recording meetings. Recording is valuable for training, accountability, and documentation. The goal is to record legally, with informed consent from everyone on the call. In most cases, that means saying "I'm going to record this meeting" at the start and giving people a chance to object. It takes five seconds. The alternative is a lawsuit.

Disclaimer: This article is for informational purposes only and does not constitute legal advice. Recording consent laws are complex, vary by jurisdiction, and change over time. Consult a qualified attorney for guidance on your specific situation.