Skip to content
Learn · Updated September 2026

TCPA (Telephone Consumer Protection Act)

The TCPA is a U.S. federal law that restricts telemarketing calls, autodialed and prerecorded calls, and unsolicited texts. It requires prior consent for certain contact, honors the Do-Not-Call registry, and enforces calling-time windows — with statutory damages per violation that make compliance a real financial risk.

How it works

TCPA governs how and when you can call or text consumers: consent requirements, quiet hours (generally 8am-9pm local time), DNC scrubbing, and identification rules. Penalties run $500-$1,500 per violation.

Why it matters

Outbound calling and SMS at scale without TCPA controls is a lawsuit waiting to happen. Compliance has to be enforced by the system, not left to operator discretion.

A TCPA-safe path for one outbound touch: 1. Classify number as wireless or landline; 2. Look up stored consent and revocations; 3. Scrub against national and internal DNC; 4. Check 8am to 9pm in contact's timezone; 5. Send, then log the touch for audit.
A TCPA-safe path for one outbound touch

Which outbound activities does the TCPA actually reach?

The statute and the FCC rules under it sort contact into a few buckets. Calls made with an autodialer or an artificial or prerecorded voice to a wireless number generally need prior express consent, and prior express written consent when the purpose is telemarketing. Texts are treated as calls for this purpose, so an automated SMS campaign sits in the same bucket as a robocall. Live, manually placed sales calls to a residential line are governed mainly by the Do-Not-Call rules and the calling-hours window.

Business lines are handled differently from personal ones, but a decision-maker's mobile number often counts as a wireless number even when it appears on a company website. Teams that run SMS outreach under a documented consent policy usually classify every mobile as in scope unless counsel says otherwise.

How much exposure can one campaign create?

The TCPA gives recipients a private right of action with statutory damages of $500 per violation, which a court can raise to as much as $1,500 per violation if the conduct was willful or knowing. Each call or text can count separately.

A hypothetical makes the scale obvious. Suppose a team texts 2,000 mobile numbers with no consent record, then sends one follow-up. That is 4,000 messages. At $500 each the theoretical exposure is $2,000,000, and $6,000,000 at the willful ceiling. Class actions aggregate exactly this kind of arithmetic, which is why the controls belong in the sending system and not in a rep's memory.

What evidence should a consent record hold?

If a claim arrives, the question is whether you can prove consent for that number at that time. A usable record stores the phone number, the exact wording the person agreed to, the date and time, the source (web form URL, paper form, verbal script), and any later revocation. A spreadsheet column that says "opted in: yes" rarely survives scrutiny because it shows none of that.

Revocation matters as much as capture. A STOP reply or a spoken request should end automated contact on every channel, which is why the TCPA and your cross-channel do-not-contact list need to share one source of truth. This is general information, not legal advice; a telecom attorney should review your consent language.

Where should a team start if it has no TCPA controls today?

Start with the list, then the clock, then the dialer. Scrub every number against the National Do-Not-Call Registry and your internal suppression list before it enters a sequence. Next, gate sends to 8am to 9pm in the recipient's local time, using the contact's timezone and not your office's. Then check whether any calling path uses prerecorded messages or automated dialing, since those carry the stricter consent requirements.

In Autocloz these checks sit in the compliance gate that every step of the multichannel sequence builder passes through, so a call or text scheduled outside the window is held with a stated reason. Our guide to TCPA rules for cold calling walks through calling scripts separately.

How Autocloz handles it

Autocloz enforces TCPA-aligned controls in the sequence engine: cross-channel DNC suppression, quiet-hours/timezone gating, consent tracking and an auditable compliance log on every outbound touch.

Free tools for this

No signup required — they run in your browser.

FAQ

Does the TCPA apply to B2B calls?

It primarily targets consumer contact, but many rules (DNC, prerecorded messages, texting to wireless numbers) can reach B2B mobile contacts. Treat mobile and personal numbers as in-scope and keep consent records.

What are TCPA quiet hours?

Calls and texts are generally restricted to 8am-9pm in the recipient's local time. Autocloz gates outbound touches to the contact's timezone automatically.

Related terms

Sources

TCPA (Telephone Consumer Protection Act) — explained by Autocloz

Want this applied to your setup?

This is a reference page. If you have a specific question about your own outreach, leave your email and a human on our team will reply.