An AI voice agent can confirm an appointment, chase an unpaid invoice or follow up a web inquiry without a person on the line. Before it dials, one question has to be settled for each phone number: what did this person agree to.
Federal law answers that question with rules written for recorded messages, which the FCC has said apply to AI voices. This post sets out which consent goes with which kind of AI call, what the agent has to say, and what is still only proposed.
AI voice agent consent at a glance
Every outbound AI voice call needs prior express consent, marketing calls need it in writing under the FCC rule, and the agent must identify the caller and offer a way out.
The table summarizes the position in November 2026 with the source for each row. Two rows describe proposals or reports and are marked as such.
| Question | Short answer | Source |
|---|---|---|
| Is an AI voice an artificial voice? | Yes | FCC 24-17 (released 8 February 2024) |
| Consent for a non-marketing AI call to a mobile number | Prior express consent | 47 U.S.C. 227(b)(1)(A); 47 CFR 64.1200(a)(1) |
| Consent for a marketing AI call | Prior express written consent | 47 CFR 64.1200(a)(2), (a)(3) and (f)(9) |
| Must consent wording mention AI? | Not under a final federal rule; proposed in 2024 | FCC 24-84, as reported by Zian AI |
| Must the agent identify the caller? | Yes, at the beginning of the message | 47 CFR 64.1200(b)(1) |
| Must a marketing call offer an opt-out? | Yes, an automated interactive mechanism | 47 CFR 64.1200(b)(3) |
| Can consent be oral? | For marketing calls, one appeals court says yes under the statute | Bradford (5th Cir., 25 February 2026) |
| Any state disclosure rule? | California requires telling the person if a prerecorded message uses an artificial voice | Cal. Pub. Util. Code 2874 |
Why does the law treat an AI agent as an artificial voice?
The FCC ruled in February 2024 that AI technologies that generate human voices fall within the existing restrictions on artificial or prerecorded voice calls.
The ruling is FCC 24-17, adopted on 2 February 2024 and released on 8 February 2024. In it the Commission confirms that the statute's restrictions on the use of an 'artificial or prerecorded voice' encompass current AI technologies that generate human voices. It concludes that calls using such technologies 'require the prior express consent of the called party to initiate such calls absent an emergency purpose or exemption'.
The reasoning is short. Voice cloning and similar technologies emulate real or artificially created human voices, and the ruling calls them artificial voice messages because a person is not speaking them. The Commission adds that the statute 'does not allow for any carve out of technologies that purport to provide the equivalent of a live agent'.
That last sentence matters for conversational agents. A system that listens and replies in real time is still producing a synthetic voice. The ruling closes by saying its requirements apply to any AI technology that initiates any outbound telephone call using an artificial or prerecorded voice to consumers.
Which consent goes with which kind of AI call?
A non-marketing call needs prior express consent in any form, and a call that advertises or telemarkets needs prior express written consent under the FCC rule.
The statute bars artificial or prerecorded voice calls to mobile numbers, and to residential lines, without the prior express consent of the called party. The FCC's rule adds a second tier. Under 47 CFR 64.1200(a)(2) and (a)(3), a call that includes or introduces an advertisement or constitutes telemarketing requires prior express written consent. A footnote in FCC 24-17 applies that tier to AI calls directly.
Written consent is defined at paragraph (f)(9). It is a signed written agreement that clearly authorizes the seller to deliver advertisements or telemarketing messages using an automatic telephone dialing system or an artificial or prerecorded voice, names the telephone number, and discloses that agreeing is not a condition of purchase.
| AI call | Consent the FCC rule describes | Notes |
|---|---|---|
| Appointment or delivery reminder to a mobile number | Prior express consent, oral or written | No advertisement in the call |
| Sales or renewal offer to a mobile number | Prior express written consent | Signed agreement naming the seller and number |
| Sales call to a residential line | Prior express written consent | 64.1200(a)(3); listed exemptions aside |
| Follow-up to a web inquiry that pitches a product | Prior express written consent | The inquiry form needs the disclosures in (f)(9) |
| Call to a number with no consent record | No consent to rely on | 500 dollars per call, up to three times if willful or knowing, under 47 U.S.C. 227(b)(3) |
Does the consent have to mention AI?
No final federal rule says so; the FCC proposed an AI-specific consent disclosure in 2024 and it remains a proposal by the reports we reviewed.
The current definition of written consent refers to 'an artificial or prerecorded voice'. Since the FCC has ruled that an AI voice is an artificial voice, consent wording that tracks the definition covers the category an AI agent falls in. The definition does not use the words AI or artificial intelligence.
The FCC has proposed more. According to a vendor summary by Zian AI, a notice of proposed rulemaking, FCC 24-84, was adopted on 7 August 2024. It would define an AI-generated call, require a disclosure at the consent stage that the person is agreeing to AI-generated calls, and require a disclosure at the beginning of each such call. The same vendor reports that no final rule had appeared in the Federal Register as of 9 November 2026 and that the federal regulatory agenda lists the next action as undetermined. That status rests on a vendor blog. We did not check the docket ourselves.
Congress has a bill on the same subject. H.R. 1027, the QUIET Act, was introduced on 5 February 2025 and would require a disclosure at the start of a robocall that uses AI to emulate a human. Congress.gov shows no action beyond introduction. Adding a plain statement about AI to consent wording ahead of any rule is a choice to make with counsel.
What does the agent have to say on the call?
Under the FCC rule it must identify the business at the start, give a telephone number, and on a marketing call offer an automated opt-out.
Paragraph (b) of 47 CFR 64.1200 applies to all artificial or prerecorded voice telephone messages, and FCC 24-17 says these requirements apply to AI calls. At the beginning of the message, the call must state clearly the identity of the business, individual or other entity responsible for initiating it. During or after the message, it must state clearly a telephone number for that business, which may not be a 900 number or one with charges above ordinary transmission charges.
When the message includes or introduces an advertisement or constitutes telemarketing, paragraph (b)(3) requires an automated, interactive voice or key press-activated opt-out mechanism for the called person to make a do-not-call request. The rule says the mechanism must be presented within two seconds of the identification.
California adds a disclosure about the voice itself. Public Utilities Code section 2874 governs automatic dialing-announcing devices. It requires an unrecorded, natural voice announcement before the device operates, stating the nature of the call and the name, address and telephone number of the business represented, and asking whether the person consents to hear the prerecorded message. Since an amendment shown as current from 1 January 2025, the announcement must also inform the person called if the prerecorded message uses an artificial voice, defined as a voice generated or significantly altered using artificial intelligence. How that section applies to a conversational agent is a question for California counsel.
Can the consent be oral?
For non-marketing calls it always could be, and for marketing calls the Fifth Circuit held in 2026 that the statute does not require a writing.
On 25 February 2026 the Fifth Circuit decided Bradford v. Sovereign Pest Control of Texas. According to the Duane Morris summary, the case concerned prerecorded calls to a customer who had given his number orally. The court held that the FCC lacked statutory authority to require written consent for prerecorded telemarketing calls, because the statute asks only for prior express consent.
The summary describes the Fifth Circuit as the only federal appeals court to take this approach and the result as a patchwork across jurisdictions. The decision binds federal courts in Texas, Louisiana and Mississippi. The FCC's written consent rule remains in the Code of Federal Regulations.
What happens when the person tells the agent to stop?
The request is a revocation of consent, and the FCC rule sets an outer limit of ten business days to honor it.
Under 47 CFR 64.1200(a)(10), a called party may revoke consent by any reasonable method that clearly expresses a desire not to receive further calls or texts. The rule says a request made through an automated, interactive voice or key press-activated opt-out mechanism on a call is a reasonable means in itself. Requests must be honored within a reasonable time not to exceed ten business days.
The paragraph is being amended. Nelson Mullins reports that FCC order 26-67 takes effect on 25 November 2026. By its summary, a revocation in response to a marketing call or text ends consent for all future marketing robocalls and robotexts from that caller, and the ten-business-day limit stays. For informational calls, a caller may designate certain exclusive opt-out methods, including an automated voice or key-press mechanism, if it discloses them clearly on each call.
Whose job is consent: the business, the vendor or the platform?
The platforms' own documents place it with the business, and the 2026 cases show the cost when a vendor run goes out without it.
Retell's documentation for its dialer compliance checks lists screens for do-not-call registries, reassigned numbers and known litigators. It also states the limits. Results are a snapshot from the moment of the check and are not refreshed. If the provider cannot determine a match, the contact passes that check. Retell does not enforce calling hours. And in its words, 'Retell doesn't verify that you have consent to call a contact.'
The cases are recent. TCPAWorld, a blog run by a defense law firm, reported on 9 November 2026 that Finley v. Altrua settled for 1.1 million dollars over AI voice contacts to a class of about 900 people across nine days, in what it describes as essentially a test run by a vendor. In Lowrey v. Twilio and OpenAI, Virginia Lawyers Weekly reported that a federal court on 1 October 2026 declined to dismiss claims that the two companies made and initiated the calls. That is a pleading-stage ruling and decides nothing about liability. We have read reports of both matters and not the court filings.
Neither report moves responsibility off the business that directs the calls. A list check tells you a number is on a registry. Only the business's own records can show that this person agreed to hear from this seller at this number.
A consent record for an AI call
It should show who agreed, to what, for which number and seller, and what the agent said and did on each call.
The list below is drawn from the definition of written consent, the identification and opt-out rules, and the revocation rule. It describes what those rules make relevant. It is a starting point for a conversation with counsel and is not a statement of what any particular business must keep.
- The consent wording the person saw or heard, with the date and time
- The telephone number and the seller named in that wording
- Whether the wording refers to artificial or prerecorded voice calls, and whether it mentions AI
- The purpose of the campaign: informational or marketing
- The opening line in which the agent identifies the business
- The opt-out offered on the call, and any opt-out the person gave in their own words
- The called person's local time and how it was determined
- A flag on each call record that an AI voice was used
Common questions
Do AI voice agents need consent to call someone?
Yes, for outbound calls to mobile numbers and residential lines. The FCC ruled in February 2024 that AI-generated voices are artificial voices under the Telephone Consumer Protection Act, and such calls need the prior express consent of the person called unless an emergency or exemption applies.
Does an AI agent have to say it is an AI?
No final federal rule requires that as of early November 2026, by the reports we reviewed. The FCC proposed an in-call AI disclosure in 2024, and a bill in Congress would require one. California requires that a person be told if a prerecorded message sent by an automatic dialing-announcing device uses an artificial voice.
Is consent to robocalls enough for AI calls?
The federal definition of written consent refers to artificial or prerecorded voice calls, and the FCC has ruled that AI voices are artificial voices. The FCC's 2024 proposal would add an AI-specific disclosure, but it has not been adopted by the reports we reviewed. Check the current status before relying on older wording.
Do appointment reminders from an AI agent need written consent?
The FCC rule asks for written consent when a call includes an advertisement or constitutes telemarketing. A pure reminder to a mobile number needs prior express consent, which can be oral. A reminder that also promotes something may be treated differently, so the script matters.
Does the platform check consent for me?
Going by published documentation, no. Retell's compliance-check page says it does not verify that you have consent to call a contact, and that an inconclusive check lets the contact through.
What about inbound calls answered by an AI agent?
This post covers outbound calls. The provisions discussed here regulate calls that a business makes or initiates. We did not research inbound AI agents, and recording or disclosure laws may apply to them, so treat that as an open question for counsel.
Reviewed November 13, 2026
Consentra is software. Nothing on this site is legal advice, and using Consentra does not by itself make a business compliant with any law or carrier rule. Whether a rule applies to your business is a question for your counsel.
Sources
- FCC: Declaratory Ruling FCC 24-17, CG Docket No. 23-362 (released 8 February 2024)
- Cornell Legal Information Institute: 47 CFR 64.1200 (read November 2026)
- Cornell Legal Information Institute: 47 U.S.C. 227 (read November 2026)
- Zian AI: FCC NPRM 24-84 and AI call disclosure rules (vendor blog)
- Zian AI: TCPA 2026 settlements and AI calling (vendor blog, November 2026)
- Congress.gov: H.R. 1027, QUIET Act, 119th Congress (introduced 5 February 2025)
- California Public Law: Public Utilities Code section 2874 (text current from 1 January 2025; read November 2026)
- Duane Morris: The Fifth Circuit green lights oral consent under the TCPA for telemarketing calls (2 March 2026)
- Nelson Mullins: FCC adopts overhaul of TCPA consent revocation rules (2 November 2026)
- Retell AI Docs: Compliance checks (read November 2026)
- TCPAWorld: Altrua settles TCPA class action involving AI voice contact to about 900 people for 1.1 million dollars (9 November 2026)
- Virginia Lawyers Weekly: OpenAI, Twilio denied dismissal in Virginia TCPA lawsuit (12 October 2026)
