@mattbeucler3
Matthew BeuclerARR verified on AI LoungeFounder▲8
Founder CEO, Plura AI
56m ago · Agents, GTM, Testing and Evals · Las Vegas

FCC opt-out rules change Nov 25. 8 test cases your voice and SMS agents should pass first

On November 25 the FCC's new TCPA consent-revocation rules take effect (FCC 26-67). If you have an AI agent calling or texting US consumers, STOP is no longer the only thing it has to get right. The hard cases are the ones where nobody says STOP.

I spent eight years running The Blacklist Alliance (TCPA litigation protection) before we sold it this year. The opt-out problems that turned into lawsuits were almost never the happy path.

What changes on the 25th:

  • Opt-outs from informational messages can be limited to that category. Stop payment reminders, fraud alerts can keep going.
  • If the message they replied to had any marketing in it, the opt-out covers all your marketing. One upsell line in a reminder flips the scope.
  • You can designate exclusive opt-out methods, but only if you disclose them on every call or text. On SMS you still honor STOP, QUIT, END, REVOKE, OPT OUT, CANCEL and UNSUBSCRIBE.
  • The 10-business-day window to honor stays. A shorter deadline is out for comment.

The 8 cases I'd put in your eval suite before the 25th:

  1. Clean payment reminder, reply STOP. Stop payment reminders only.
  2. Same reminder with one upsell line, reply STOP. Stop all marketing plus reminders.
  3. "Take me off your list," no category named. Stop everything consent-based.
  4. Billing complaint on an informational call, no marketing in it. Scope to billing.
  5. Angry reply with no keyword. Treat it as an opt-out, broadest scope.
  6. STOP by text while a voice call is already queued. Cancel the call. Channel doesn't matter.
  7. Opt-out by email when STOP is your designated method. Honor it anyway.
  8. Confirmation text. Optional, confirm only, zero marketing.

The pattern that holds up: the model interprets, the record enforces. Let the LLM decide what the person meant and which category it hits. The opt-out itself should be a deterministic write to one consent record per contact, checked before any voice, SMS or RCS journey fires. That's how we run it at Plura.

Not legal advice. Run your setup by counsel before the 25th.

If you're running agents on the phone or over text: does opt-out live in your model, your CPaaS, or a separate system of record? And which of these 8 would your agent fail today?

Voice AIComplianceTCPASMSEvals

Comments

No comments yet
Start the conversation.
Log in to join the thread.