Your Phones Are in Nevada. Your Callers Are Not.

A Las Vegas personal injury firm puts an AI receptionist on its main line. Every call is recorded, transcribed, and summarized into the case file. At 7:40 on a Tuesday night, a woman in Riverside calls about a crash on the drive home from Vegas. The firm's phones are in Nevada. She is in California.

Whose recording law applies?

The practical answer is: plan as if both do. This post puts the two statutes side by side and ends with one rule that satisfies both. It applies just as much to a dealership taking calls from Southern California shoppers or a hotel sales office booking groups from Los Angeles. This is not legal advice. It is a plain reading of two statutes so you can have a sharper conversation with your own lawyer.

What Nevada's statute says

NRS 200.620 makes it unlawful to intercept a wire communication, which includes a phone call, unless the interception is made with the prior consent of one of the parties. Read that far and Nevada looks like a one-party state.

It is not that simple. The same subsection pairs that consent with a second condition: an emergency situation where getting a court order is impractical, followed by an application for court ratification. An ordinary business recording its own inbound calls does not meet that second condition. That is why phone recording in Nevada is treated as needing the consent of everyone on the call. We walked through this in detail in our earlier post on Nevada recording consent for AI phone systems.

So before California even enters the picture, a Las Vegas business recording calls should already be getting consent from the caller.

What California's statute says

California Penal Code 632 makes it a crime to intentionally record a confidential communication with an electronic device without the consent of all parties.

Two details matter for a business phone line.

First, the definition of confidential. Under 632, a communication is confidential when the circumstances reasonably indicate a party wants it kept between the parties. It excludes situations where the parties may reasonably expect the communication to be overheard or recorded. Our reading, not a court's: a caller describing an injury, a debt, or a divorce to a law firm is close to the textbook case of a conversation the caller expects to stay private. And a clear recording disclosure is exactly what changes that expectation.

Second, the penalty written into the statute. A first violation carries a fine of up to $2,500 per violation, jail of up to one year, or both. For someone previously convicted under 632 or several related sections, the fine ceiling rises to $10,000 per violation. Per violation is the phrase to notice. An AI system that records every call does not make one mistake. It makes the same mistake on every call.

Nevada and California, side by side

Both statutes as read on FindLaw on September 6, 2026.

Read the third row again. The two statutes get there by different roads, but for a business answering its own phones they land in the same place.

Why "we are a Nevada business" is not the answer

The instinct is to say your servers, your office, and your phone number are all in Nevada, so Nevada law governs. That argument is not a sure thing. Both statutes are written to protect the people on the call, and a California caller who sues will naturally reach for California's statute. Which law a court applies is a real question that lawyers argue about, and neither statute's text answers it for you.

You do not want to be the business that pays to find out. The better move is to set up your calls so the question never matters, because you already did what both states require.

There is a second trap: area codes. A 702 number can belong to someone who moved to Sacramento three years ago, and a 213 number can belong to someone who lives in Henderson. You cannot reliably sort callers by state from caller ID, so any plan that treats California callers differently will miss some of them.

The one safe rule

Get the consent of every party, out loud, before the recording starts, on every call, regardless of where the caller appears to be.

In practice that means the recording disclosure is the first thing the caller hears, the recording begins after the disclosure plays, and the caller has a real way to decline, such as being routed to a person or a voicemail box that is not recorded. When a new party joins, such as a transfer to an attorney's cell or a three-way call with an adjuster, the disclosure repeats. Outbound calls from the AI follow the same rule, disclosure first.

This rule satisfies Nevada, because every party consented. It satisfies California, because every party consented and nobody on the line can claim they expected the call to go unrecorded.

Where AI phone setups quietly break the rule

Most businesses that get this wrong already have a disclosure. The problem is timing and edges.

Audio captured before the greeting. Many AI voice platforms start streaming audio for transcription the moment the call connects. If the disclosure plays while the recording is already running, the first seconds were recorded before consent.

Voicemail and after-hours paths. The main menu has the disclosure, but the overflow voicemail or the after-hours bot uses a different greeting that does not.

Transfers. The AI discloses, then warm transfers to a staff cell phone where a second recording starts with no fresh notice to the new party.

Where the recordings live. Consent answers whether you may record. It does not answer who can access the files afterward. For firms handling privileged conversations, keeping recordings and transcripts on hardware you control is worth considering, which is the case we make for onsite AI.

What to do this week

1. Call your own number from a cell phone. Listen to the first ten seconds and write down exactly what a caller hears and when. Then ask your vendor, in writing, at what moment audio capture begins relative to that greeting.
2. Walk every path. Repeat the test after hours, into voicemail, and through a transfer. Every path that records must disclose first, and every transfer to a new party must disclose again.
3. Remove state logic. If anyone has configured different recording behavior by area code or caller location, replace it with one disclosure for all callers and document the change with the date.

If you want a second set of eyes on your call flow, our free 15-minute audit covers it, and you can start from our page on AI for law firms in Las Vegas.