FCC TCPA Revocation Rule: How Opt-Outs Must Work

In February 2024, the Federal Communications Commission adopted an order in CG Docket No. 02-278 that rewrote the rules for how consumers revoke consent to robocalls and robotexts under the Telephone Consumer Protection Act (TCPA, 47 U.S.C. 227). The core provisions took effect on April 11, 2025. If your organization texts people, this rule governs how every opt-out must be treated.

The short version: consumers can revoke consent in any reasonable manner, senders cannot dictate an exclusive opt-out channel, standard reply keywords must always work, revocations must be honored within ten business days, and one confirmation message is allowed. This guide walks through each requirement in plain language.

What the Rule Says

The FCC codified revocation requirements at 47 CFR 64.1200(a)(10) through (a)(12). The obligations, stated plainly:

1. Any reasonable manner. A consumer may revoke prior express consent in any reasonable way that clearly expresses a desire not to receive further messages. Senders may not designate an exclusive means of revocation, so "you can only unsubscribe through our website" is prohibited.
2. Standard keywords are per se reasonable. Replying STOP, QUIT, END, REVOKE, OPT OUT, CANCEL, or UNSUBSCRIBE to a text constitutes a reasonable revocation, full stop. Senders must treat these as valid.
3. Other phrasings count too. A message that uses different words but clearly conveys the request, "please stop texting me", creates a rebuttable presumption of revocation. If a sender claims the request was not clear, that dispute is resolved on the totality of circumstances.
4. Ten business days to honor. Senders must honor revocation requests within a reasonable time, not to exceed ten business days from receipt. After that window, further covered messages violate the rule.
5. One confirmation text allowed. A sender may send a single message confirming the opt-out, within five minutes of receipt, and it may not contain marketing. If the sender runs multiple message programs, the confirmation may ask the person to clarify whether they meant all programs, and once the revoke-all provision takes effect, silence must be treated as revoking all.
6. Revocation-by-text must be supported. If you text consumers, you must be able to process reply-based opt-outs. Sending from a number that cannot receive replies while offering no equally easy alternative does not satisfy the rule.

One timing caveat. The FCC has temporarily stayed a single component of the rule: the requirement that a revocation made in response to one type of message be treated as revoking consent for all other message types on unrelated matters. The compliance date for that revoke-all scope has been extended to January 31, 2027 (FCC orders DA 25-312 and DA 26-12). Every other provision above took effect on April 11, 2025 and is fully enforceable now. Treating opt-outs broadly remains the safest practice in the meantime.

What Changed From the Old Regime

Before this order, revocation rights existed through FCC precedent and case law, but the mechanics were contested: senders argued about which channels counted, how fast processing had to be, and whether nonstandard wording was effective. The 2024 order settled those arguments:

What Compliance Looks Like Operationally

For a texting program, the rule translates into five operational requirements:

• Automate keyword handling. All enumerated keywords, with case-insensitive matching, should trigger immediate suppression. Manual processing risks blowing the ten-day window on volume days.
• Catch conversational opt-outs. Replies like "stop texting me please" or "wrong number, remove me" must reach a human or system that suppresses the number. An unmonitored inbox is a liability. FRANSiS uses an AI Powered Helper to flag conversational revocations that keyword filters miss.
• Suppress across your systems. Revocation applies to the consent, not the channel it arrived on. An opt-out received by text suppresses autodialed calls to that number too, and one received by phone call suppresses texts.
• Send the confirmation correctly. One message, within five minutes, no marketing content. If you operate multiple programs, this is your single chance to ask which ones they meant, and no reply means all.
• Log everything. Record the revocation, its timestamp, its channel, and the suppression action. The record is your defense.

The full opt-out lifecycle, including list hygiene and re-subscription, is covered in our guide to SMS opt-in and opt-out requirements.

The Stakes

The TCPA carries a private right of action with statutory damages of 500 dollars per violation and up to 1,500 dollars per willful or knowing violation (47 U.S.C. 227(b)(3)), and messages sent after a valid revocation are exactly the fact pattern plaintiffs look for. Because every message after the deadline is a separate violation, a mishandled opt-out that keeps a number on a broadcast list compounds quickly. State mini-TCPA statutes add parallel exposure in several states.

Treat the revocation rule as a floor, not a target: honoring opt-outs instantly, rather than within ten days, is both technically trivial for modern platforms and the practice carriers and the CTIA Messaging Principles expect. Our TCPA compliance checklist places revocation handling in the context of the full compliance program.

Auditing Your Revocation Handling

The rule rewards organizations that can prove their process, so audit it the way a plaintiff's lawyer would:

1. Test the keywords. From a phone outside your organization, opt in, then reply with each enumerated keyword in different casings and with trailing words ("STOP please"). Confirm suppression happened, the confirmation arrived within five minutes, and no further messages followed.
2. Test the conversational path. Reply with a plain-language refusal ("do not text me again") and verify it reaches suppression, not a dead inbox.
3. Test cross-channel suppression. If your organization also places calls, confirm a texted opt-out suppresses the number everywhere consent-based automation touches it.
4. Pull the logs. For a sample of past opt-outs, measure received-to-suppressed time and check the audit trail is complete: timestamp, channel, message content, action taken.
5. Check your vendors. If multiple platforms send for you, an opt-out captured by one must propagate to all. Fragmented suppression lists are how organizations with good intentions send actionable messages.

Run the audit quarterly and after any platform change. The records the audit produces are themselves evidence of a compliance program, which matters if a dispute ever reaches the willfulness question, where damages triple. Consent and suppression data deserve the same protection as any sensitive records; our security page covers how FRANSiS stores them.

The Rule as Consumer Experience

Regulations read differently when translated into what a person on the other end experiences. Under this rule, a consumer who texts STOP should see exactly one more message from you, a confirmation arriving within minutes, and then silence unless they return on their own. A consumer who writes "please quit texting me" should get the same result without having to know a keyword. A consumer who opts out by calling your office should stop receiving texts too, because revocation is about the consent, not the channel.

Programs that deliver that experience discover a side effect: complaint rates drop. Most carrier spam reports come from people who tried to leave and felt ignored, and every spam report damages sender reputation in a way opt-outs never do. A clean exit costs you one subscriber; a messy one costs you standing with every carrier filtering algorithm watching your number. The rule, in other words, mandates what good list management already wanted: make leaving effortless, and the list that remains is the one worth having.

Frequently Asked Questions

Does the rule apply to informational texts or only marketing?

The revocation provisions apply to consent-based robocalls and robotexts generally, not just marketing. When a person revokes, covered automated messages must stop regardless of content category, subject to the narrow exceptions the FCC recognizes for certain exempted informational calls.

Can I ask someone why they are leaving before processing the opt-out?

No. The single permitted confirmation message may clarify scope across multiple programs, but it cannot be a retention pitch, cannot contain marketing, and cannot condition the opt-out on further action. Process the suppression regardless of any reply.

What if someone opts out and then texts us a question later?

A consumer-initiated message after revocation permits a response to that inquiry, but it does not silently reinstate consent for your ongoing program. Re-subscription should be its own affirmative act, such as texting your opt-in keyword or completing your sign-up flow.

Does STOP to one of our numbers opt them out of all our numbers?

Under the rule's revoke-all provision, whose compliance date the FCC extended to January 31, 2027, revocation attaches to the consent, not to a single phone number. Even before that date, the safest practice is to suppress the contact across programs and sending numbers unless the person clarifies, in response to your confirmation message, that they meant only one program.

We are a small organization that processes opt-outs by hand. Is that allowed?

The rule does not mandate a technology, only the outcome: honored within ten business days, every time, including nonstandard phrasings. Manual processing that reliably meets that bar is lawful but fragile. Platform-level automation removes the failure mode.

Opt-Outs, Handled the Moment They Arrive

FRANSiS suppresses enumerated keywords instantly, flags conversational revocations with an AI Powered Helper, sends the compliant confirmation, and keeps the audit log, so the ten-day window never gets close. Contact us to see revocation handling done right.