On 6 January 2026 the FCC pushed the TCPA revoke-all rule back again, from 11 April 2026 to 31 January 2027. If you were racing a spring deadline, you just got a year. The catch is that the hard part was never the date. It’s that most contact centers keep opt-outs in the campaign that collected them, and revoke-all makes that arrangement illegal.
What revoke-all actually asks for
The rule is one sentence with a lot of engineering behind it: when someone revokes consent in response to one call or text, you have to treat that as revoking consent for all future calls and texts from you, including ones about completely unrelated things.
Read that again as a data problem. A customer tells your collections campaign to stop. Under revoke-all, your renewals campaign, your survey campaign and your SMS reminders all have to know, without anyone copying a number between lists.
Most platforms can’t do that today, because the opt-out is stored where it was collected.
The parts already binding, and the part that moved
It’s worth separating these, because a lot of teams have quietly assumed the whole rule is parked until 2027. It isn’t.
Since 11 April 2025 you have had to honour a revocation made by any reasonable method, and process it within 10 business days. That is live now. A reply of STOP, a spoken request to an agent, an email to a published address: all of it counts, and the clock is already running.
What moved to January 2027 is only the universal part, the bit that makes one revocation cover unrelated future messages.
Why I’d build it now rather than in December 2026
Here’s the honest argument for not waiting. The date has slipped twice, and the FCC has an open proceeding asking whether revoke-all should be modified or replaced. So yes, it might move again, and it might come back softer.
None of that changes what you should build. A single consent record per contact, consulted before every dial and every send, is what the 10-business-day duty already wants. It’s also what a state attorney general asks about, what your enterprise customers put in their security questionnaires, and what stops the specific failure where somebody opts out on Monday and gets a survey call on Thursday from a different campaign.
Teams that wait will do this in a rush in December, against a date that has a history of moving. That’s the worst version of the project.
What the change looks like in practice
The shift is small to describe and awkward to retrofit: campaigns stop owning consent and start reading it.
- One record per contact, not per list. Contact identity, current state, the timestamp, and how the revocation arrived. Everything else references it.
- Check at send time, not at import time. A list built on Monday is stale by Wednesday. The check belongs immediately before the dial or the message.
- Log the arrival, not just the state. When a regulator asks, “we suppressed it” is weaker than “the request arrived here, at this time, by this method, and here is the call that didn’t go out”.
- Decide what a caller means. Revoke-all applies per caller. If you run several brands from one platform, work out now whether they’re one caller or several, and write the answer down.
That last one catches people. It’s a business question wearing a technical costume, and it’s much easier to answer calmly in 2026 than under a demand letter.
Where this sits in ICTContact
ICTContact keeps do-not-call handling at the contact layer rather than inside individual campaigns, and exposes DNC entries through the API, so a revocation recorded once is visible to the campaigns that run afterwards. If you’re on an older setup where suppression lives in per-campaign lists, that’s the piece to move first, and it’s worth doing before you touch anything else.
If you’re planning wider changes to how outbound runs, our notes on compliance guardrails for AI contact centers and on where AI voice agents actually work cover the neighbouring ground.
Frequently asked questions
Is revoke-all in force right now?
No. As of the FCC’s 6 January 2026 order it takes effect on 31 January 2027. But the rest of the revocation rule, including the 10-business-day processing duty, has been in force since 11 April 2025.
Could the date move again?
It could. It has already moved twice, and there’s an open FNPRM asking whether revoke-all should be changed or replaced. Plan for the requirement, not the calendar entry.
Does an opt-out from a marketing text stop service calls too?
Once revoke-all applies, a revocation covers future calls and texts from that caller on unrelated subjects. The safe design assumption is yes, so build the consent record to be consulted by every channel and campaign type.
What counts as a reasonable method of revoking?
Broadly, whatever a person would reasonably use to say stop: replying to a text, telling an agent on the call, using a published email address or web form. You can’t insist on one channel and ignore the others.
We run several brands on one platform. Does one opt-out kill all of them?
It depends on whether those brands are one caller or several, which is a legal question about your setup rather than a software setting. Get an answer in writing now, because the platform has to be configured to match it.
What’s the single highest-value change to make first?
Move suppression out of campaigns and into one consent record per contact, checked at send time. Everything else in this rule gets easier once that exists.
The deadline moved. The design didn’t. If your opt-outs still live inside campaigns, that’s the work, and there’s now a comfortable year to do it properly instead of a panicked month to do it badly.