Link Leads Blog · August 26, 2026
Twelve states require every party on a call to consent before it's recorded, not just one. A dialer or CRM that records by default doesn't know which state it just dialed into. This is the practical version — which states require it, the line that gets consent on tape, and how to set up a multi-state calling list so the setting is right before you dial, not after.
This is not legal advice. Call recording consent statutes vary by state, carry real civil and criminal penalties in some states, and change over time — confirm current requirements with an attorney before you build a recording policy around this post.
Federal law and most states only require one-party consent to record a phone call — meaning the agent's own knowledge that the call is being recorded is enough, even if the other party never finds out. A smaller group of states go further and require all-party consent: every person on the call has to agree before recording starts. For a dialing operation working leads across a national or multi-state list, the all-party states are the ones that create exposure, because the agent has to actually get a yes on tape before the substance of the call, not just have a general policy of recording.
The commonly cited all-party (or two-party) consent states are California, Connecticut, Florida, Illinois, Maryland, Massachusetts, Michigan, Montana, Nevada, New Hampshire, Pennsylvania, and Washington. A few of these apply the rule a little differently — Nevada, for example, treats it as one-party consent under case law even though the statute reads as all-party, and Illinois' law was rewritten after a state supreme court struck down the old version. That variation is exactly why this needs a lawyer's confirmation for the states you actually dial, not a copy-paste list — statutes get amended and courts reinterpret them. Every other state follows one-party consent, which covers the majority of a typical aged-lead file by record count.
An aged consumer list pulled across all 50 states will have a meaningful share of records in all-party states just by population weight — California and Florida alone are two of the largest state pulls on most orders. That means a single national dialing session can cross from a one-party state into an all-party state call to call, and the recording rule that applies is determined by where the person being called is located, not where the agent is sitting. A campaign that segments by state for compliance reasons already has the infrastructure to flag all-party states differently — it's the same state field used for the Florida telephone solicitation act rules and for time-zone-based calling windows.
Consent has to happen before the substantive part of the call, and it has to be affirmative — silence or continuing to talk after a disclosure is not consent in most all-party states. A short, direct opener works:
"Hi, this is {agent} with {agency} — this call may be recorded for quality purposes, is that okay?"
If the answer is anything other than a clear yes, recording has to stop for that call, or the call has to proceed unrecorded. Some agents build a hard rule instead of asking: never record calls to all-party states at all, and only record in the one-party states where a blanket recording policy is already lawful. That removes the judgment call from every individual dial and just requires the state to be flagged correctly on the record before the call connects.
The realistic failure isn't an agent deciding to record without asking — it's a dialer, CRM, or call-tracking tool that records every call by default as a platform-wide setting, without any state-aware logic behind it. Most CRMs and cloud dialers ship with call recording turned on globally for coaching and quality-assurance purposes, and that default was written for inbound sales lines, not outbound campaigns hitting all-party states. The fix is a setting check, not a script change: confirm whether the platform can suppress or gate recording by the called party's state, and if it can't, decide up front whether the campaign records nowhere, records everywhere with the disclosure line above, or only records the one-party states on the list. All three are workable policies — leaving the default recording setting untouched without checking is the one that isn't.
Ironically, a properly disclosed and consented recording is also one of the better pieces of evidence an agent can have if a call is ever disputed — it shows the disclosure was made and the person continued the conversation. That's a separate question from TCPA/DNC compliance, which governs whether the number should have been called at all; recording consent only governs whether that specific call can be captured on tape. Both records matter for the same reason: if a complaint ever comes in, a documented scrub and call log is what shows the campaign was run in good faith, and a properly consented recording of the call itself is more of the same kind of paper trail.
The cheapest time to handle this is at list-build, not mid-campaign. Tag every record by state when the file loads into the dialer, mark the all-party states as a distinct segment, and set the recording policy for that segment before the first dial goes out — whether that's "don't record," "ask and log the answer," or "route to a different disposition workflow that skips recording entirely." Pair it with the same state-based logic already used for calling-hour windows and DNC scrub timing, so one state field drives every compliance rule in the campaign instead of maintaining separate lists for each one.
Recording consent is one piece of a larger compliance stack for a multi-state calling campaign — TCPA and DNC scrubbing govern whether to call at all, state mini-TCPAs like Florida's add their own rules on top, and recording consent governs what you can capture once you're on the line. None of this requires slowing down; it requires the state field on the list doing more work before the campaign starts. Build a state-targeted order with the age band and volume for your calling plan, or grab the free 100-row sample to see the fields a file actually ships with before setting up the segmentation above.