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 + your internal DNC list, only dial within the recipient's local 8am–9pm window, and keep an auditable consent/record trail. Penalties are $500–$1,500 *per call*, so enforcement has to happen before the dial.

The non-negotiables

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

Why "after the fact" is too late

Cleaning up violations post-hoc doesn't undo them — each connected call to a DNC number is already a liability. The economics make it cheaper to enforce at the gate.

How Autocloz enforces it

Every dial runs 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 called. The audit log proves it.

> Start free — the dial gate is on for every campaign by default.

Share
Free to start

Stop reading. Start sending.

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