
Does the TCPA require consent to make calls?
Key Facts
- AI-generated voices are treated as artificial voices under the TCPA, requiring prior express consent for telemarketing calls according to legal analysis
- Statutory damages for TCPA violations start at $500 per call and rise to $1,500 if the violation is knowing or willful per legal sources
- FCC fines can reach up to $16,000 per violation—or $26,000 for intentional breaches as confirmed by regulatory guidance
- Class action judgments have exceeded $925 million in recent years due to TCPA violations based on litigation trends
- Consent must be obtained separately for each identified seller under the FCC's one-to-one consent rule effective December 2023 per Cooley LLP analysis
- Company-specific do-not-call requests must be honored for a minimum of five years and override prior written consent under TCPA requirements
- National DNC Registry scrubbing is required at least every 31 days to maintain calling compliance as mandated by FCC rules
Yes, the TCPA Requires Consent — and the Stakes Are Higher Than Most Businesses Think
Yes, the TCPA Requires Consent — and the Stakes Are Higher Than Most Businesses Think
The TCPA requires consent before making most outbound calls, with penalties starting at $500 per violation and rising to $1,500 if the violation is knowing or willful. FCC fines can reach up to $16,000 per violation — or $26,000 for intentional violations — and class action judgments have exceeded $925 million in recent years. These stakes are not theoretical; they reflect real financial exposure for businesses that fail to verify consent before dialing.
Consent under the TCPA is not a simple yes-or-no checkbox — it is tiered based on call purpose, technology, and phone type. Prior Express Written Consent (PEWC) is required for telemarketing calls using an automatic telephone dialing system (ATDS) or artificial/prerecorded voice to cell phones, and for prerecorded voice calls to residential lines. For non-marketing artificial voice calls using an ATDS to cell phones, only Prior Express Consent (PEC) — which can be oral or implied — is sufficient. This distinction matters because AI-generated voices are treated as artificial voices under the TCPA, meaning any AI-powered calling campaign must meet the applicable consent standard before the first call is made.
- Dual-purpose calls — those with any sales component — are treated as telemarketing and require PEWC
- Consent must be "logically and topically" related to the context in which it was given
- The burden of proof rests entirely on the caller, with no good-faith exception for mistaken belief
For businesses using managed outbound calling services like My AI Call Center, this means list discipline and consent verification are not optional — they are foundational. Campaigns only launch after reviewing list source, consent records, and calling windows to ensure compliance. Without documented, revocable consent that matches the call’s scope and purpose, even well-intentioned outreach can trigger liability. The safest path is to treat every call as requiring verifiable permission — and to honor opt-outs immediately, every time.
Which Type of Consent Your Calls Need: Telemarketing, Technology, and Phone Type Decide
The type of consent your outbound calls require is not a one-size-fits-all rule — it hinges on three interconnected factors: the purpose of the call, the technology used to place it, and whether the recipient is on a cell phone or residential line. These elements determine whether prior express written consent (PEWC), prior express consent (PEC), or no consent at all is legally sufficient under the TCPA.
Call purpose is the first deciding factor. Any call made with the intent to encourage a purchase or sale — even if the transaction doesn’t occur during the call — is classified as telemarketing under TCPA guidelines. This includes dual-purpose calls, where relationship-building is paired with a future sales objective; such calls are treated as telemarketing regardless of when the sale might happen. As a result, they trigger the highest consent standard when combined with regulated technology.
Technology and phone type then refine the requirement. Using an automatic telephone dialing system (ATDS) or an artificial or prerecorded voice — including AI-generated audio — to call a cell phone for telemarketing purposes demands PEWC. For non-telemarketing calls to cell phones using the same technology, only PEC — which can be oral or implied — is required. Meanwhile, artificial or prerecorded voice calls to residential phones for telemarketing also require PEWC, though non-marketing prerecorded calls to residential lines historically needed no consent, though recent FCC guidance now imposes volume limits and opt-out rules even in those cases.
The FCC’s December 2023 order further tightened consent requirements by mandating one-to-one consent, meaning a single consumer’s agreement cannot authorize calls from multiple sellers. This closes the so-called lead generator loophole, eliminating the ability to share or daisy-chain consent across affiliated partners or brands under common ownership. Additionally, consent must be logically and topically related to the context in which it was given — agreeing to receive information about car loans, for example, does not permit calls about debt consolidation.
Critically, possessing a phone number does not equate to consent. Consumers may revoke consent at any time through any reasonable means, and the burden of proving valid, unrevoked consent always falls on the caller. For businesses using managed calling services like My AI Call Center, this underscores the necessity of verifying consent records before launch and maintaining rigorous opt-out and DNC compliance throughout each campaign.
- PEWC is required for telemarketing calls using ATDS or artificial/prerecorded voice to cell phones
- PEC suffices for non-telemarketing artificial voice calls to cell phones using an ATDS
- One-to-one consent rules prevent a single consent from covering multiple sellers
AI Calls, Revocation, and the Rules That Catch Callers Off Guard
AI-powered calling introduces compliance nuances that many businesses overlook until they face enforcement actions. The TCPA treats AI-generated voices as artificial voices, triggering prior express consent requirements for any call using this technology, whether to cell phones or residential lines for telemarketing purposes. This means even informational or reminder calls powered by AI require valid consent if they use an automatic dialing system or prerecorded voice, and the burden of proving that consent rests entirely with the caller.
Consent under the TCPA is not a one-time checkbox — it is revocable at any time by any reasonable means. A consumer can withdraw permission via a simple text message saying "STOP" or even a verbal request during a call, and callers must honor that revocation immediately. Maintaining accurate opt-out logs and syncing them across campaigns is not just a best practice; it’s a legal necessity to avoid violations that can carry $500 per incident in statutory damages, rising to $1,500 if the violation is knowing or willful.
Businesses must also maintain an internal do-not-call (DNC) list that honors consumer requests for at least five years, overriding any prior express written consent. Simultaneously, numbers must be scrubbed against the National DNC Registry at least every 31 days to remain compliant, a frequency that catches many off guard who assume quarterly checks are sufficient. Calling hours are strictly limited to 8 AM to 9 PM in the recipient’s local time zone, with state-specific variations adding further complexity — especially as states like Florida, Maryland, and Oklahoma enforce their own mini-TCPA laws with stricter autodialer definitions and, in some cases, criminal penalties.
For organizations using managed services like My AI Call Center, these rules are built into campaign design from the start. List and consent reviews happen before launch, ensuring only permissioned contacts are called and that AI disclosures, opt-out handling, and quiet-hour compliance are baked into every script. This proactive approach turns regulatory complexity into operational clarity, reducing risk while preserving the ability to run useful, consent-aligned calls at scale.
- AI-generated voices are treated as artificial voices under the TCPA, requiring prior express consent for telemarketing and certain non-marketing calls
- Consent can be revoked at any time by any reasonable means, including non-standard methods like a text saying "I do not want to hear from you"
- Company-specific DNC requests must be honored for a minimum of five years and override prior written consent
- National DNC Registry scrubbing is required at least every 31 days, and calling hours are limited to 8 AM–9 PM local time
How to Verify Consent Before Any Campaign Launches
Before launching any outbound calling campaign, verifying consent is not just a best practice—it’s a legal necessity under the TCPA. Since the burden of proof lies entirely with the caller, and there is no exception for a good-faith but mistaken belief, every number on your list must be backed by documented consent that matches the call’s purpose and technology. Failing to do so risks penalties of up to $500 per violation—or $1,500 if the violation is knowing or willful—along with potential FCC fines exceeding $16,000 per incident. A rigorous pre-launch review protects both compliance and campaign integrity.
My AI Call Center builds this verification into its process by reviewing list source and consent records before any campaign begins. This includes confirming that consent was obtained via a signed agreement that clearly identifies the phone number and the scope of contact—such as whether it covers appointment reminders, surveys, or promotional outreach. We also ensure the call content aligns logically and topically with the context in which consent was given, as required by the FCC’s one-to-one consent rules effective December 2023. Lists purchased without clear permission records are flagged and typically declined, because we tell clients plainly if the list won’t support the campaign before any spend occurs.
To operationalize consent verification, teams should follow a pre-launch checklist: confirm list origin and permission status; match each number to a signed consent record specifying call purpose and technology; scrub against the National DNC Registry at least every 31 days; maintain an internal DNC list honored for a minimum of five years; and establish immediate opt-out handling during the campaign. These steps aren’t just defensive—they form the foundation of a sustainable, trust-based calling program that respects consumer preferences while delivering measurable outcomes.
Running Compliant AI Calling Campaigns Without Building a Compliance Team
Building a TCPA-compliant calling program sounds like a job for a legal team — until you realize most of it comes down to structure. The caller bears the burden of proving consent, with no exception for a good-faith mistake, which means the real work happens before the first call is ever placed.
A managed approach starts with scope. Consent only covers content that is "logically and topically" related to the context in which it was given, and under the FCC's one-to-one consent rules, a single consent can no longer cover multiple sellers. Running each campaign around one clear goal — a reminder, a qualification, a renewal — keeps every call inside the consent that actually exists.
Because AI-generated voices are treated as artificial voices under the TCPA, disclosure and opt-outs can't be afterthoughts. Recipients can revoke consent "at any time by any reasonable means", so every call needs a clear AI disclosure plus keyword opt-outs like STOP and REVOKE, honored immediately and logged. Company-specific DNC requests override even prior written consent and must be honored for at least five years, so opt-out and DNC logs should ship with every campaign as standard deliverables — not as a favor.
A structured campaign process covers the remaining bases:
- List and consent review before launch, with bought lists lacking permission records flagged or declined
- Approved calling windows that respect the 8 AM – 9 PM local time rule and state-specific quiet hours
- Script, disclosure, and escalation approval before anything dials — nothing launches until you sign off
- Outcome reports with disposition codes and opt-out logs routed back into your CRM
The stakes justify the discipline. Statutory damages run $500 per violation, up to $1,500 if willful, and regulators increasingly target owners and officers personally, according to legal analysis. With class action judgments exceeding $925 million in recent years, "we thought the list was fine" is not a defense.
My AI Call Center builds this structure into every campaign: reviewed lists only, one goal per campaign, and opt-outs logged and honored immediately across all campaigns. The first campaign review is free, and you'll know the full number before approving launch.
Plan your campaign with a free campaign review — start with your goal, your list, and your consent records, and find out plainly whether the list will support the campaign before you spend anything.
Frequently Asked Questions
Does the TCPA require consent to make calls, or can I call anyone if I have their phone number?
What type of consent do I need for AI-powered calls to cell phones if the call is for telemarketing?
Can I use one consumer's consent to make calls for multiple different businesses or brands I own?
If someone asks to stop receiving calls during a conversation, do I have to honor that immediately?
How often do I need to check the National Do Not Call Registry to stay compliant?
Are there any exceptions to the TCPA consent rules if I made a mistake but acted in good faith?
Turn Compliance into Your Competitive Edge
The TCPA doesn’t just demand consent—it reshapes how businesses should approach outbound calling: with precision, respect, and proven permission. As we’ve seen, the stakes are real—statutory damages start at $500 per call, FCC fines can reach $26,000 for intentional violations, and class actions have topped $925 million. But compliance isn’t just about avoiding penalties; it’s about building trust. When you verify consent upfront, honor opt-outs immediately, and align every call with the scope of permission given, you’re not just checking a legal box—you’re running campaigns that consumers actually want to receive. That’s how you improve list quality, boost engagement, and protect your brand. For organizations using managed services like My AI Call Center, this discipline is built in from the start: list and consent reviews happen before launch, scripts are approved, and outcomes flow back into your CRM. The result? Fewer risks, clearer data, and calls that confirm, qualify, and connect—without the guesswork. If you’re ready to run a campaign the right way, start with a free campaign review—bring your goal, your list, and your consent records, and we’ll tell you plainly whether your list will support the call before you spend anything.