Compliance

TCPA compliance for cold calling (DNC, quiet hours, consent)

TCPA fines run $500–$1,500 per violating call. Scrub against DNC, honour 8am–9pm local quiet hours, and log consent. Here's how to enforce it before the dial, not after.

12 Mar 2026 8 min readBy Autocloz Editorial, Compliance team
TCPA compliance for cold calling (DNC, quiet hours, consent)

Short answer: to stay TCPA-compliant on cold calls, scrub every number against the national and your internal DNC lists, dial only inside the recipient's local 8am–9pm window, and keep an auditable consent trail. At $500–$1,500 *per call*, you enforce this before the dial — never after.

The non-negotiables

  • DNC pre-flight on every number — national, state, and your own suppression list.
  • Local quiet hours figured from the lead's timezone, not yours.
  • Consent + record-keeping behind any prior-express-consent claim.
  • STIR/SHAKEN attestation so carriers don't flag your calls as spam-likely.

Why "after the fact" is too late

You can't un-ring the phone. Every connected call to a DNC number is already a liability the moment it connects, and no cleanup reverses it. The math is simple: it's far cheaper to block at the gate than to pay per violation.

How Autocloz enforces it

Every dial passes through evaluate_send() — a compliance gate that checks DNC, computes the recipient's local quiet hours, and blocks with a structured reason before any carrier API is touched. The audit log is your proof it did.

> Start free — the dial gate is on for every campaign from the start.

Share
Free to start

Stop reading. Start sending.

Every tactic in this article is implemented behind the Autocloz dashboard.