The 10-Business-Day Revocation Rule Is Live. The Other Half Keeps Getting Delayed.

The 10-Business-Day Revocation Rule Is Live. The Other Half Keeps Getting Delayed.

There are two halves to the FCC's consent revocation rule, and healthcare operators keep tracking the wrong one. The half that governs how a patient can revoke consent, and how fast you have to act on it, has been enforceable since April 2025. The half that would force a revocation in one channel to propagate across everything else you send has now been pushed twice and currently sits at January 31, 2027.

Confusing the two produces two opposite errors: treating the whole rule as future work, or building a cross-channel suppression project you did not need to finish this year. Here is what is actually in force.

What is enforceable right now

The operative text is 47 CFR 64.1200(a)(10). The FCC announced in the Federal Register that the addition of paragraph (a)(10), along with (a)(11) and the amendment to (d)(3), became effective April 11, 2025.

The rule says a called party may revoke prior express consent — including prior express written consent — "by using any reasonable method to clearly express a desire not to receive further calls or text messages from the caller or sender." Four elements matter operationally.

1. Certain methods are reasonable per se

A revocation made through an automated, interactive voice or key-press opt-out mechanism on a call; by replying to a text with "stop," "quit," "end," "revoke," "opt out," "cancel," or "unsubscribe"; or through a website or phone number you designated to process opt-outs is, in the rule's words, "definitively revoked." There is no room to argue about whether it counted.

2. Other words still count

If a reply text uses different words, the rule requires you to treat it as valid "if a reasonable person would understand those words to have conveyed a request to revoke consent." In a home health or hospice contact center, that language is not hypothetical. "Please stop calling my mother, she passed away last week" is a revocation. So is "we discharged, take us off the list." Neither is on the keyword list.

3. You cannot designate an exclusive channel

The final sentence of (a)(10) is blunt: callers "may not designate an exclusive means to request revocation of consent." A policy that only honors opt-outs submitted through the patient portal does not comply. Neither does one that requires a written request.

4. Ten business days is the ceiling, not the target

All revocation requests made "in any reasonable manner must be honored within a reasonable time not to exceed ten business days from receipt of such request." The same ten-business-day window applies under 64.1200(d)(3) to internal do-not-call requests, with records retained for five years.

There is also a texting-platform requirement worth flagging: if you use a protocol that does not accept reply texts, the rule requires a clear and conspicuous disclosure on each message that two-way texting is unavailable, plus reasonable alternative ways to revoke on each message. Agencies using one-way SMS reminder tools frequently miss this.

What keeps getting delayed

The 2024 order behind the rule also required callers to treat a revocation received in response to one type of message as applying to all future robocalls and robotexts from that caller on unrelated matters. That is the provision that has not taken hold.

Order	Released	Effect
Effective date notice	October 2024	(a)(10) effective April 11, 2025
DA 25-312	April 7, 2025	Extends the unrelated-matters scope provision to April 11, 2026
DA 26-12	January 6, 2026	"the effective date of section 64.1200(a)(10) is extended to January 31, 2027 to the extent discussed herein"

Read the ordering clause carefully, because it is the source of most of the confusion. The extension runs only "to the extent discussed herein" — meaning the cross-subject scope requirement. The reasonable-method standard, the per se list, the no-exclusive-means prohibition, and the ten-business-day deadline are not extended and are not waived.

What the rule does not reach

Precision matters more than coverage here, because overstating the rule is how compliance programs lose credibility internally.

• It governs robocalls and robotexts, plus telephone solicitations. Paragraph (a)(10) applies to calls and texts made pursuant to paragraphs (a)(1) through (3) and (c)(2) of the section. A manually dialed, live-agent, non-solicitation clinical call is a different analysis.
• It does not require you to record calls. Nothing in 64.1200 mandates call recording. It requires that revocation requests be honored and, under (d), that do-not-call records be maintained. How you evidence that is your choice; recording is one option among several, and it carries its own state-law questions that we have covered in our post on why the standard all-party consent state list is unreliable.
• Being a HIPAA covered entity does not exempt you from revocation. The healthcare provisions elsewhere in 64.1200 relax certain consent requirements; they do not create a right to keep calling someone who has told you to stop.

Where this is genuinely contested

Two areas are unsettled and should be treated that way in your policy.

First, the FCC's own rule text and its extension orders point in different directions on what "revocation" reaches during the waiver window. The rule states that when a called party uses a per se method, "that consent is considered definitively revoked and the caller may not send additional robocalls and robotexts." The bureau has separately waived the requirement to apply that revocation to unrelated subject matter until January 31, 2027. Agencies reading only the rule text and agencies reading only the waiver reach different conclusions about scope, and both positions are defensible on the documents. The conservative operational answer — suppress broadly — is also the one that survives whichever reading prevails.

Second, state law varies and is moving. A number of states have enacted their own telemarketing statutes with private rights of action, and several of them define covered calls, consent, and permissible calling windows differently from the federal rule. Federal compliance is a floor, not a safe harbor, and the analysis is state-specific. Counsel licensed in your operating states should make that call.

What to do this week

1. Find every channel a revocation can arrive on. Inbound calls, voicemail, reply texts, the general info email address, the website form, the patient portal, and anything a caregiver says to a scheduler in person. Write the list down. If a channel is not on your list, it is a channel where revocations are dying silently.
2. Time-stamp the clock. The ten business days run from receipt, not from when the request reaches the person who can process it. Measure your actual interval from first contact to suppression. Most agencies have never measured it.
3. Delete any exclusive-means language. Search your call scripts, IVR prompts, text footers, and admission packet for phrases like "opt-out requests must be submitted through." Rewrite them to describe one convenient method without excluding others.
4. Audit your one-way SMS tools. If any reminder or survey platform cannot accept reply texts, confirm each outgoing message carries both the two-way-unavailable disclosure and an alternative revocation route.
5. Train on the non-keyword revocation. Give intake and scheduling staff five real-sounding phrases that are revocations without the magic words, and a single place to log them. This is the highest-yield hour of training you will run this quarter.
6. Decide your scope posture in writing. Either you suppress across all message types now, or you do not and you have a documented plan to be ready before January 31, 2027. Both are defensible. Having neither is not.

Our home care call compliance checklist covers the adjacent recording, redaction, and retention questions that usually surface once this work starts.

The detection problem underneath

Every item above assumes you can tell when a revocation happened. In practice the hard cases are not the ones where someone texts STOP — those are handled by the platform. They are the ones spoken mid-conversation to a scheduler who was solving a different problem, and never coded as anything.

SurfacerIQ operates in the category of interaction intelligence: reviewing conversation content across full call volume rather than a sample, so that opt-out language and similar compliance-relevant statements are identified as events rather than left inside a disposition code. That is the capability class the ten-business-day clock quietly depends on.

This post is general information, not legal advice. Rules and effective dates in this area have changed repeatedly; verify the current text and any outstanding waivers with counsel before setting policy.

If you want to pressure-test how revocation requests move through your contact center, talk to us.