Call recording consent laws: one-party vs. two-party states

If you record calls — for coaching, quality, or dispute resolution — you're touching consent law, and the rules aren't uniform. The core distinction is one-party vs. two-party consent, and getting it wrong carries real risk. Here's the practical version for outreach and sales teams.

The two consent standards

One-party consent means that recording a conversation is permitted as long as at least one party to the call consents. If you're on the call, you can be that party, so you may record your own conversations without separately notifying the other person (under that standard alone).

Two-party consent — more accurately called all-party consent — means that everyone on the call must consent to being recorded. "Two-party" is the common shorthand, but on a call with three or more people, all of them must consent, not just two.

That "all-party" precision matters: on a conference call spanning multiple people or states, the strictest applicable rule can require consent from every participant.

Why the distinction matters

US states are split between these standards. Some follow one-party consent; others require all-party consent. The exact list changes as laws are amended, so it's not something to memorize once and forget.

The complication for outbound teams is interstate calls. When your agent is in a one-party state and the person you're calling is in an all-party state — or vice versa — it's not always obvious which state's rule governs. Courts and regulators have taken different views, and the safest reading is often that the stricter standard applies. That's exactly the situation outbound calling creates constantly: you call across state lines all day.

The practical approach most teams take

Because the map is mixed and interstate calls muddy which rule applies, many teams stop trying to branch by state and instead adopt the strictest standard everywhere: assume all-party consent is required, and get it on every call. Operationally that usually means:

• Announce recording at the start of the call. A clear disclosure like "this call may be recorded for quality and training" puts the other party on notice.
• Give them a chance to consent or object. Continuing the call after a clear disclosure is commonly treated as consent, but honoring an objection (stop recording or end the call) is the safe response.
• Log the disclosure. Keep a record that the notice was given, tied to the call.
• Be consistent. Applying one policy to every call is simpler to run and easier to defend than trying to detect each contact's state in real time.

This "announce and get consent every time" approach trades a little friction for a lot of certainty, and it's why so many quality-monitoring programs sound the way they do.

Beyond consent: handling recordings

Consent is the front door, but recordings are sensitive data once you have them:

• Store them securely and limit who can access them.
• Set retention — keep recordings only as long as you have a reason to, then delete them.
• Watch sensitive content. Recordings that capture payment card or other sensitive data can bring additional obligations; avoid capturing what you don't need.
• Support opt-outs. If someone objects to recording, have a path to continue without it or to end the call.

How Fivra fits

Fivra's dialer offers dual-channel call recording and live monitoring for coaching and quality — but recording behavior should be configured to match your consent policy. Because recording-consent rules vary by state and by whether a call crosses state lines, set your disclosure and recording defaults to the standard you've decided to follow (many teams choose the strictest). Fivra also provides the surrounding compliance tooling — DNC screening, STOP suppression, and audit logs — so your recording practice sits inside a documented process.

This is general information, not legal advice. Consult qualified counsel about the specific states you call into and out of, and about your recording and retention practices.

FAQ

What is the difference between one-party and two-party consent?

One-party consent means only one person on the call needs to consent to recording, and that person can be you. Two-party (all-party) consent means everyone on the call must consent. "Two-party" is shorthand — on a call with three or more people, all participants must consent under an all-party standard.

Which states require two-party consent?

US states are split between one-party and all-party consent, and the specific list changes as laws are amended, so it should be verified against current sources rather than memorized. Because of that split, many teams don't rely on the map at all and instead apply the strictest standard everywhere.

Which rule applies when a call crosses state lines?

It's not always clear. When the caller and recipient are in states with different rules, courts and regulators have reached different conclusions, and the safest reading is often that the stricter (all-party) standard applies. Outbound teams call across state lines constantly, which is why many default to all-party consent.

How do I record calls compliantly across all states?

The common approach is to adopt the strictest standard everywhere: announce at the start of each call that it may be recorded, give the other party a chance to object, honor objections, and log that the disclosure was given. Applying one consistent policy is simpler and easier to defend than branching by state.

Is announcing "this call may be recorded" enough?

A clear disclosure followed by the other party continuing the call is commonly treated as consent under many standards, but the safe practice is to also honor any objection — stop recording or end the call — and to keep a record that the disclosure was made. Confirm with counsel what satisfies the standards you follow.

How long should I keep call recordings?

Keep recordings only as long as you have a business or compliance reason, then delete them, and store them securely with limited access in the meantime. Avoid capturing sensitive data (like payment details) you don't need, since that can add obligations. Set a defined retention period rather than keeping recordings indefinitely.