The 'Eleven All-Party Consent States' List Is Wrong. Here's What to Do Instead.

The 'Eleven All-Party Consent States' List Is Wrong. Here's What to Do Instead.

Search for two party consent states call recording and you will find a number. Usually eleven. Sometimes twelve, occasionally thirteen, and the state lists behind those numbers do not agree with each other. That disagreement is not sloppiness on the part of whoever published the list. The lists differ because the underlying statutes differ in ways a count cannot express.

If your agency records patient and caregiver calls across state lines — and most home health, home care, and hospice operators now do — the number is the wrong artifact to build a policy on. Here is what is actually settled, what is genuinely contested, and what to operate on in the meantime.

What is settled: the federal floor

The federal Wiretap Act is not ambiguous. 18 U.S.C. § 2511(1)(a) makes it unlawful to intentionally intercept, endeavor to intercept, or procure another person to intercept any wire, oral, or electronic communication.

Section 2511(2)(d) then carves out the exception nearly every business recording program relies on:

"It shall not be unlawful under this chapter for a person not acting under color of law to intercept a wire, oral, or electronic communication where such person is a party to the communication or where one of the parties to the communication has given prior consent to such interception unless such communication is intercepted for the purpose of committing any criminal or tortious act in violation of the Constitution or laws of the United States or of any State."

Three things follow. Federal law is a one-party consent regime. Your agent is a party to the call, so the federal exception is generally available. And the exception has a condition attached — it does not apply where the interception is for the purpose of a criminal or tortious act. Violations carry criminal exposure and a civil action under 18 U.S.C. § 2520.

Federal law is a floor, not a ceiling. States may impose stricter requirements, and several do.

What is not settled: almost everything above the floor

Here is where the published lists come apart. The variation is not in whether a state is "strict" — it is in four separate dimensions that different lists resolve differently.

1. Consent versus notification

Some state schemes are written around consent from all parties. Others are written around notice, where adequate disclosure plus continued participation is treated as establishing consent. A list that codes both as "two-party consent" has flattened a real operational difference: one requires an affirmative act you must capture, the other requires a disclosure you must prove you made.

2. What counts as a protected communication

Several states protect only confidential communications, defined by reference to the parties' reasonable expectation of privacy. Whether an inbound call to a business line that opens with a recording disclosure is "confidential" under such a statute is exactly the kind of question that gets litigated, and courts have not answered it uniformly. A state can appear on an all-party list and still, in practice, treat a disclosed business call very differently from a private one.

3. Which state's law applies to an interstate call

Your intake coordinator sits in one state. The patient's daughter calls from another. Your recording infrastructure sits in a third. Which law governs is a genuine conflict-of-laws question, and the answers courts have given are not consistent. Some analyses look to where the interception occurred; others to where the parties were located; others apply the more protective state's law. This is the single largest reason state-count lists mislead operators — they imply the answer depends on one state.

4. What the statute actually covers

Some state schemes were drafted around wire and landline communications and were amended later, unevenly, to address cellular and cordless calls. Whether a given provision reaches a mobile-to-mobile call can turn on amendment history rather than on the headline rule.

None of that is resolvable by counting states. It is resolvable only by a state-specific legal analysis, which is why this post does not reproduce a list. Publishing a number we cannot source to primary law would be worse than publishing nothing.

Two federal myths worth killing

The FCC does not require a beep tone on your calls. The FCC's own consumer guidance states that "the FCC has no rules regarding recording of telephone conversations by individuals, but some state laws prohibit this practice," and directs consumers to their state public service commission and attorney general. See the FCC's guidance on recording telephone conversations. The periodic beep is a legacy convention, not a general federal mandate on healthcare businesses.

HIPAA does not require you to record calls, and it is not a consent statute for recording. HIPAA governs how PHI may be used and disclosed and how it must be safeguarded. It does not compel a healthcare organization to record telephone conversations, and it does not supply the consent that state wiretap law may require. Those are separate legal regimes that happen to touch the same audio file. Any vendor pitch that collapses them should be treated with suspicion.

The operating posture that survives the uncertainty

You cannot resolve a genuine legal split from an ops chair. You can adopt a posture that is defensible under either resolution.

The posture is: obtain all-party consent everywhere, capture it in the recording, and treat every relaxation from that baseline as a documented exception approved by counsel.

That is deliberately more conservative than federal law requires. The tradeoff is worth naming honestly: you accept a small amount of friction at the top of every call in exchange for not having to be right about a contested state-law question on every one of them. For most healthcare contact centers, that trade is easy. For an outbound-heavy operation where disclosure measurably suppresses connect rates, it may not be, and that is a business decision to make with counsel rather than a rule to follow blindly.

What to do this week

• Write down the actual disclosure language your callers hear. Not what the policy says — what the IVR plays and what agents say on outbound. Get the verbatim text. Most operators discover the inbound and outbound scripts do not match.
• Confirm the disclosure is inside the recording. A disclosure that plays before the recording starts proves nothing later. The consent moment and the recorded audio need to be the same artifact.
• Check what happens on transfer, callback, and after-hours. These are the three paths where the disclosure is most often skipped, because they were built later and by someone else.
• List the states you actually operate in and receive calls from. Distinguish where your agents sit, where your patients are, and where your infrastructure lives. Those three lists are your legal scope, and most agencies have never written them down.
• Hand that state list to counsel with one question. Not "is recording legal" — ask "where does our current disclosure fall short of all-party consent as this state defines it?" It is a narrower question and you will get a faster answer.
• Log your exceptions. If a line or campaign runs without full disclosure, it should exist on a written list with a named approver and a date. An undocumented exception is indistinguishable from an oversight.

Where this fits

Consent is one layer. What you do with the recording afterward — access controls, redaction, retention, disclosure to vendors — is governed by an entirely different body of rules, and we have laid that out in our HIPAA call recording compliance guide. For the operational version, including what to record and what to leave alone, see the home care call compliance checklist.

The category, briefly

A practical consequence of the all-party posture is that you need to verify disclosure actually happened, on every call, rather than assuming the IVR behaved. That verification across full call volume is what call intelligence platforms are for; SurfacerIQ works in that category for healthcare contact centers.

This post is general information about federal and state recording law, not legal advice. State wiretap statutes and their interpretation vary considerably and change, and the conflict-of-laws questions above are genuinely unsettled — get advice from counsel licensed in the states where you operate.

If you want to work through how your disclosure holds up across your call paths, talk to us.