FCC Seeks to Revise TCPA Consent Revocation Rules

The FCC’s September 9, 2026, draft Report and Order and Further Notice of Proposed Rulemaking (“draft FNPRM”) would significantly reconsider the Commission’s current TCPA consent-revocation regime. Most notably, it would move away from the pending requirement that a consumer’s opt-out from one informational call or text automatically revokes consent for every future robocall and robotext from that business on unrelated matters, while also proposing new obligations to make revocation more accessible and easier to process.

The draft is scheduled for consideration at the FCC’s September 30 Open Meeting. Because it is still a draft, its language and proposals may change before adoption; none of its proposed modifications is currently effective merely because the draft has been released.

Current Consent-Revocation Framework

The FCC’s existing consent-revocation rules—principally in 47 C.F.R. § 64.1200(a)(10)—apply to calls and texts made under the TCPA provisions requiring prior express consent or prior express written consent. Since April 11, 2025, the rules have generally required callers and text senders to honor a consumer’s revocation of consent made through any reasonable method that clearly expresses a desire to receive no further covered calls or texts.  

The current framework has several important features:

Any Reasonable Means:  A consumer is not limited to a company’s preferred keyword, webform, telephone number, or channel. A reasonable request conveyed by text, voice, or another reasonable method must be honored.

No Exclusive Revocation Channel:  A caller or sender cannot require the consumer to use only one designated way to revoke consent.

Per Se Reasonable Text Replies:  “STOP,” “QUIT,” “END,” “REVOKE,” “OPT OUT,” “CANCEL,” and “UNSUBSCRIBE,” when sent in reply to a text, are deemed reasonable revocation requests.

Ten-Day Deadline:  Revocation requests must be honored as soon as practicable and no later than 10 business days after receipt.

Single Confirmation Text:  A sender may send one nonmarketing text confirming the revocation request; it must be the only additional message after receipt of the request.

Cross-Channel Application:  A revocation communicated through one medium can apply to covered calls and texts from the same caller or sender.

The FCC had also adopted a particularly broad “revoke-all” component: where a consumer replied to or otherwise revoked consent in response to one type of informational robocall or robotext, the caller generally would have to treat that request as revoking consent for all future robocalls and robotexts from that caller, including communications on unrelated matters. The FCC has delayed the effective date of that narrow portion of the rule to January 31, 2027, while the Commission considers the issue; the rest of the 2025 revocation framework remains in place.

What the Draft Would Change

The draft would give callers more ability to define the method and scope of an opt-out, provided that the consumer is given clear notice and a practical way to revoke.

Reconsidering the “revoke-all” rule

The core proposed change is to replace the automatic, business-wide effect of a revocation with a more context-specific approach. The FCC’s draft would allow a caller to interpret a revocation made in response to an informational call or text as applying only to the specific category of informational automated calls or texts to which the consumer directed the request—not necessarily to all unrelated communications from the company.

For example, if a consumer texts “STOP” after receiving a package-delivery update, an appointment reminder, a suspected-fraud alert, or a payment-related message, the company could potentially treat that opt-out as applicable to that category of communication rather than as a blanket instruction to stop every informational message from the company. The stated policy concern is that an overbroad default opt-out could cause consumers to lose communications they may still want, such as fraud warnings, healthcare reminders, security notifications, or delivery updates.

That would be a substantial operational change from the current deferred rule, which would otherwise require a single revocation to sweep broadly across unrelated messages from the same business.

Allowing an exclusive revocation method:  The current rule prohibits a caller or sender from designating an exclusive means to revoke consent. The draft would reconsider that prohibition and would allow a caller to designate one or more exclusive methods, if the method is clearly and conspicuously disclosed.  The draft identifies potential designated methods such as:

-       An automated, interactive voice-response or keypress opt-out mechanism during a call.

-       Replying to an incoming text using one of the FCC-recognized terms: STOP, QUIT, END, REVOKE, OPT OUT, CANCEL, or UNSUBSCRIBE.

-       A website or telephone number specifically designated to receive and process revocation requests.

If adopted in that form, the change would be significant for large organizations that currently must identify, interpret, route, and honor revocation requests received across a wide range of customer-service, email, text, voice, and other channels. It could permit companies to centralize revocation processing through designated pathways—but only if they give consumers a clear and conspicuous disclosure of those pathways and can reliably process requests received through them.

The draft does not mean that a company could hide the opt-out mechanism in terms and conditions or make it unduly difficult to use. The proposal’s durability would likely turn on the final rule’s disclosure standard, permitted methods, scope rules, and the FCC’s eventual interpretation of what constitutes a meaningful and accessible revocation process.

Requiring Two-Way Text Capability

The FNPRM would seek comment on requiring callers or senders to use two-way texting functionality so that consumers can revoke consent by replying to a text message.

This proposal targets a recurring operational problem: one-way or no-reply texting arrangements can leave consumers unable to use the most intuitive method of revocation—replying directly to the message they received. If adopted, companies using one-way messaging platforms, alphanumeric sender IDs, certain short-code configurations, or messaging vendors that do not consistently accept and process inbound replies could need to modify their platform architecture, vendor contracts, sender configurations, and opt-out workflows.

For marketers, the proposal could make “Reply STOP to opt out” not merely a commonly expected industry practice, but part of a broader federal requirement that the underlying program actually accept and act on replies.

Requiring a Revocation Method for all Robocalls

The FNPRM also asks whether callers should be required to provide a means to revoke consent in connection with all robocalls, not only those for which consent is legally required under the specific TCPA provisions covered by the existing rule.

Depending on the final scope, that proposal could affect informational, non-telemarketing, exempt, or otherwise consent-optional automated-call programs. The practical effect would be to turn opt-out availability into a more universal operational feature of automated-calling and texting programs—even where the caller believes it has another legal basis to contact the consumer.

This point warrants close attention because it could expand the universe of communications that must include, or otherwise furnish, an accessible revocation mechanism.

Revisiting The Compliance Clock

The FCC is also seeking comment on whether to revise the current time for callers to honor revocation requests. Under the existing rule, callers must act as soon as practicable and no later than 10 business days after receiving a reasonable revocation request.

The draft does not itself establish a replacement deadline. It opens the question whether 10 business days remains appropriate in light of contemporary messaging systems, consumer expectations, technical feasibility, and the cost of integrating suppression across call, text, CRM, and vendor platforms. Comments will likely focus on whether a shorter deadline is operationally realistic, whether different deadlines should apply to calls and texts, and whether particular industries or message categories need tailored treatment.

Treatment of Affiliates

Finally, the draft seeks comment on the treatment of affiliates in the consent-revocation framework.

This question is consequential for organizations with multiple legal entities, brands, lines of business, or affiliated companies that share customer data, marketing platforms, consent records, contact centers, and dialing or messaging vendors. The FCC may consider whether a revocation given to one entity should bind affiliated entities; whether a consumer must be able to opt out at an enterprise, brand, campaign, product-line, or entity level; and how companies should disclose the relationship between the sender and affiliates.

A final affiliate rule could require companies to map their corporate family, consent sources, shared customer databases, outbound calling/texting tools, and suppression-list architecture more carefully than they do today.

Operational Implications

The draft’s central theme is not deregulation in a simple sense. It would potentially narrow the sweeping effect of an opt-out and give businesses greater flexibility to prescribe revocation channels, but it may also require more universal opt-out capability, reply-enabled texting, and more sophisticated affiliate-level consent governance.

Businesses should not assume that a prospective ability to designate an exclusive opt-out channel eliminates all risk from natural-language revocations received elsewhere. Until a final rule is adopted and effective, the current “any reasonable means” rule remains operative, subject only to the narrow delayed effective date for the unrelated-matters component of the revoke-all provision.

What Happens Next

At the September 30 Open Meeting, the Commission may adopt, revise, or decline to adopt the draft Report and Order and FNPRM. If it adopts an FNPRM, the item will be published in the Federal Register and interested parties will receive a formal opportunity to submit comments and reply comments under the deadlines set in the adopted item and publication notice.

The record is likely to feature competing views:

- Consumer advocates may argue that category-specific or exclusive-channel rules could confuse consumers, dilute the practical effect of a clear “stop” request, and permit continued unwanted contact.

- Financial institutions, healthcare providers, retailers, delivery providers, and other high-volume informational communicators may argue that a broad revoke-all rule can suppress fraud, security, appointment, servicing, and other communications consumers value.

- Messaging and voice-platform providers may seek technically feasible standards for two-way texting, keyword recognition, message-category identification, cross-platform suppression, and affiliate data-sharing.

- Large enterprise callers may seek clear safe harbors for disclosures, machine-readable opt-out processing, documented consumer preferences, and allocation of responsibility among brands and vendors.

After the comment record closes, the FCC could issue a final rule, seek additional comment, or adopt only selected proposals. The timing is uncertain. The most important immediate point is that the FCC has not yet displaced the operative rules: companies must still honor reasonable revocations, cannot currently require an exclusive revocation method, and must process qualifying revocations as soon as practicable and within 10 business days.

For now, compliance teams should preserve existing TCPA opt-out controls while inventorying the systems and contracts that would be affected by a final rule: two-way text functionality, designated opt-out mechanisms, category-based suppression, affiliate-level data governance, and end-to-end proof of when a revocation was received and honored.

‍