Compliance & Automation
FCC Opt-Out Rules Take Effect November 25, 2026: What Changes for Your Texts, Reminders and AI Voice Agents
Short answer: Yes. The FCC scrapped the "revoke-all" opt-out rule, and the replacement now has a date. Order FCC 26-67, adopted September 30, 2026, was published in the Federal Register on October 26, 2026 (91 FR 67214) and takes effect November 25, 2026. From that day, a STOP on an informational text or robocall can apply only to that message category, a marketing opt-out still ends all marketing, and you may designate an exclusive opt-out method if you disclose it clearly on every call or text. Until November 25, the current rules apply: honor any reasonable opt-out within 10 business days. That leaves 19 days from today (November 6, 2026) to get your templates, CRM and AI voice agents ready. Live eCFR § 64.1200 is still the pre-amendment text until November 25 — see the cross-reference to 91 FR 67219.
Updated November 6, 2026: 19 days until FCC 26-67 takes effect on November 25, 2026. We re-checked live eCFR § 64.1200 today — it is still the pre-amendment rule (callers "may not designate an exclusive means"), with a cross-reference to the amendment at 91 FR 67219. Federal Register citation remains 91 FR 67214. Earlier October updates covered FR publication and the companion proposal.
That is a TCPA wiring problem, not just a policy memo. It changes how your CRM, texting platform and AI voice agent store and act on consent. Lawyers will explain the rule. This post explains how to build it, including how it connects to missed-call text-back and A2P 10DLC registration.
This is not legal advice. Have your attorney review your specific programs.
What did the FCC actually decide?
At its September 30 open meeting, the FCC voted 3-0 to adopt a Report and Order and Further Notice of Proposed Rulemaking, FCC 26-67 in CG Docket No. 02-278. The FCC released the final text on October 1, and it is largely unchanged from the draft circulated in September.
The order does three things that matter to clinics, law firms and home-services companies:
- Opt-outs by message type for informational messages. You may treat an opt-out as applying only to the category of informational call or text it was directed at, not everything you send. According to ABA Banking Journal, you must also give notice of how you will interpret an opt-out.
- Marketing still works the old way. In the order's own rule text, revocation requests made in response to calls or texts that contain an advertisement or constitute telemarketing "revoke consent to all future calls or text messages containing an advertisement or constitute telemarketing from that caller" (FCC 26-67; TechTimes).
- You can designate an exclusive opt-out method. Choose one or more of three methods: an automated voice or keypress opt-out on a call, a reply text using standardized words, or a website or phone number you designate (Nixon Peabody). The method must be disclosed "clearly and conspicuously" on the call or in the text. If you do that, you don't have to process opt-outs sent any other way. If you don't, you're still bound by the "any reasonable means" standard.
When do the new rules take effect?
November 25, 2026. The final rule, "Enhancing the Ability of Consumers To Control the Robocalls," ran in the Federal Register on October 26, 2026 at 91 FR 67214, and its dates line reads "Effective November 25, 2026." We read the full published text on October 27 to check the details below against the rule itself, not just the law-firm summaries. On November 6, 2026 we re-checked the live eCFR text of 47 CFR 64.1200: it still shows the pre-amendment (a)(10) ("Callers or senders of text messages … may not designate an exclusive means to request revocation of consent"), with a Cross Reference block pointing to the amendment published at 91 FR 67219, October 26, 2026. Until November 25, build against the published order and keep running the current "any reasonable means" process.
What about January 31, 2027? That was the waiver delay for the old 2024 revoke-all piece. The published order says the amended 64.1200(a)(10) "will go into effect at that time and supersede the delayed effective date of the relevant portion of that rule that was previously extended to January 31, 2027." So there is no second deadline to wait for.
Don't count on extra runway either. The FCC wrote that it declined a request "to extend the effective date up to 12 months after Federal Register publication." Until November 25, do not treat category-scoped stops or exclusive-method protections as live law. Keep honoring reasonable-method revocations within 10 business days, and use the remaining 19 days to finish the wiring.
Old rule vs. new rule
| Issue | 2024 rule (never took effect) | New rule (FCC 26-67) |
|---|---|---|
| STOP on an informational message | Revoked consent for all calls and texts that need consent | Can apply only to that category of informational message, with notice of how you interpret it |
| STOP on a marketing message | Revoked everything | Revokes all future marketing from you |
| How people can opt out | Any reasonable means | An exclusive method you designate and clearly disclose (otherwise, any reasonable means) |
| Text opt-out disclosure | No exclusive method to disclose | If reply text is your exclusive method, naming one keyword ("Reply STOP") is enough |
| Texts that can't receive replies | No specific rule | Each text must say two-way texting isn't available and give another way to opt out |
| Effective date | 2024 revoke-all delayed by waiver to Jan 31, 2027 | November 25, 2026 (published Oct 26, 2026 at 91 FR 67214); supersedes the Jan 31, 2027 waiver date |
What does "reply STOP" disclosure require now?
The final order added one useful clarification. If you designate reply texts as your exclusive method, you can satisfy the disclosure requirement by naming just one standardized word in each message. "Reply STOP to opt out" is enough (Inside Global Tech).
But you still have to honor all seven standardized words: "stop," "quit," "end," "revoke," "opt out," "cancel," and "unsubscribe."
This is where we see systems fail. Your texting platform might catch STOP, but does your CRM? Does your n8n or Zapier workflow that sends follow-ups check the same list? One gap and messages keep going to someone who opted out. Automatic texts like a missed-call text-back (see also our missed-call capture build) are a common place for that gap.
What if your texts can't receive replies?
The published rule text has a line that catches a lot of small-business setups. Some reminder and notification tools send from numbers that can't receive replies. Under the amended 64.1200(a)(10), if you "choose to use a texting protocol that does not allow reply texts," every text must clearly say that two-way texting isn't available "due to technical limitations of the texting protocol," and must give "reasonable alternative ways to revoke consent," such as a phone number or website.
Older scheduling and invoicing tools are the first place to look. Check every sender in your stack: if a STOP reply bounces or goes nowhere, either switch that tool to a two-way number or add the disclosure and an alternative opt-out to each template. The companion proposal asks whether to remove this one-way option entirely, so switching to two-way is the safer bet.
What if someone opts out a way you didn't designate?
This is where the exclusive-method choice pays off, or doesn't. The new rule text in FCC 26-67 splits callers into two groups:
- You designated an exclusive method and disclosed it on every call and text. You are "not required to process revocation requests made by any other means." A customer who emails "please stop texting me" hasn't used your method.
- You didn't designate one. You "must process revocation requests made by any reasonable means." If a consumer shows they used some other method, the rule creates a rebuttable presumption that they revoked consent, and a totality-of-circumstances test decides whether you can prove otherwise.
If nobody at your business ever chose a method, you're in the second group by default. That's the riskiest place to be once these amendments take effect. Pick a method, put it in every template, and keep honoring clear requests anyway. Your texting platform or carrier may also process STOP replies on its own, whatever you designate, so your CRM needs to hear about those too.
Can you send a confirmation text after someone opts out?
Yes, one. The rule allows a text that "merely confirms the text recipient's revocation request" with no marketing or promotional information. If it goes out within five minutes, it's presumed to fall within the person's prior consent. If it takes longer, you have to show the delay was reasonable (FCC 26-67, rule text). The Further Notice also asks whether a confirmation text could be used to clarify which category someone meant to stop.
So the confirmation should fire automatically from the same handler that records the opt-out, not from a human working a queue the next morning. Something like "You're unsubscribed from appointment reminders. No more reminder texts will be sent" is the pattern, with no offer attached.
Not sure where your opt-outs get lost? Book an AI systems assessment and we'll trace every automated text and call you send, and where a STOP stops (or doesn't).
Do these rules apply to AI voice agents?
For outbound calls, yes. In February 2024 the FCC ruled that AI technologies that simulate human voices count as "artificial or prerecorded voice" under the TCPA. That means AI callbacks, reminder calls and follow-ups need consent and must respect opt-outs. From November 25, an outbound AI agent that relies on an exclusive key-press or voice opt-out has to say that method on the call, so the opt-out line belongs in the agent's opening, not buried in a fallback. A real estate team whose AI calls sellers back is a common example, which is why our default in the realtor receptionist comparison is that AI answers and a human calls back. Prerecorded or artificial-voice calls that include marketing must still offer an automated voice or keypress opt-out.
Separately, in August 2024 the FCC proposed rules that would require businesses to disclose AI-generated calls when getting consent and at the start of the call. That proposal is still pending. It's not a final rule, and FCC 26-67 doesn't add an AI disclosure requirement. When we re-checked the eCFR on November 6, 2026, the robocall rule (47 CFR 64.1200) still had no AI-disclosure requirement, and the live (a)(10) text is still pre-amendment until November 25 (cross-ref 91 FR 67219). We build disclosure into our agents anyway, because it costs almost nothing and keeps you ahead if the rule is finalized. Our AI receptionist disclosure laws guide covers the state rules already in force, and pairs with missed-call text-back if you also send automatic SMS after a missed ring.
How to wire this into your systems
This is the part generic legal posts skip. It's also the part that determines whether you're compliant in practice.
1. Store consent by message type, not as a single flag
Under the new model, one "opted out: yes/no" field doesn't hold enough information. Consent has to be tracked at the category level.
In GoHighLevel or HubSpot, we set up separate consent fields for each bucket, for example:
- Appointment reminders
- Billing and payment notices
- Case or job status updates
- Review requests
- Marketing (one bucket, because one marketing opt-out kills all of it)
Every automated workflow checks its own bucket before it sends. A STOP on a reminder flips the reminder bucket. A STOP on a promo flips marketing.
Watch the classification. Troutman's advice is blunt: any promotional content makes a message telemarketing, and when in doubt, treat it as telemarketing. A "reminder" with a discount offer attached counts as marketing. Have counsel sign off on your category map.
2. Make STOP sync everywhere, fast
Most of our clients send from more than one place: Twilio, a CRM's built-in texting, a scheduling tool, an n8n workflow. An opt-out caught in one system has to reach all of them. It's the same sync problem we solved when we kept a local service company's CRM in step with invoicing and Jobber.
We route every inbound reply through one handler, usually an n8n workflow fed by a Twilio webhook. It matches all seven keywords, figures out which category the message was replying to, updates the CRM consent field, and blocks that category everywhere — whether texts leave from a custom stack or a GoHighLevel AI receptionist setup. Opt-outs currently have to be honored within a reasonable time, not to exceed 10 business days, and the FCC is considering cutting that to seven. A well-built system does it in seconds. The same handler should sit next to your A2P 10DLC campaign and consent records; carrier registration does not replace TCPA opt-out handling.
3. Give the AI voice agent a real opt-out
For outbound AI calls, we add a spoken and keypress opt-out ("Say 'stop calling' or press 2 at any time") that the agent recognizes mid-conversation. When triggered, it writes to the same CRM consent field through a webhook into the CRM and ends the call politely. If the caller asks for a person instead, the same agent should hand off cleanly. Here's how we set up AI-to-human transfers.
For inbound AI receptionists, including after-hours call answering and on-call dispatch for plumbing and HVAC shops, we still capture "stop texting me" requests and log them. Even if you've designated an exclusive method, honoring a clear request is good customer service. Recording those calls is a separate consent question, covered in our AI call recording laws guide. The FCC is also asking for comment on how to treat requests sent outside the designated method (EIA).
4. Put your exclusive method in every script and template
The exclusive-method protection only works if the disclosure is on every call and in every text. We update SMS templates, voice agent prompts, IVR menus and live-staff scripts together, so nothing goes out without it.
What's still open?
The order came with a companion proposal, published the same day at 91 FR 67239. Comments are due November 25, 2026, the same day the new rules take effect, and reply comments are due December 28, 2026, in CG Docket No. 02-278 through the FCC's ECFS. The FCC is asking about:
- A shorter window for honoring opt-outs. A joint letter from ABA, NCLC and ACA International suggests seven business days instead of ten.
- Removing the one-way texting option, so every text can take a STOP reply
- Requiring a "revoke all" method before a business can treat opt-outs by category
- How opt-outs apply across affiliates, separate lines of business or divisions
Build your system so a "revoke all" button and a two-way number are one setting away. Either may become required, and Brownstein's October 26 summary notes the proposals are largely based on that same industry and consumer-group framework.
Related builds while the runway closes
Use these Wrk Less posts alongside this opt-out wiring guide:
- AI receptionist for after hours — closed greetings and message vs escalate
- AI receptionist lead capture — structured fields into the CRM
- AI receptionist disclosure laws — AI announcement rules + the same Nov 25 countdown
- Missed-call text-back and TCPA — when an automatic text after a missed call is informational vs marketing
- AI receptionist holiday hours — Thanksgiving and Christmas sit on the same consent calendar
- Orlando / Orange County AI receptionist — local Florida home-service playbook
Your checklist before November 25, 2026
- List every automated call and text you send, and from which tool
- Label each one informational or marketing (if in doubt, marketing)
- Create a separate consent field for each category in your CRM
- Choose your exclusive opt-out method(s) for texts and calls
- Add the disclosure to every SMS template, voice script and AI agent prompt
- Make sure all seven keywords are recognized: stop, quit, end, revoke, opt out, cancel, unsubscribe
- Find any tool that sends from a number that can't take replies, and switch it or add the required disclosure
- Route all inbound replies through one handler that updates every system
- Add voice and keypress opt-out to outbound AI voice agents
- Send one automatic confirmation text within five minutes, with no marketing in it
- Test it: send STOP to each workflow and confirm everything downstream halts
- Keep a log of opt-outs with timestamps
- Have counsel review your category map and disclosures
Get a consent and opt-out audit
The rule change takes one afternoon to understand. Fixing it across four tools that don't talk to each other takes much longer. That's the work we do.
At Wrk Less, we build the AI receptionists, reminder workflows and CRM integrations that clinics, law firms and home-services companies run on. A consent and opt-out audit maps every automated message you send, finds where opt-outs get lost, and rebuilds the wiring in the 19 days before November 25, 2026. If you're still choosing a platform, our AI receptionist pricing breakdown compares what the popular platforms cost at your call volume.
Book your audit with Wrk Less and go into the new rules with a system you can prove works.
Questions people ask
Did the FCC scrap the revoke-all opt-out rule?
Yes. On September 30, 2026 the FCC adopted order FCC 26-67, released October 1, which replaces the 2024 revoke-all approach for informational messages with category-scoped opt-outs and lets businesses designate an exclusive opt-out method if they disclose it clearly. The order was published in the Federal Register on October 26, 2026 (91 FR 67214) and takes effect November 25, 2026.
Does replying STOP to an appointment reminder stop every text from that business?
Not necessarily. Under the new order, a business may treat a STOP reply to an informational message, like an appointment reminder, as covering only that category. Marketing is different: opting out of one marketing message revokes consent for all future marketing from that business. The business must tell people how it will interpret opt-outs.
When do the new FCC opt-out rules take effect?
November 25, 2026. FCC 26-67 was published in the Federal Register on October 26, 2026 at 91 FR 67214, and the rule says it is effective November 25, 2026. As of November 6, 2026 that is 19 days away. That date supersedes the January 31, 2027 delay on the old revoke-all rule, and the FCC declined a request for a 12-month extension. Until November 25, keep honoring opt-outs made by any reasonable means within 10 business days — live eCFR § 64.1200 is still the pre-amendment text, with a cross-reference to 91 FR 67219.
Do these rules apply to AI voice agents?
Yes, for outbound calls. The FCC ruled in 2024 that AI-generated voices count as artificial voices under the TCPA, so consent and opt-out rules apply to AI callbacks and reminders. From November 25, 2026, an outbound AI agent that relies on an exclusive key-press or voice opt-out must clearly say that method on the call. A separate 2024 FCC proposal to require AI-call disclosure is still pending, not final.
What if my texting platform can't receive STOP replies?
Under the amended rule, a business that uses a texting protocol that doesn't allow reply texts must say in each text that two-way texting isn't available due to technical limitations, and give reasonable alternative ways to opt out, such as a phone number or website. The FCC's companion proposal asks whether to remove that one-way option, so switching to a two-way number is the safer choice.
When are comments due on the FCC's new opt-out proposal?
Comments on the companion proposal (91 FR 67239) are due November 25, 2026, and reply comments are due December 28, 2026, in CG Docket No. 02-278. It asks about shortening the ten-business-day window, requiring two-way texting, requiring a revoke-all method, and how opt-outs apply across affiliates.
Has the live eCFR already updated for FCC 26-67 opt-out rules?
Not yet as of November 6, 2026. The live eCFR text of 47 CFR 64.1200 still shows the pre-amendment (a)(10), including that callers may not designate an exclusive means to revoke consent, with a Cross Reference to the amendment at 91 FR 67219 (Oct. 26, 2026). The published Federal Register rule (91 FR 67214) takes effect November 25, 2026 — 19 days from November 6. Build against the published order now, but keep running any-reasonable-means honor periods until that date.
What should I change on my AI phone and text stack before November 25, 2026?
Map every automated call and text, label each informational or marketing, create category-level consent fields, pick and disclose an exclusive opt-out method (or keep any-reasonable-means), honor all seven STOP keywords, fix one-way text senders, route replies through one handler, and put voice/keypress opt-out on outbound AI agents. You have 19 days from November 6, 2026. Pair this with our disclosure-laws and missed-call text-back posts if those flows are live.