By Sagar Shankaran, Founder of CallSphere
Avoid costly TCPA violations with this 2026 compliance guide covering prior express consent, DNC rules, ATDS definitions, and enforcement trends.
Key takeaways
The Telephone Consumer Protection Act (TCPA), codified at 47 U.S.C. Section 227, is the primary federal statute governing outbound telephone communications in the United States. Enacted in 1991, the TCPA restricts telemarketing calls, auto-dialed calls, prerecorded or artificial voice calls, unsolicited faxes, and text messages. It is enforced by the Federal Communications Commission (FCC) and through private litigation.
The TCPA matters enormously because of its statutory damages provision: $500 per violation, trebled to $1,500 per willful violation. In high-volume outbound calling operations, a single campaign error can generate millions of dollars in liability. In 2025, TCPA-related lawsuits and settlements exceeded $2.3 billion, making it one of the most litigated consumer protection statutes in the United States.
The regulatory landscape shifted significantly in 2024-2025 following the Supreme Court's decision in Facebook v. Duguid (2021) narrowing the ATDS definition, subsequent FCC rulemaking expanding one-to-one consent requirements, and the growing use of AI voice agents in outbound calling — a technology the FCC addressed directly in its February 2024 Declaratory Ruling.
The TCPA prohibits calls to cell phones using an ATDS without the called party's prior express consent.
flowchart LR
REQ(["Inbound request"])
PII["PII detection<br/>regex plus NER"]
POL{"Policy engine<br/>OPA or rules"}
REDACT["Redact or mask"]
LLM["LLM call"]
OUT["Response"]
AUDIT[("Append only<br/>audit log")]
BLOCK(["Block plus<br/>notify DPO"])
REQ --> PII --> POL
POL -->|Allow| REDACT --> LLM --> OUT --> AUDIT
POL -->|Deny| BLOCK
style POL fill:#4f46e5,stroke:#4338ca,color:#fff
style AUDIT fill:#ede9fe,stroke:#7c3aed,color:#1e1b4b
style BLOCK fill:#dc2626,stroke:#b91c1c,color:#fff
style OUT fill:#059669,stroke:#047857,color:#fff
Post-Facebook v. Duguid ATDS definition: An ATDS is equipment that has the capacity to store or produce telephone numbers to be called using a random or sequential number generator and to dial such numbers. Equipment that merely stores and dials numbers from a pre-existing list does not qualify as an ATDS under this definition.
Practical impact: After Duguid, calls made from predictive dialers using pre-loaded contact lists may not trigger the ATDS provision. However, this does not eliminate TCPA risk — other provisions (prerecorded voice, DNC) still apply, and several states have enacted broader ATDS definitions.
The TCPA prohibits calls delivering a prerecorded or artificial voice message to:
Hear it before you finish reading
Talk to a live CallSphere AI voice agent in your browser — 60 seconds, no signup.
AI voice agent implication: The FCC's February 2024 Declaratory Ruling confirmed that calls made using AI-generated voices are "artificial voice" calls under the TCPA. This means AI voice agent outbound calls are subject to the full TCPA consent requirements for prerecorded/artificial voice calls.
The TCPA and FCC rules (47 C.F.R. Section 64.1200) prohibit telemarketing calls to numbers registered on the National Do Not Call Registry, with limited exceptions:
Organizations that conduct telemarketing must maintain an internal DNC list and honor requests to be placed on it. Procedures must be established for adding numbers within 30 days of a request, and numbers must remain on the internal DNC list for 5 years from the date of the consumer's request.
The TCPA establishes different consent levels depending on the type of call and the technology used:
Required for:
How obtained: The consumer provides their phone number in the context of the business relationship. For example, providing a cell phone number on an account application or registration form constitutes prior express consent for informational calls to that number.
Required for:
PEWC requirements (47 C.F.R. Section 64.1200(f)(9)):
Effective January 27, 2025, the FCC's updated consent rules require:
Still reading? Stop comparing — try CallSphere live.
CallSphere ships complete AI voice agents per industry — 14 tools for healthcare, 10 agents for real estate, 4 specialists for salons. See how it actually handles a call before you book a demo.
| Year | Entity | Violation | Penalty |
|---|---|---|---|
| 2024 | Insurance lead generator | Calling numbers on DNC registry using prerecorded AI voices | $299 million (proposed) |
| 2024 | Political robocaller | AI-generated voice calls impersonating a political candidate | $6 million + criminal referral |
| 2025 | Debt collection agency | Continuing to call after consumer revoked consent | $45 million |
| 2025 | Solar energy company | Calling consumers who opted out; inadequate internal DNC procedures | $82 million (proposed) |
| 2025 | Health insurance marketplace | AI voice calls to cell phones without prior express written consent | $156 million (proposed) |
Several states have enacted calling restrictions that exceed federal TCPA protections:
Build a consent management system that:
For organizations using AI voice agents for outbound calls:
CallSphere's AI voice agent platform includes built-in TCPA compliance controls: PEWC verification before outbound calls, mandatory AI disclosure at the start of each call, real-time DNC checking, time-zone-aware calling windows, and automated consent revocation processing.
Maintain the following records for at least 5 years:
The TCPA's cell phone provisions (ATDS and prerecorded voice restrictions) apply regardless of whether the call is B2B or B2C — the restriction is based on the number called (cell phone), not the relationship. DNC registry restrictions technically apply only to "residential subscribers," but many business owners register their numbers on the DNC registry. Best practice is to treat all outbound calls as subject to TCPA regardless of the B2B context.
Yes. The FCC has ruled that consumers can revoke consent by any reasonable means, including verbally during a call, by text message, by email, or in writing. The revoking consumer does not need to use a specific method or channel designated by the caller. Organizations must monitor all communication channels for revocation requests.
The statutory damages are $500 per violation, trebled to $1,500 per willful violation. Each call to a non-consenting number is a separate violation. A 10,000-call campaign to non-consenting numbers could generate $5 million to $15 million in statutory damages. Class actions can aggregate thousands of individual claims, resulting in settlements in the hundreds of millions of dollars.
The FCC's one-to-one consent rule (effective January 27, 2025) requires that prior express written consent specifically authorize calls from one identified seller. Lead generators can no longer obtain a single consumer consent and sell it to multiple callers. Each caller must be individually identified in the consent language. This has fundamentally changed the lead generation business model, requiring either single-seller lead forms or separate consent for each buyer.
Yes. The FCC has ruled that text messages are "calls" under the TCPA, subject to the same ATDS, prerecorded voice (for automated texts), and DNC restrictions as voice calls. The same consent requirements apply: prior express written consent for telemarketing texts, prior express consent for informational texts. The FTSA (Florida) explicitly covers text messages with the same penalty structure as voice calls.
Written by
Sagar Shankaran· Founder, CallSphere
Sagar Shankaran is the founder of CallSphere, where he builds production AI voice and chat agents deployed across healthcare, hospitality, real estate, and home services. He writes about agentic AI, LLM engineering, and shipping voice agents that handle real calls in production.
See how AI voice agents work for your industry. Live demo available -- no signup required.
Using GPT-Realtime-2 for healthcare voice agents. BAA scope, PHI handling, retention, logging, and why a managed platform usually wins this build.
AI Control Tower is the governance layer for ServiceNow's Project Arc — policy, monitoring, and audit logs for autonomous agents. Here is how it works.
CAISI announced new agreements with Google DeepMind, Microsoft, and xAI in May 2026. What gets tested, what changes for enterprise AI buyers, what to watch.
Six-domain AI vendor diligence: financial, security, privacy, operational, legal, ethics. Plus 30+ specific questions, SOC 2 / ISO 27001 baselines, and review cadence.
Enterprise CIO Guide perspective on The first wave of EU AI Act enforcement landed in 2026 — here is the practical impact on agent deployments.
FINRA 2210 governs financial communications. How financial services firms are deploying LLM agents while meeting marketing-compliance requirements in 2026.
© 2026 CallSphere LLC. All rights reserved.
Made within New York
Watch how CallSphere handles real customer calls, schedules appointments, and processes payments — live.
Try Live DemoBook a DemoCalculate Your ROI