Call Recording Consent: One-Party vs. All-Party States

The federal baseline: one party is enough

Federal law (the Wiretap Act, 18 U.S.C. §2511) permits recording a phone call when one party to the call consents — and the business placing or receiving the call counts as a party. If federal law were the whole story, a company could record every call it participates in without telling anyone.

It isn't the whole story. State law applies on top, and states split into two camps.

One-party states vs. all-party states

Most states mirror the federal rule: one party's consent suffices. But for phone calls, about a dozen states require every participant's consent before recording — commonly called "two-party" or all-party consent states. The core statutory list is California, Delaware, Florida, Illinois, Maryland, Massachusetts, Montana, New Hampshire, Pennsylvania, and Washington, and two more behave as all-party for phone recording in practice: Connecticut (via its civil recording statute) and Nevada (via state supreme court case law). A couple of frequently mis-listed states cut the other way — Oregon's all-party rule covers in-person conversations, not phone calls, and Michigan courts read a participant exception into its statute — but no calling operation should be building state-by-state logic here anyway, for reasons below.

The all-party states are not fringe: California and Florida alone cover a fifth of the country's population, and both attach real teeth — California's Invasion of Privacy Act supports private lawsuits at $5,000 per violation, and plaintiffs' firms actively recruit for them.

Cross-state calls: whose law wins?

When a one-party-state business calls an all-party-state resident, courts have not settled on a single answer — some apply the caller's law, others the recipient's, and California courts in particular have applied California law to out-of-state companies recording calls with Californians.

A business calling lists across state lines cannot control where the called party is standing, cannot reliably infer it from the number, and cannot afford a choice-of-law gamble on every call. The practical resolution is the one every serious call center reached years ago: follow the strictest rule everywhere. Announce the recording and obtain consent on every recorded call, regardless of where it terminates.

The detail everyone misses: when recording starts

"This call may be recorded" only works as consent if it comes before the recorded conversation. That sounds obvious, but most calling systems record from the moment the call is answered — which means by the time the disclosure plays, the system has already captured the greeting, background audio, and sometimes an entire exchange, none of it consented to.

Consent-gating has a useful side effect: calls that never reach the disclosure — answered by a machine, hung up in the first seconds — are never recorded at all, which keeps un-consented audio out of your storage entirely.

AI calls raise the stakes, and simplify the fix

An AI voice agent records calls for the same reasons a call center does — quality, dispute resolution, extraction — and faces the same consent rules. The difference is reliability: a human agent can forget the disclosure or read it after small talk has already been captured. Software cannot forget.

Vosy implements consent-gated recording at the platform level: the recording pipeline starts only when the consent disclosure plays, the disclosure line itself is configurable per agent, and calls that end before consent produce no recording. Recordings and transcripts are then encrypted at rest. The disclosure-then-record sequence is enforced by the system on every call — it isn't a line in a prompt that an agent might skip.

Related: recording consent is one of three disclosure obligations an AI calling operation carries — see when an AI call must identify itself as AI →