The Telephone Consumer Protection Act (TCPA) does not have a separate rulebook for AI. A text written by an LLM and sent by software is an automated text, so the usual rules apply: get the right consent first, identify who is sending, and honour opt-outs quickly. What changed in 2026 is how opt-outs work, through an FCC order that takes effect on November 25, 2026.
Does the TCPA cover AI texts?
Yes. The FCC has long treated text messages as "calls" for TCPA purposes. Texts sent automatically to mobile numbers fall under the consent rules regardless of whether a template, a human or an LLM wrote the words. The AI part changes nothing about consent; it adds risk, because a model can produce content (such as a promotion) that your consent does not cover.
For voice, the FCC was explicit. Its February 8, 2024 declaratory ruling held that AI-generated voices, including voice clones, are "artificial" voices under the TCPA, so calls using them need prior consent, as Cooley summarised. It did not ban AI voice technology; it confirmed the existing rules apply.
What consent do AI texts need?
| Message type | Typical consent standard | Example for an AI agent |
|---|---|---|
| Customer-initiated reply | Customer asked for the information | Answering a question the customer just texted |
| Informational, automated | Prior express consent | Appointment reminders, order updates |
| Marketing, automated | Prior express written consent | Offers, promotions, upsells |
| Opted-out number | None; do not send (beyond a confirmation) | Anyone who texted STOP |
The line that trips AI agents up is between informational and marketing. If your support bot adds "By the way, we have 20% off whitening this week", that message may need marketing-level consent. Constrain the prompt, filter outbound text in code and keep your 10DLC campaign aligned with what the bot actually sends.
What changed in the FCC's opt-out rules?
The revocation rules have moved several times since 2024.
- FCC adopts consent revocation rules, including "revoke-all"
- Most revocation rules take effect; revoke-all delayed one year
- FCC delays revoke-all again, to January 31, 2027
- FCC adopts order overhauling revoke-all (FCC 26-67)
- Amended rules take effect, superseding the 2027 date
The order, FCC 26-67, was published in the Federal Register on October 26, 2026 (91 FR 67214) and takes effect November 25, 2026. As Nelson Mullins and Troutman Pepper Locke, also summarise, it does the following:
- Narrows revoke-all. An opt-out sent in response to an informational message applies only to that category of informational messages. An opt-out from marketing still applies to all future marketing calls and texts from that sender.
- Allows exclusive opt-out methods. A sender may designate one or more of three automated methods as the only way to revoke: an interactive voice or key-press opt-out on calls, a reply text using standardized words, or a designated website or phone number. The method must be clearly and conspicuously disclosed in each message.
- Seven standard reply words. If you use reply-text opt-outs, you must accept stop, quit, end, revoke, opt out, cancel and unsubscribe. Including one of them (for example, "Reply STOP to opt out") satisfies the disclosure.
- No exclusive method, no shortcut. Senders that do not designate an exclusive method must keep honouring opt-outs made by any reasonable means.
- Ten business days. Revocations must be honoured within a reasonable time, no more than ten business days. A companion proposal (FNPRM) asks whether to shorten this; some summaries mention seven business days, but that has not been adopted.
- One-way texts. If replies are not possible, each text must say so and offer another reasonable opt-out route.
Earlier coverage, including our own research notes, cited a January 31, 2027 date for revoke-all. That date is out of date: FCC 26-67 replaces it, and the amended rules apply from November 25, 2026.
What should an AI texting program do in practice?
- Map your messagesClassify every message the agent can send as reply, informational or marketing.
- Collect the right consentUse written consent language for any marketing; store timestamp, wording and source.
- Gate the modelHandle opt-out words and HELP in code; block outbound text outside the registered use case.
- Disclose the opt-outInclude "Reply STOP to opt out" or your designated method in messages.
- Honour fastStop sending immediately in software; do not rely on the ten-day maximum.
- Keep recordsLog consent, opt-outs and message content for audits and disputes.
The CTIA Messaging Principles add carrier-level expectations on top: opt-in confirmation messages, HELP responses, message frequency disclosures and a public privacy policy. Carriers enforce these through 10DLC vetting even where the TCPA is silent. Our SMS opt-in and opt-out rules guide turns them into a checklist.
What about lead follow-up and outbound AI texting?
Outbound is where the risk concentrates. An AI that texts web leads, re-engages old customers or follows up after a quote is sending automated messages to people who did not just text you. Before turning it on:
- Confirm each contact's consent covers the content the AI will send.
- Check state laws; several states have their own telemarketing and "mini-TCPA" rules with stricter time-of-day and consent requirements. We have not catalogued them here.
- Respect quiet hours in code.
- Make sure the AI never claims to be human when asked.
Our guide to AI SMS lead qualification covers how businesses structure these flows.
How does this compare with the UK?
UK marketing texts fall under PECR rather than the TCPA. The structure is similar (consent or a narrow "soft opt-in", plus an opt-out in every message) but enforcement is by the ICO, with maximum fines now £17.5 million or 4% of global turnover. See our UK PECR guide, and personalagent.uk's explainer on the Data (Use and Access) Act.
Bottom line
Treat your AI agent like any other automated sender. Match consent to message type, keep the model inside that scope, handle the seven opt-out words in code and stop sending immediately. Then review your opt-out disclosures before November 25, 2026, when the FCC's amended rules take effect.



