AI call consent and recording: a US planning guide

Legal status note: researched 2026-08-25 for general US planning. Requirements, effective dates, exemptions, litigation, and state law can change. Qualified counsel must review the exact workflow before launch.

AI calling and call recording are separate compliance questions. A business may need a lawful basis to place an artificial-voice call, required identity or opt-out disclosures, and a valid approach to recording or transcription. The answer changes with call purpose, number type, recipient, consent language, state connections, sector, and vendor chain. This guide is a planning checklist, not legal advice.

1. Classify the call before writing a script

Document whether the call is inbound or outbound; informational, transactional, servicing, healthcare, charitable, or telemarketing; made to a mobile, residential, or business number; manually or automatically initiated; and delivered with an artificial or prerecorded voice. Also record who is legally responsible and whether an exemption is being considered.

Purpose and content of the call
Inbound, outbound, and initiation method
Number and recipient category
Artificial or prerecorded voice use
Seller, caller, vendor, and beneficiary roles

2. Treat AI-generated voice as regulated call technology

In FCC 24-17, the FCC stated that AI-generated voices fall within the TCPA's artificial or prerecorded voice restrictions. The ruling explains that covered outbound calls require prior express consent absent an emergency purpose or exemption, with additional requirements where the message includes advertising or telemarketing. Do not turn this summary into a universal consent rule; counsel must classify the exact call.

Record the consent basis and scope
Match consent to purpose, caller, and number
Use required identification and disclosures
Design opt-out for applicable calls
Retain evidence and honor revocation

3. Review telemarketing separately

The FTC's Telemarketing Sales Rule and FCC rules can overlap, and state laws may add obligations. The FTC guidance says outbound telemarketing calls delivering prerecorded messages generally require the recipient's prior signed written agreement from the specific seller and an interactive opt-out, subject to the rule's scope and exceptions. Do-not-call, calling-time, abandonment, caller identity, recordkeeping, and truthful-sales requirements also need review.

Seller-specific permission
Do-not-call suppression
Required identity and sales disclosures
Interactive opt-out and voicemail path
Calling time, records, and campaign controls

4. Separate permission to call from permission to record

Consent to receive a call is not automatically consent to record or transcribe it. Federal law includes a one-party-consent provision in 18 U.S.C. § 2511(2)(d), while states may impose stricter requirements and interstate calls can create choice-of-law questions. Counsel should approve the disclosure timing, affirmative-consent method, refusal path, agent behavior, and states included in the deployment.

Determine every state's connection
Review audio, transcript, summary, and monitoring
Give a non-recorded or human alternative where required
Capture proof of disclosure and consent
Do not rely on a generic nationwide phrase without review

5. Make revocation and opt-out operational

An opt-out is not complete when it appears in a transcript. It must update the correct suppression source across calling systems, campaigns, vendors, and channels. FCC 24-24 addresses revocation by reasonable means and a timeframe not exceeding ten business days for covered requests; teams should verify current effective requirements and aim to suppress sooner where practical.

Recognize spoken and keypress requests
Update entity-specific suppression
Stop queued retries and downstream campaigns
Confirm only where legally permitted
Audit propagation and exception handling

6. Govern recordings and vendors after the call

Define why audio and transcripts exist, who can access them, how long they remain, whether they are used for model training, which subprocessors receive them, and how deletion, export, legal hold, incident response, and contract termination work. Sector rules may add requirements. Avoid collecting payment credentials, health data, or secrets in recordings unless the approved design requires and protects them.

Purpose and data minimization
Retention and deletion schedule
Access, audit, and export controls
Vendor and subprocessor obligations
Redaction, incident, and legal-hold process

Next step

Bring the call purpose, audience, states, script, consent source, recording design, channels, vendors, and retention plan. We will map the technical controls for counsel to review.

FAQ

Are AI-generated voice calls covered by the TCPA?

The FCC stated in FCC 24-17 that AI-generated voices fall within the TCPA's artificial or prerecorded voice restrictions. Application, consent, exemptions, and disclosures depend on the exact call.

Do all outbound AI calls require written consent?

Do not use one universal rule. Requirements depend on purpose, content, technology, number type, recipient, exemption, and overlapping FCC, FTC, state, and sector law. Telemarketing often carries stricter written-consent requirements.

Is consent to receive a call also consent to record it?

Not automatically. Calling consent and recording consent are separate analyses. Federal and state interception laws, interstate contacts, disclosure, affirmative consent, and refusal handling require counsel review.

Should the agent say it is AI?

The script should meet all applicable identity, artificial-voice, advertising, telemarketing, consumer-protection, and sector requirements. Even where wording is not expressly mandated, transparent disclosure may be a policy choice; counsel must approve it.

How should opt-outs work?

Recognize reasonable requests, update the authoritative suppression list, stop queued calls, propagate the change to vendors and channels, record the event, and monitor failures within the applicable deadline.

Can recordings be used to train models?

Only if the actual notices, consents, contracts, privacy commitments, sector rules, retention, security, and vendor terms support that use. Training should never be assumed from operational recording permission.