Opt-in and opt-out handling is the part of an AI texting agent that must never be left to the AI. The rules come from three layers: US law (the TCPA and the FCC's 2026 revocation order), carrier requirements (CTIA guidelines enforced through 10DLC vetting) and, in the UK, PECR. The practical answer is the same everywhere: get clear consent, confirm it, make opting out easy, and stop immediately when asked.

What counts as valid opt-in for an SMS agent?

The CTIA Messaging Principles list ways a consumer can show consent, including entering a number on a website, texting a keyword, signing up at a point of sale, opting in by phone menu, or starting the conversation themselves (where the business only replies with responsive information).

For AI agents, that last one matters. A customer who texts your number with a question has consented to an answer to that question. It does not automatically cover later marketing or unrelated messages. For marketing, US law generally needs prior express written consent; see our TCPA guide.

CTIA also recommends that consent be:

  • Specific to you and the campaign. Opt-ins should not be transferred, sold or shared.
  • Recorded. Keep the timestamp, method, the wording shown, the campaign, IP address, phone number and who consented.

What should the opt-in confirmation say?

For recurring messages, CTIA says to send a confirmation before anything else, containing:

  1. Program nameWho is texting and what the messages are about.
  2. Customer careA phone number or HELP instructions.
  3. How to opt outFor example, "Reply STOP to opt out".
  4. FrequencyThat messages recur, and roughly how often.
  5. FeesClear language such as "Msg & data rates may apply".

Example for an AI booking assistant:

Acme Dental: You're signed up for appointment texts from our AI assistant. Up to 4 msgs/month. Msg & data rates may apply. Reply HELP for help, STOP to opt out.

Which opt-out words must you accept?

Two sources set the list, and they overlap.

Source Words or rule Status
FCC order (adopted Sept 30, 2026; effective Nov 25, 2026) stop, quit, end, revoke, opt out, cancel, unsubscribe Required if you use reply-text opt-outs
CTIA guidelines Standard STOP wording; also act on stop, end, unsubscribe, cancel, quit and "please opt me out", ignoring case and punctuation Carrier best practice, enforced in vetting
PECR (UK) A simple, free opt-out in every marketing message Law; no fixed keyword list

The FCC order, FCC 26-67, takes effect on November 25, 2026. As Nelson Mullins and Troutman Pepper Locke explain, it lets senders designate exclusive opt-out methods: a key-press or voice opt-out on calls, a reply text using a standard word, or a named website or phone number. Each must be clearly disclosed in every message. You may disclose just one reply word, but you must honour all seven. If you do not designate an exclusive method, you must honour opt-outs made by any reasonable means, which in practice can include a customer writing "don't text me anymore" in their own words. For an AI agent, the safest design is to accept the seven words and plain-language requests.

Standard reply words (FCC 2026)
7
Maximum time to honour
10 business days
Final confirmation allowed (CTIA)
1
Further messages after that
0

How do you implement opt-out in an AI agent?

Put a deterministic gate in front of the model. A minimal version:

import re

OPT_OUT = {"stop", "quit", "end", "revoke", "opt out", "optout",
           "cancel", "unsubscribe", "stopall"}
HELP = {"help", "info"}

def normalise(text: str) -> str:
    return re.sub(r"[^a-z ]", "", text.lower()).strip()

def gate(sender: str, text: str, store) -> str | None:
    t = normalise(text)
    if t in OPT_OUT:
        store.opt_out(sender)          # durable write, timestamped
        return "You're unsubscribed from Acme Dental texts. No more messages will be sent."
    if t in HELP:
        return "Acme Dental: call 555-0100. Reply STOP to opt out."
    if store.is_opted_out(sender):
        return None                    # silently drop; never call the LLM
    if re.search(r"\b(stop texting|don'?t text|remove me|opt me out)\b", text.lower()):
        store.flag_for_review(sender, text)  # or treat as opt-out outright
    return "PASS"

Notes:

  • Exact matching on the normalised message catches "STOP", "Stop." and " stop ". Longer messages that merely contain "stop" ("stop by tomorrow?") should not trigger an opt-out, which is why CTIA warns about words that could cause unintentional opt-outs. Route those plain-language cases to a confirmation or human review.
  • Check your provider's built-in handling. Twilio and other providers can process standard keywords at the platform level; make sure your own database agrees with theirs so you do not message someone the platform has blocked.
  • Re-opt-in (START, UNSTOP) should also be handled in code and recorded.

What about opting out of one thing but not another?

The FCC's 2026 order narrowed "revoke-all". An opt-out sent in reply to an informational message (say, appointment reminders) applies to that category of informational messages; an opt-out from marketing applies to all of your marketing. If your AI agent sends both types, track consent per category and say clearly in the confirmation what the person has stopped.

Under the UK's PECR, the opt-out requirement applies to marketing; genuine service messages are generally separate, but customers rarely see the distinction, so be explicit. Our UK PECR guide has more.

Do opt-outs mean deleting data?

Not necessarily. You need to keep the opted-out number on a suppression list precisely so you never text it again. Separately, customers may ask you to delete their conversation history; in the UK and EU that is a data-protection request under UK GDPR or GDPR. Keep the minimum record needed to honour the opt-out. Consumers wondering how to remove their own data from texting agents can read our guide to deleting AI texting agent data.

Checklist before launch

  • Opt-in wording names your business, describes message type and frequency, and mentions fees.
  • Consent records are stored with timestamp, method and wording.
  • Opt-in confirmation is sent before any other message.
  • The seven FCC words and common plain-language requests are handled in code.
  • One opt-out confirmation, then silence.
  • HELP returns a fixed support message.
  • Suppression list is checked before every outbound send, including AI follow-ups.
  • Your 10DLC campaign describes the same keywords and replies.

For where this gate sits in a full system, see our SMS agent architecture guide.