The Ten-Business-Day Clock Nobody Set

There is a widespread and comfortable belief that the FCC's consent-revocation rules got delayed. It is half right, and the half that is wrong is the expensive half.

The rules took effect on April 11, 2025. What got delayed was one specific provision, and understanding which one separates the operators who are currently compliant from the ones who think they have another year.

What is in force right now

Under the rule as adopted, a consumer may revoke prior express consent in any reasonable manner that clearly expresses a desire to stop receiving calls or texts. Not through a designated channel. Not using a specific word. Any reasonable manner.

The FCC identified a set of standardized keywords that must be treated as per se reasonable: stop, quit, revoke, opt out, cancel, unsubscribe, and end. Those are the floor, not the ceiling. Per BCLP's analysis, revocation can arrive by voicemail or email to any number or address where a consumer could reasonably expect to reach the caller, and even an in-person verbal statement carries a presumption of reasonableness. That presumption matters more than it looks: it shifts the burden onto the business to prove a given method was unreasonable.

Once received, the request must be honored as soon as practicable and no later than ten business days.

There is one narrow allowance. A single clarification message may be sent, within five minutes, containing no promotional content. One message. Five minutes. Anything else in that window is not a clarification, it is a violation with a timestamp on it.

What actually got waived

The delayed piece is the "revoke-all" provision: the requirement that a revocation made in response to one type of message be applied to all future robocalls and robotexts from that caller, including on unrelated matters.

The FCC first waived that portion for a year to April 11, 2026. Then, in a Second Extension Order issued January 6, 2026, it pushed that same portion to January 31, 2027.

So the scope question got postponed. The clock did not. A business that reads "the rule was delayed" and files it under next year's problems has confused a narrow waiver on cross-subject application with a general reprieve on honoring opt-outs at all.

This is general commentary on published regulatory materials, not legal advice, and anyone operating under these rules should confirm current status with counsel. The FCC has moved this date twice already.

Why the requirement is architectural

Reading the rule as a policy question makes it sound manageable. Reading it as a systems question makes it obvious what it demands.

Revocation can arrive through any channel a consumer might reasonably use. That means the detection surface is not a keyword parser on the SMS gateway. It is every inbound path: texts, voicemail transcripts, email replies, web forms, and a note an employee typed after a phone call.

Then it has to propagate. A revocation received by text must suppress voice calls. One left on a voicemail must reach the SMS platform. Per the rule, it applies to both robocalls and robotexts regardless of which channel carried the request. In a typical stack that means a dialer, a CRM, a marketing automation platform, an internal suppression list, and whatever a partner or affiliate is running, all reaching agreement inside ten business days.

Most organizations do not have a mechanism for that. They have several systems, each with its own opt-out flag, synced by a person who exports a spreadsheet on Fridays.

And every continued contact after a missed revocation is a separate violation, which is what turns a synchronization bug into a per-message damages calculation.

The build that follows

The compliant architecture is not complicated to describe, which is not the same as easy.

One suppression record, authoritative, that every outbound system reads before it sends. Detection running on every inbound channel rather than one. A timestamped log capturing when the request arrived, through which channel, how it was interpreted, and when each downstream system acknowledged it. Propagation measured in minutes, because ten business days is the legal maximum and building to a legal maximum leaves no room for the week somebody is on holiday.

The clarification allowance is worth encoding literally: one message, five minutes, no promotional content, enforced by the system rather than by a person remembering the rule.

Ten business days sounds generous until it is a deadline you are measuring across five systems that have never spoken to each other.

Sources: FCC consent-revocation rules effective April 11, 2025 (revocation in any reasonable manner; per se reasonable keywords stop, quit, revoke, opt out, cancel, unsubscribe, end; honored as soon as practicable and no more than ten business days; one clarification message permitted within five minutes with no promotional content); BCLP (revocation by voicemail or email to any number or address where a consumer could reasonably expect to reach the caller; presumption of reasonableness for in-person verbal statements shifting the burden to the business; application to both robocalls and robotexts regardless of the channel used to revoke); Wiley and Consumer Financial Services Law Monitor (limited waiver of the "revoke-all" provision, first to April 11, 2026, then extended by the FCC's Second Extension Order of January 6, 2026 to January 31, 2027). General commentary on published regulatory materials, not legal advice.