TL;DR

  • Consent under the TCPA is not permanent. A consumer may revoke prior express consent — including prior express written consent — at any time, and callers must stop. Revocation is now the mirror image of consent: just as the caller must prove consent was given, the caller must prove revocation was honored.
  • The FCC’s revocation order finalized the standard: a consumer can opt out in any reasonable manner, and the caller must process the revocation within ten business days. The core requirements took effect April 11, 2025; the provision covering how revocation propagates across message programs takes full effect January 31, 2027.
  • “Any reasonable manner” means a consumer is not confined to a magic word or a designated channel. Replying STOP to a text works, but so does a reply of “stop texting me,” a verbal request on a call, or an opt-out submitted through any method the caller has held out. Courts have refused to enforce caller-imposed revocation formalities.
  • Revocation of consent for one type of message generally revokes consent across the relationship, subject to a narrow exception the FCC carved out. A consumer who opts out of texts about one product cannot be treated as still consenting to calls about the same subject matter.
  • The operational failure mode is not refusing to honor opt-outs — it is an opt-out that is received in one system and never reaches the one placing the call. In a lead-gen supply chain, revocation given to a publisher does not automatically travel to every downstream buyer, and the buyer still placing calls is the one who gets sued.

For years, TCPA compliance conversations centered almost entirely on the front end of the relationship: did the consumer give prior express written consent, was the disclosure clear and conspicuous, was the consent tied to the right seller. Revocation was treated as an afterthought — a footnote about honoring “STOP” replies.

That framing no longer survives contact with the current rules. The FCC has built out a detailed revocation regime, and litigation has followed the money into it. Revocation is now a first-class compliance obligation with its own standard, its own timeline, and its own proof burden. A caller can have flawless consent documentation for the moment the relationship began and still lose a case because it kept calling after the consumer said stop — and could not prove it processed the request in time.

This guide covers what revocation actually requires under the current FCC framework, the “any reasonable manner” standard and why caller-imposed formalities fail, how the ten-business-day clock works, the scope question of how far a single opt-out reaches, and — most importantly for anyone buying or selling leads — how revocation is supposed to propagate through a supply chain, and who inherits the liability when it does not.

What the FCC Revocation Rule Actually Requires

The FCC’s revocation rulemaking codified several requirements that had previously lived in guidance and case law. Three of them matter most operationally.

Consumers May Revoke in Any Reasonable Manner

The central holding is that a consumer may revoke consent through any reasonable means that clearly conveys the desire to stop receiving calls or texts. A caller cannot require that revocation come through a single designated method, a specific keyword, or a particular form. If a consumer replies to a marketing text with “stop,” “unsubscribe,” “quit,” “cancel,” “end,” or “opt out” — or a plainly equivalent message — the FCC treats that as a valid revocation the caller must honor.

This closes off a defense callers used to raise: that the consumer did not follow the “correct” opt-out procedure. Under the current rule, a revocation is effective when the consumer’s intent is reasonably clear, regardless of the channel or the exact words. A verbal “stop calling me” during a live call is a revocation. A reply email to a texting program’s confirmation, if that is a path the caller made available, can be a revocation. The burden is on the caller to have a mechanism that captures reasonable opt-outs, not on the consumer to find the one blessed path.

The Caller Has Ten Business Days to Stop

Once a consumer revokes, the caller must honor the request within ten business days of receipt. This is not “immediately” and it is not “eventually” — it is a hard, countable window. The ten-day clock is generous enough to accommodate real processing time across systems, and short enough that a caller who is still dialing three weeks later has no defense.

The practical significance is that the ten-day window presumes the caller has a system that can (a) receive the revocation, (b) route it to every calling or texting channel touching that number, and (c) suppress future contact — all inside ten business days. A caller that receives an opt-out in a customer-service inbox but has no pipeline to its dialer will blow the deadline not because it refused to comply, but because the request never got where it needed to go.

One Opt-Out Can Reach the Whole Relationship

The FCC addressed scope directly: revoking consent for one category of messages generally revokes consent for all robocalls and robotexts from that caller on that subject, not just the specific program the consumer replied to. A consumer who texts “STOP” to a promotional campaign has not merely unsubscribed from that one campaign — the caller must treat the number as revoked for related autodialed or prerecorded contact.

The FCC did preserve a narrow ability for callers to seek clarification. If a consumer’s revocation is genuinely ambiguous as to scope, the caller may send a single message confirming the request and asking which messages the consumer wants to stop — but that confirmation message itself must honor the opt-out if the consumer does not respond, and the caller cannot use the “clarification” exchange as a pretext to keep marketing. The provision governing how this propagation and confirmation logic operates across message senders is the piece with the January 31, 2027 full-effect date.

”Any Reasonable Manner”: Why Caller-Imposed Formalities Fail

The single most litigated revocation question is whether a consumer’s opt-out “counted.” Callers have historically tried to narrow their exposure by defining, in the fine print, exactly how revocation must occur — reply with this specific word, use this specific portal, call this specific number. The current rule and the case law behind it treat those restrictions with suspicion.

In Reid v. I.C. System, Inc., No. CV-12-02661 (D. Ariz. 2014), the court recognized that a consumer may revoke consent orally, rejecting the notion that revocation had to be in writing to be effective. Courts building on that principle have repeatedly refused to enforce caller-imposed revocation formalities where the consumer’s intent to stop was clear. The reasoning is consistent: the TCPA is a consumer-protection statute, and reading it to let a caller trap consent behind procedural hurdles the consumer never agreed to would defeat its purpose.

The FCC’s “any reasonable manner” standard now bakes that principle into the rules. The operational implication is that a compliance program cannot be built around recognizing a single opt-out keyword. It has to be built around detecting reasonable expressions of intent to stop — across text, voice, email, web, and any other channel the caller has opened — and treating each of them as a revocation event that starts the ten-day clock. A program that only listens for “STOP” and ignores “please take me off your list” is not compliant; it is exposed.

How Revocation Breaks in a Lead-Gen Supply Chain

Everything above is manageable when one company owns the entire relationship — it collected the consent, it makes the calls, it receives the opt-out. Lead generation almost never works that way, and that is where revocation becomes dangerous.

Consider the ordinary path of a purchased lead. A publisher captures consent on a landing page. The lead is sold to an aggregator, then to a buyer, then perhaps resold or matched to several buyers. The consumer, weeks later, replies “STOP” — but replies to whichever party most recently contacted them, or calls the number on a caller ID, or emails the publisher whose brand they vaguely remember. That revocation now exists in exactly one place in the chain. Every other party still holding the number has no idea it happened.

The party that gets sued is the one that placed the next call. And under the TCPA’s burden structure, that caller has to prove it had consent and did not have a revocation on file. “We never received the opt-out” is not a defense if the opt-out was given to a party in the caller’s own supply chain — a consumer is not required to figure out the org chart of everyone who bought their number. This is the revocation analog to the consent-provenance problem: a right that was validly exercised somewhere in the chain, but that never propagated to the party who needed to act on it.

Two structural facts make this worse. First, revocation is time-stamped and directional — it matters exactly when it was received and by whom, because the ten-business-day clock and the “on file” question both turn on that. Second, revocation, like consent, is a claim about something that happened on infrastructure the downstream caller does not control. A buyer cannot see the opt-out a consumer texted to a publisher three intermediaries back unless there is a mechanism that carries the revocation event downstream the way the lead itself traveled.

What a Defensible Revocation Program Requires

A revocation program built to survive litigation — not just to send confirmation texts — captures a defined set of elements. Missing any one of them tends to be where a case is lost.

Omnichannel capture. A mechanism that recognizes reasonable opt-out expressions across every channel the caller uses — SMS keywords and their equivalents, verbal requests on live and recorded calls, email replies, web opt-out forms, and any other path the caller has held out. Listening for a single keyword on a single channel is not enough.

A receipt timestamp. An immutable record of when each revocation was received, because the ten-business-day clock runs from receipt. A revocation with no reliable timestamp cannot prove the deadline was met.

Propagation to every calling surface. A pipeline that carries the revocation from wherever it was received to every dialer, texting platform, and campaign touching that number — inside the ten-day window. This is the step that most often fails silently.

Scope handling. Logic that treats a revocation as covering the full relationship by default, applies the FCC’s narrow single-clarification exception correctly, and never uses a “clarification” message as a marketing pretext.

Supply-chain propagation. For purchased or resold leads, a way for a revocation received by one party to reach every other party still holding the number. Absent this, a consumer’s valid opt-out to a publisher leaves every downstream buyer exposed on a request they never saw.

Authenticatable records. Finally, the revocation record has to be provable. Just as consent records need to be independently verifiable rather than self-asserted, a “we suppressed the number” claim is only as good as the tamper-evident, timestamped evidence behind it. A database row that says the opt-out was honored is worth little if the opposing party can dismiss it as after-the-fact reconstruction.

Revocation Compliance Checklist

  • Capture opt-outs across every channel you contact through — text, voice, email, web — not just a single SMS keyword.
  • Honor reasonable expressions of intent to stop, not only a designated word or portal. Treat “take me off your list” the same as “STOP.”
  • Timestamp every revocation at receipt and start the ten-business-day clock from that moment.
  • Route every opt-out to all calling and texting surfaces touching that number within ten business days.
  • Default to full-relationship scope; use the single-clarification message only when scope is genuinely ambiguous, and honor the opt-out if there is no reply.
  • Never send a “clarification” that is really a marketing message — the FCC and courts read that as continued contact after revocation.
  • For purchased or resold leads, propagate revocations downstream so every party holding the number learns it was opted out.
  • Keep authenticatable, timestamped records of when each opt-out was received and when contact was suppressed.
  • Audit for orphaned opt-outs — revocations received in one system (support inbox, publisher form) that never reached the dialer.
  • Confirm readiness for the January 31, 2027 propagation provision before the deadline, not after.

Key Takeaways

  • Revocation is the mirror image of consent. The caller must prove not only that consent was given, but that revocation — whenever it came — was honored within ten business days. Both are affirmative burdens the caller carries.
  • The “any reasonable manner” standard means a compliance program cannot rely on a single opt-out keyword. It must detect reasonable expressions of intent to stop across every channel the caller uses.
  • A single opt-out generally reaches the whole relationship. The narrow clarification exception is not a license to keep marketing, and the propagation logic behind it takes full effect January 31, 2027.
  • In a lead-gen supply chain, the deadliest failure is an orphaned opt-out — a valid revocation received by one party that never travels to the downstream caller who keeps dialing. The caller placing that call inherits the liability, and “we never got it” is not a defense when the opt-out lives elsewhere in its own chain.
  • The record that wins a revocation case is timestamped, channel-agnostic, propagated, and independently verifiable — the same properties that make a consent record defensible, applied to the moment the consumer said stop.

Revocation turns consent from a one-time event into a lifecycle that has to be tracked, propagated, and proven end to end. See how session-level records document not just that consent was given, but that it was honored when it was withdrawn — across the entire supply chain.