Staying TCPA-Compliant When You Auto-Dial: Quiet Hours, Consent & Scrubbing

Auto-dialing is where outbound voice gets dangerous. A power dialer that loads a list, drops voicemails, and routes connects to your reps will happily place 400 calls an hour — and if 30 of those numbers belong to TCPA litigators or DNC complainers, you've just manufactured 30 potential demand letters before lunch. The dialer doesn't know the difference. You have to build the guardrails.

Full disclosure: I work for ReadySMS, and we sell a Power Dialer plus a standalone litigator scrub. So I have a horse in this race. But the guardrails below are the same ones I'd tell you to run if you used a competitor's dialer — the TCPA doesn't care whose software placed the call.

This is a practical breakdown, not legal advice. Statutory damages run roughly $500 to $1,500 per call under the TCPA, so the math on "skip the guardrails" gets ugly fast. Let's walk the three things that actually move your risk: quiet hours, consent and DNC, and litigator scrubbing.

The three layers, in order of how often they bite

Most outbound voice TCPA trouble comes from three places. They stack — fixing one doesn't excuse ignoring the others.

LayerWhat goes wrongPractical fix
Quiet hoursCalling before 8am / after 9pm in the recipient's time zoneTime-zone-aware send/dial windows
Consent + DNCDialing numbers with no prior express consent, or on the National DNCCapture and store consent; honor DNC and internal opt-outs
Litigator / serial filerDialing a known TCPA plaintiff who sues for sportPre-dial scrub against litigator + DNC-complainer lists

The third one is the cheapest to fix and the one most teams skip, which is exactly why it bites. We wrote a deeper piece on how these stack — The Three Layers of TCPA Risk Reduction — but here's the outbound-voice version.

Quiet hours: it's the recipient's clock, not yours

The federal rule is simple to state and easy to violate: no telemarketing calls before 8:00 a.m. or after 9:00 p.m. in the called party's local time. Many states are stricter — some pull the evening cutoff to 8:00 p.m., some restrict Sundays.

The trap with a power dialer is that your reps sit in one time zone and your list spans four. A rep dialing at 5:30 p.m. Pacific is calling 8:30 p.m. Eastern — fine — but at 6:15 p.m. Pacific that East Coast number is now a 9:15 p.m. call, and you've crossed the line without anyone noticing.

What to actually do:

  • Enforce dial windows by the recipient's area code / mapped time zone, not your reps' clock.
  • Pad the edges. Stop East Coast dialing a few minutes before the hard 9:00 p.m. cutoff so a queued call that connects late doesn't push you over.
  • Treat unknown / VoIP numbers conservatively — if you can't reliably map the time zone, hold them for the safe mid-day window.

ReadySMS enforces quiet hours on the SMS side based on the recipient's local area, and the same discipline applies to voice. If your dialer can't gate by recipient time zone, you're relying on reps to do timezone math at speed, which they won't. We dug into the legal-vs-smart version of this for text in SMS Quiet Hours — the logic transfers cleanly to calls.

Consent: you need it before the first dial, not after

For most outbound marketing calls, the TCPA wants prior express consent, and for calls using an autodialer or prerecorded/voicemail-drop content, the bar is prior express written consent. That means a record showing the person agreed to be called at that number, for this kind of message, before you dialed.

Voicemail drop is where this gets people. A pre-recorded voicemail dropped into someone's inbox is a prerecorded message under the TCPA — it doesn't matter that the phone never rang for them. If you're using voicemail drop, your consent posture needs to support prerecorded contact, not just live dialing.

Practical consent hygiene for an auto-dial operation:

  1. Capture consent at the source — the form, the opt-in, the checkbox — and store it with a timestamp and the language they agreed to.
  2. Keep it per-number. Consent attaches to a phone number, not a person. A new number means new consent.
  3. Honor opt-outs immediately and permanently. If someone says "stop calling," that suppression has to propagate so they never re-enter a dial queue from a different campaign or list import.
  4. Scrub the National DNC for numbers you don't have an established relationship with. "We bought the list" is not consent and not an exemption.

ReadySMS records opt-in attestation for bulk and API sends to build an audit trail, and opt-outs propagate across campaigns so a suppressed contact stays suppressed. The same principle has to govern your dial list: one source of truth for who said no. For the consent-capture mechanics in detail, Stay Compliant: Proven Tips for Securing SMS Consent covers the opt-in side that feeds your dialer.

Litigator scrubbing: the $0.005 step nobody runs

Here's the layer that's pure asymmetry. A small but real slice of phone numbers belong to serial TCPA plaintiffs and known DNC complainers — people who maintain numbers specifically to catch non-compliant callers and file. One of them in your dial queue is a near-guaranteed claim.

The fix costs half a cent per number. ReadySMS runs a standalone TCPA & DNC litigator scrub at $0.005 per contact that checks each number against known litigator lists and DNC-complainer lists, then auto-suppresses the matches before you dial. You pay only for what you scrub.

The worked math

Say you're about to load a 20,000-number list into the dialer.

  • Scrub cost: 20,000 × $0.005 = $100.
  • One missed TCPA litigator who files: $500–$1,500 in statutory damages — and that's per call, before legal fees, before any class action exposure.

So the entire scrub of your list costs less than a single unscrubbed plaintiff. You don't need the scrub to catch many litigators to pay for itself — you need it to catch one. We laid the full version of this out in The Math: One TCPA Lawsuit vs Scrubbing Your Whole List, and the conclusion is boring: scrub the list.

The scrub doesn't make you lawsuit-proof. It removes the highest-probability plaintiffs from your queue. Compliance is still ultimately your responsibility — scrubbing just takes the easy, known risks off the board cheaply.

Wiring the guardrails into the dial flow

Compliance breaks when it's a separate step someone has to remember. The goal is to make the guardrails part of the pipeline so a non-compliant call is hard to place, not just discouraged.

A sane outbound-voice flow:

  • Ingest the list → tag the source and consent status on every number.
  • Scrub litigator + DNC + complainer lists → suppress matches automatically.
  • Gate by recipient-local time zone → queue numbers only inside their legal window.
  • Dial with consent-eligible numbers only → voicemail drop only on numbers with written-consent-grade records.
  • Suppress on opt-out → "remove me" propagates instantly and permanently across every campaign.

ReadySMS Power Dialer runs queue and manual dial, voicemail drop, call recording, and transfer/barge/whisper, with speed-to-lead auto-dial on the Team plan ($69/agent/mo). Speed-to-lead is great — calling a fresh lead inside five minutes massively outperforms calling them an hour later (we covered that in Speed-to-Lead) — but "fast" is not an excuse to skip the scrub. The right sequence is scrub, then sprint. A fast call to a litigator is just a fast lawsuit.

When the auto-dialer isn't your problem

Honest caveat: not every outbound calling setup triggers the strictest rules. If you're placing manual, one-at-a-time calls to existing customers with a clear prior relationship and live consent, your exposure profile is lower than a cold blast to a purchased list with prerecorded voicemail drops. The guardrails still matter, but the urgency scales with how automated and how cold the campaign is.

The danger zone is the common agency setup: bought or aggregated lists, autodialer pacing, prerecorded voicemail, multiple time zones. That combination hits every layer at once. If that's you, run all three guardrails — no skipping the scrub because the list "looks clean."

The practical takeaway

Auto-dialing compliance isn't one big thing, it's three small ones you can actually implement this week:

  • Quiet hours gated by the recipient's clock, padded at the edges.
  • Consent + DNC captured at the source, honored permanently, scrubbed against the National DNC for cold numbers.
  • Litigator scrub at $0.005/number before every dial — cheaper than one missed plaintiff, every single time.

None of these make you immune. They take the known, high-probability risks off the table so your reps can dial without manufacturing claims. If you want to see how the scrub and dialer price out for your volume, the pricing page and cost calculator have the per-agent and per-contact numbers — and you can scrub a test list before you commit to anything. Build the guardrails first; then dial fast.