The Legal Baseline: AI Voices Require Consent Under TCPA

The FCC's February 2024 Declaratory Ruling settled the question: AI-generated voices are legally classified as artificial or prerecorded voices under the TCPA. This means prior express consent is required for all AI-powered calls, with written consent mandatory for marketing purposes — regardless of message content or existing business relationships.

Non-compliance carries significant risk, with statutory damages ranging from $500 to $1,500 per call and no aggregate cap. Recent settlements underscore the financial exposure, including a $19M class-action resolution against QuoteWizard and a $9.95M settlement involving Gen Digital in 2025–2026. These figures highlight why consent verification is not just a legal formality but a core operational safeguard.

• Consent must be specific to AI or prerecorded voice calls — general marketing permission is insufficient.
• An established business relationship does not exempt AI calls from consent requirements.
• Written consent is required for marketing calls in 47 states, with only Texas, Louisiana, and Mississippi recognizing oral consent post-Bradford ruling.
• Consent records must be documented, verifiable at call time, and retained for at least four years (seven recommended).
• Opt-out requests must be honored within 10 business days under rules effective April 11, 2025.

For organizations running AI-powered campaigns, this legal baseline transforms list discipline from a best practice into a compliance necessity. My AI Call Center integrates these requirements into its pre-launch process, verifying that consent records explicitly cover AI voice before any campaign begins — ensuring calls are not only effective but fully aligned with TCPA standards.

Consent Standards Vary by Call Type, Jurisdiction, and Documentation

Consent is not a single standard — it is a moving target that shifts depending on what the call is for, where the recipient lives, and what your records can prove. Getting this wrong is expensive: TCPA statutory damages run $500 to $1,500 per call with no aggregate cap, and recent class-action settlements have ranged from $4.75 million to $19 million (TCPA compliance analysis).

The consent tier depends on call purpose. Marketing AI calls require prior express written consent (PEWC) in 47 states, while informational or transactional calls only require prior express consent, which can be oral (TCPA compliance guidance). The FCC's thresholds mirror this: written consent for marketing calls to both residential landlines and wireless numbers, but only prior express consent for informational wireless calls (regulatory alerts).

Do not assume an existing customer relationship lowers the bar. It does not. "EBR does not exempt the call from the AI consent requirement. The artificial voice itself triggers the consent obligation" (compliance research). That means renewal, retention, and win-back campaigns against your own customer lists still need verified consent records.

A February 25, 2026 Fifth Circuit ruling in Bradford v. Sovereign Pest Control established that oral consent satisfies TCPA requirements for AI calls — but only in Texas, Louisiana, and Mississippi (legal analysis). It does not override the written-consent standard in the other 47 states. As one analysis puts it: "The defensive value of Bradford is real but narrow. It does not authorize anyone to abandon written consent capture for nationwide outbound programs" (TCPA compliance playbook).

Jurisdiction also follows the recipient, not the caller. A Texas company calling a Florida resident is bound by Florida's standard (compliance guidance).

Consent must also be specific. Documented consent must "explicitly include agreement to receive AI-generated or prerecorded voice calls" — general marketing consent is insufficient (AI calling compliance guidance). Acceptable formats include:

• Opt-in checkboxes on forms that specifically reference AI or prerecorded voice calls
• Signed agreements with clear consent language
• Recorded verbal consent, captured and logged cleanly

Because rules keep moving, compliance depends on infrastructure, not policy documents: "If consent cannot be confirmed, the call does not go out" (industry perspective). Records should be retained for at least four years to align with the TCPA statute of limitations, with seven years recommended by defense counsel (retention guidance).

This is why My AI Call Center reviews list source and consent records before any campaign launches, and flags bought lists without clear permission records. For nationwide programs, written consent capture is not just the conservative choice — it is the only standard that holds up across every jurisdiction your calls touch.

Operationalizing Consent: Documentation, Infrastructure, and Ongoing Compliance

Getting consent right on paper is only half the job. The other half is proving it — call by call, record by record, years after the fact.

Consent that cannot be verified at the moment a call is placed is functionally worthless. As one compliance analysis puts it, "If consent cannot be confirmed, the call does not go out" — and that requires integration between the consent system and the dialer, not a spreadsheet review before each campaign. Consent must also be specific to AI or prerecorded voice calls; general marketing permission does not qualify.

Acceptable documentation formats include:

• Opt-in checkboxes on web forms that explicitly mention AI-generated or prerecorded voice calls
• Signed agreements containing AI-specific consent language
• Recorded verbal consent, captured with a timestamp and the exact disclosure provided

Each record should capture the timestamp, the method of capture, and the specific disclosure the person agreed to, per the Texas Bankers Association's regulatory alert on the FCC ruling.

Retention matters as much as capture. The TCPA statute of limitations runs four years, and defense counsel recommend keeping records for seven to withstand late-filed claims. That means complete call records — attempts, dispositions, timestamps, and campaign linkage — not just the original opt-in.

Revocation is the other half of the lifecycle. Under rules effective April 11, 2025, recipients can revoke consent by any reasonable means, and callers must honor the request within 10 business days — though treating opt-outs as immediate is the safer standard. This is why My AI Call Center logs opt-outs and honors them on the spot, carrying them into client DNC records across all campaigns.

The stakes justify the rigor. TCPA statutory damages run $500 to $1,500 per call with no aggregate cap, and recent class-action settlements — including QuoteWizard at $19 million and Gen Digital at $9.95 million — show how quickly thin consent records turn into nine-figure exposure. TCPA filings are also up 95% year over year.

The practical takeaway: consent is an infrastructure problem, not a policy document. Any campaign against an approved, permissioned, or reviewed list should launch only after consent records are checked, documented, and wired into the calling system itself.