The TCPA ‘Revoke-All’ Rule Lands January 2027: What US Outbound Teams Must Change

If your business calls or texts American consumers with anything automated — an AI voice agent, an SMS drip, a prerecorded reminder — there is a date you should have on the wall: January 31, 2027. That’s when the FCC’s delayed “revoke-all” provision of the TCPA consent revocation rule is now scheduled to take effect, after the Commission’s Consumer and Governmental Affairs Bureau pushed it back a second time on January 6, 2026 (Order DA 26-12, CG Docket No. 02-278). This guide covers exactly what’s already law today, what changes in January 2027, why the rule has slipped twice, and the operational work outbound teams should be doing now — because the sensible response to this delay is to build as if the deadline were tomorrow.

One thing up front: this is general information from an outbound-marketing operator, not legal advice. We run AI calling and SMS programs for US clients remotely and we live inside these rules daily, but your compliance calls belong with a TCPA attorney.

Book a call

How we got here: one rule, two delays

The short history matters, because half the confusion online comes from articles written before the latest order.

• February 2024. The FCC adopts the TCPA Consent Order (FCC 24-24, adopted February 15, released February 16, 2024) in CG Docket No. 02-278: consumers may revoke robocall/robotext consent in any reasonable manner, revocations must be honored within ten business days, and — the contested part — a revocation triggered by one message type reaches everything the sender robocalls or robotexts about.
• April 11, 2025. Most of the order takes effect, per the FCC’s Federal Register announcement (89 FR 82518). Days before, on April 7, 2025, the Bureau grants a waiver (DA 25-312) delaying only the revoke-all scope portion of § 64.1200(a)(10) until April 11, 2026. Banking and credit-union associations had argued they couldn’t yet process “a revocation sent in response to one business unit’s call or text so that all business units cease placing calls or texts to the consumer.”
• October 2025. The Commission opens a Further Notice of Proposed Rulemaking (FCC 25-76) seeking comment, in the Commission’s words, “on ways we can modify the requirement that a caller must treat an opt-out request made in response to one type of call to be an opt-out request for all types of calls or to modify it to give consumers greater control over their right to stop unwanted calls.”
• January 6, 2026. With the old deadline three months out, the Bureau issues DA 26-12: “we find that good cause exists to extend the effective date for this requirement until January 31, 2027.” Electric utilities had told the FCC compliance would take “substantial funds, personnel resources, and time”; the Bureau chose not to force that spend while the rule itself is under review. Law firms tracking the docket, including Hunton Andrews Kurth, flagged the same date.

Crucially, DA 26-12 is narrow. The order “does not alter the status quo relating to any other prior Commission rules or rulings addressing revocation of consent.” Everything below in the “already in force” section is live law right now — the delay buys time on exactly one thing.

What’s already in force today (and catches teams out)

Since April 11, 2025, under the 2024 rule:

• Revocation by any reasonable method. A consumer can kill consent however a normal person would: replying “stop,” “quit,” “end,” “revoke,” “opt out,” “cancel,” or “unsubscribe” to a text, using an automated voice or key-press opt-out on a call, or using a website or phone number you’ve designated. Each of those is reasonable per se — you can’t argue about it.
• Off-menu revocations count too. A voicemail or an email “to any telephone number or email address intended to reach the caller” creates, in the rule’s words, “a rebuttable presumption that the consumer has revoked consent.” “You didn’t use our official form” is not a defense.
• Ten business days, maximum. Revocations “must be honored within a reasonable time not to exceed ten business days from receipt of such request.” Modern platforms suppress in seconds; the ten-day ceiling exists for stragglers, not as a grace period to squeeze in final sends.
• One confirmation text, tightly limited. You may send a single confirmation of the opt-out — presumed lawful if it goes “within five minutes of receipt” — and it must contain no marketing. If you send multiple categories of messages, that confirmation may ask whether the consumer meant to stop all of them. If they don’t reply, the rule’s answer is already the 2027 answer: “the sender must cease all further texts for which consent is required.”

If any of that is news, start with our pillar guide to TCPA compliance for AI voice and SMS agents, which covers the consent tiers, quiet hours, state mini-TCPAs and penalty math this post deliberately skips. The one number worth repeating from it: TCPA statutory damages run $500 per call or text, up to $1,500 for willful violations, with no cap and an active class-action bar. Revocation-handling failures are mechanical to prove — the plaintiff has the “STOP” screenshot and your subsequent messages.

What actually changes on January 31, 2027

The delayed provision requires callers, in the Bureau’s phrasing, to treat a revocation “made by a called party in response to one type of informational message as applicable to all future robocalls and robotexts from that caller on unrelated matters.”

Translated into operations: today, if a customer replies STOP to your appointment-reminder texts, the conservative read is that your reminder campaign stops, and the waiver means you are not yet federally required to also silence, say, a different department’s informational robocalls. From January 31, 2027, that separation disappears. One STOP, sent to any robocall or robotext, and every automated call and text your organization sends that person on any unrelated matter must stop — marketing and informational alike, voice and SMS alike — unless a message is one they’ve specifically asked to keep (via the clarification mechanism) or falls under an exemption such as emergency calls.

The businesses that lobbied for delay — banks with separate fraud-alert, servicing and marketing stacks; utilities with outage-notification systems bolted to third-party vendors — are exactly the profile of organization that struggles here: multiple business units, multiple vendors, no shared suppression layer. Most small and mid-size US businesses have a simpler estate, which is the good news: for you, revoke-all is mostly a data-architecture problem, and a solvable one.

Today vs January 31, 2027: side by side

Could the rule change again before 2027?

Honestly: maybe. The Bureau delayed precisely because the Commission is reconsidering the requirement in FCC 25-76 — to “avoid imposing potentially unnecessary compliance costs” if the rule is modified — and the Commission has delegated the Bureau authority to extend again if needed. The FCC could soften revoke-all, give consumers a menu of what to stop, or leave it intact.

Our advice is to ignore the possibility. Every component the 2027 rule demands — unified consent records, cross-channel suppression, instant keyword handling — already pays for itself today by shrinking your exposure under the rules that are currently in force, and no plausible FNPRM outcome makes honoring opt-outs faster and more broadly a mistake. Teams that treated the April 2026 date as real are calm right now. Teams that banked on the delay get to re-run the fire drill against a January 2027 wall — with a docket that could also close without further extension.

The pre-2027 playbook for outbound teams

1. Build one record of truth for consent. If consent status lives separately in your dialer, your SMS platform, your CRM and a spreadsheet, revoke-all is unworkable. Consolidate to a single per-person record that stores what they consented to, when, from what source, at what scope — and a single revoked flag every sending system reads before every send.
2. Make suppression cross-channel by default. Wire a STOP text to also suppress AI voice calls to that number, and a key-press opt-out on a call to also suppress SMS. That’s the 2027 requirement, it’s the current rule’s safest read, and it’s what customers assume happens anyway.
3. Audit reply-keyword handling end to end. Test all seven per-se keywords, lowercase, with trailing punctuation, and inside longer sentences (“please stop texting me about this”). “Any reasonable method” means your intent detection needs to catch the messy versions — and your AI voice agents need to recognize a spoken “take me off your list” mid-conversation, confirm it, and write the revocation back to the record of truth in real time, not in a nightly batch.
4. Tag consent scope at capture. From 2027, the only way to keep (for example) delivery notifications alive after a marketing opt-out is the consumer’s explicit choice. Capture consent per message type now, and template your five-minute clarification text now, so “stop the promos, keep my reminders” is a real option rather than an all-or-nothing loss.
5. Pull vendors into the loop. If an outside platform sends on your behalf, revocations they receive are revocations you must honor everywhere, and vice versa. Contractually require suppression sync (webhooks or API, not weekly CSVs) and confirm the propagation completes well inside ten business days.
6. Mind revocation in reactivation campaigns. Old databases are where stale consent hides. Before any database reactivation program, wash the list against every opt-out record you hold across every channel — a 2024 STOP that only made it into your old SMS tool is still a revocation.

For the channel-level mechanics — keyword processing, quiet hours, carrier registration and sequence design — see our AI SMS outbound automation guide.

How we handle this at LeadsNow

LeadsNow AI is an Australian-built, remotely delivered AI lead generation and appointment-setting agency serving US businesses. Since 2017 our AI agents have booked 50,769+ sales appointments and generated 1M+ leads, and the platform was engineered around the consent-first model US law now demands: we don’t cold-call with AI at all (the written-consent rules make that a non-starter, as we detail in our AI cold calling and TCPA guide) — we work opted-in inbound leads and clients’ own databases. Opt-outs detected in any channel, spoken or texted, suppress the contact across all channels immediately; consent scope is stored per contact in one record. We publish 25 filmed client case studies and hold a 4.6-star rating across 43 Google reviews, and because we charge per result — per booked appointment — we have zero incentive to keep messaging people who’ve said stop: unwilling contacts don’t book.

FAQ

When does the TCPA revoke-all rule take effect?

January 31, 2027, under the FCC Consumer and Governmental Affairs Bureau’s order DA 26-12 (released January 6, 2026, CG Docket No. 02-278). This is the second delay: the provision was originally due April 11, 2025 with the rest of the 2024 revocation order, then waived to April 11, 2026, then extended to the current date.

Which TCPA revocation rules already apply right now?

Since April 11, 2025, consumers can revoke robocall/robotext consent by any reasonable method — including replying “stop,” “quit,” “end,” “revoke,” “opt out,” “cancel,” or “unsubscribe” to a text — and every revocation “must be honored within a reasonable time not to exceed ten business days from receipt,” per the FCC’s rule as published in the Federal Register (89 FR 15756, FCC 24-24). Only the revoke-all scope provision is on hold.

Does a STOP reply today stop just that one campaign?

Don’t run your program on that assumption. The waiver only suspends the federal requirement to extend one revocation to unrelated robocalls and robotexts from the same sender; the revocation itself is fully effective for the messaging it targets, and if you send a scope-clarification text and get no reply, you must stop all texts for which consent is required anyway. Treating every STOP as global today is both the safest legal posture and free practice for 2027.

Could the revoke-all rule change again before January 2027?

Possibly. The FCC is taking comment in a 2025 rulemaking (FCC 25-76) on whether to modify the requirement, and the Bureau holds delegated authority to extend the date again. Nothing is guaranteed in either direction — which is why we’d build the compliant architecture now and treat any further softening as a bonus.

We use an outside AI calling or SMS platform — whose problem is this?

Yours, legally: the consent obligations attach to the calls and texts made to your customers, and courts routinely reach the business on whose behalf messages were sent. Practically it’s shared — your vendor needs real-time revocation sync with your systems so that an opt-out captured anywhere suppresses everywhere. Ask any platform you’re evaluating to demonstrate cross-channel suppression, not just an SMS STOP handler.

Is “please stop texting me” valid if it doesn’t use an official keyword?

Yes. The seven listed keywords are reasonable per se, but the rule protects any reasonable revocation, and even a voicemail or email to an address “intended to reach the caller” creates a rebuttable presumption of revocation. Your keyword filter is the floor, not the definition — intent detection (human or AI) has to catch natural-language opt-outs too.

This article is general information for outbound-marketing operators, not legal advice. Rules cited were verified against FCC and Federal Register primary sources in August 2026; confirm current status with a TCPA attorney before relying on it.

See if we’re a fit

Three quick questions. If it’s a fit, our live calendar loads on the next screen. If it isn’t, we’ll point you to free resources instead — you won’t have to sit through a sales call to find out.