TCPA consent revocation: what the FCC changed on 30 Sep 2026
FCC 26-67 lets callers name one opt-out method and limit some opt-outs to one type of call. What changed, what didn't, and a checklist for sales teams.
By the DialSavvy team5 min read
On this page
Under the TCPA, a person can withdraw consent to autodialed, artificial-voice or prerecorded calls and texts, and you must honor it within 10 business days. On 30 Sep 2026 the FCC changed how that works in FCC 26-67. You can now name the opt-out methods you accept, and an opt-out from one informational message no longer has to stop all of them.
The changes take effect 30 days after the order appears in the Federal Register. The FCC says it will announce the exact date in a Public Notice. As of mid-October 2026, check the docket (CG Docket No. 02-278) before you change your process.
Who this applies to
The consent revocation rule, 47 CFR 64.1200(a)(10), covers calls and texts that need consent under the TCPA. That means calls made with an autodialer or an artificial or prerecorded voice. For sales teams, that usually means:
- AI voice agents. Since FCC 24-17 (8 Feb 2024), the FCC treats AI-generated voices as “artificial or prerecorded voice” under the TCPA. Our article on AI voice agent consent rules covers the consent you need first.
- Prerecorded messages, including voicemails left by a recording.
- Automated texts, such as a follow-up after someone books a demo.
A rep who dials one number by hand and talks live is under a different rule. When a person says “stop calling me” on that call, the company-specific do-not-call rules in 64.1200(d) apply. They also give you a maximum of 10 business days, and you keep the request for 5 years. Our guide to the TCPA and B2B cold calling explains which numbers these rules reach.
What changed in FCC 26-67
| Topic | The 2024 rule | After FCC 26-67 |
|---|---|---|
| How people can opt out | Any reasonable method, and the caller must honor it | You can name one or more of 3 methods as the only ones you accept. If you don’t, any reasonable method still counts |
| Opt-out from an informational message | Stops all calls and texts that need consent from that caller (“revoke all”) | Can be read as covering only that type of informational message |
| Opt-out from a sales message | Stops all calls and texts that need consent | Stops all advertising and telemarketing calls and texts from that caller |
| Time to honor | A reasonable time, at most 10 business days | Unchanged. The FCC asks whether to shorten it |
| Confirmation text | Allowed within 5 minutes, with no marketing | Unchanged |
The “revoke all” wording from the FCC’s 2024 order never took effect. Bureau waivers pushed its start date to 31 Jan 2027, and the new rule replaces it.
The 3 methods you can name
You can choose one or more:
- An automated, interactive voice or key-press opt-out on the call.
- A reply text with a standard word: “stop”, “quit”, “end”, “revoke”, “opt out”, “cancel” or “unsubscribe”.
- A website or phone number you set up to take opt-outs.
There are two conditions. You must disclose the method “clearly and conspicuously” on the call or in the text. If you name reply texts, one standard word in each message is enough (“Reply STOP to opt out”), but you must accept all 7 words.
If you name a method, you don’t have to process opt-outs that arrive another way. If you name none, the old standard stays: any reasonable request counts. The FCC also declined to let callers decide when and how to tell people about their chosen method.
Informational vs sales messages
The category change helps teams that send both service messages and sales messages. Picture a software company that texts meeting reminders and also runs AI-voice callbacks to leads. If a customer replies STOP to a meeting reminder, the company may treat that as an opt-out from meeting reminders only.
The reverse doesn’t work. If a lead says “stop” to a sales callback, that opt-out covers every advertising or telemarketing call and text from the company, including AI voice and prerecorded ones. The FCC says there are no exemptions from consent for this category, so one request is enough.
What hasn’t changed
- You still need consent first. Sales calls with an artificial or prerecorded voice to mobile numbers need prior express written consent under 64.1200(a)(2).
- 10 business days is still the limit. Faster is better. The rule caps the delay; it isn’t a target.
- Messages from a texting system that can’t take replies must say so in each text and give another way to opt out.
- State laws can add their own rules. Check them with your counsel.
A checklist for your team
Use this before the effective date, then again once the FCC’s Public Notice confirms it.
- List every automated touch. Include AI voice calls, prerecorded voicemails, autodialed calls, and every kind of text. Mark each as informational or sales.
- Decide whether to name a method. If you name one, add the disclosure to every script and template, for example: “To stop these calls, press 9 now” or “Reply STOP to opt out.”
- Map opt-outs to categories. An opt-out from a sales touch must suppress every sales channel: AI voice, prerecorded messages and texts. Rep calls go on your do-not-call list.
- Route manual requests. If you name methods but someone asks a rep to stop, decide in writing what happens. Honoring it anyway is the simpler policy to train and to defend.
- Time the process. Measure the time from request to suppression, in business days. If your CRM sync runs weekly, that’s a problem.
- Keep records. Store the request, the channel, the category and the date it took effect.
The FCC’s further notice asks whether to shorten the 10-day limit, require two-way texting, require a single “revoke all” option, and decide how opt-outs apply to affiliates and separate business lines. Build your process so a shorter limit would only change a number in a config file.
How DialSavvy handles this
Before every call, DialSavvy checks the contact against calling hours in their time zone and against your do-not-call list. Both checks are live, with rule packs by country. DialSavvy Agents are in early access, and their calls are for people who agreed to them. AI-voice consent checks are coming. See /product/compliance/ for what each check covers.
If you’re rewriting your opt-out flow for this order, book a demo and bring your call and text templates. We’ll walk through where each opt-out lands.
Not legal advice. This is a plain summary of public rules as of Oct 16, 2026. Rules change and depend on who you call and how: check with your counsel before you rely on it.
Sources
- Report and Order and FNPRM, FCC 26-67 (adopted 30 Sep 2026, released 1 Oct 2026), Federal Communications Commission (docs.fcc.gov)
- 47 CFR 64.1200, Delivery restrictions, eCFR (ecfr.gov)
- Declaratory Ruling, FCC 24-17 (AI-generated voices under the TCPA, released 8 Feb 2024), Federal Communications Commission (docs.fcc.gov)
Checked against these sources by the DialSavvy team. How we write. Spotted an error? Email hello@dialsavvy.com.