In consultation · Open for comment
A draft is open for comment. The text can still move before adoption. Primary document.
The Federal Communications Commission published a notice of proposed rulemaking on 26 October 2026 (FR Doc. 2026-21820, CG Docket No. 02-278) seeking comment on reducing the maximum timeframe for honoring TCPA revocation requests, requiring two-way texting protocols, offering a revoke-all method, and clarifying affiliate treatment. It affects every caller and texting platform placing robocalls or robotexts. The binding rule today remains 10 business days under section 64.1200(a)(10).
The Federal Communications Commission has opened a consultation that would tighten the TCPA consent revocation rules again, seeking comment on reducing the maximum timeframe callers have to honor revocation requests, requiring two-way texting protocols, offering a means to revoke consent to all robocalls, and providing greater specificity on affiliates (FR Doc. 2026-21820, 91 FR, 26 October 2026; CG Docket No. 02-278). The proceeding is at the notice-of-proposed-rulemaking stage. The operative rule today remains the 2024 standard: honor company-specific do-not-call and revocation-of-consent requests within a reasonable time not to exceed 10 business days after receipt.
The Commission has been narrowing the gap between a consumer saying "stop" and a caller acting on it for three years. On 8 June 2023 the Commission adopted a Notice of Proposed Rulemaking (FCC 23-49, CG Docket 02-278) to clarify and strengthen consumers' ability to revoke consent to receive both robocalls and robotexts, and to clarify callers' obligations to honor such requests in a timely manner.
That 2023 NPRM proposed a 24-hour deadline. Specifically, it proposed to amend the rules to strengthen the right of revocation by specifying reasonable methods to revoke while codifying the underlying right to revoke by any reasonable means; to require that, within 24 hours of receipt, callers honor company-specific do-not-call and revocation-of-consent requests for robocalls and robotexts subject to the TCPA; and to codify the Soundbite Declaratory Ruling, under which a one-time text confirming a consumer's request that no further text messages be sent does not violate the TCPA provided it merely confirms the opt-out request.
The Commission did not adopt 24 hours. In the resulting Report and Order (FCC 24-24), published in the Federal Register on 5 March 2024 as "Strengthening the Ability of Consumers To Stop Robocalls," it settled on a reasonable time not to exceed 10 business days. The 2026 proceeding reopens that number.
| Before | After | |
|---|---|---|
| 2023 NPRM proposal | Within 24 hours of receipt, callers honor company-specific do-not-call and revocation-of-consent requests | Not adopted |
| 2024 Report and Order (FCC 24-24) | — | A reasonable time not to exceed 10 business days |
The Commission is seeking comment on four discrete changes to the revocation regime. Per the 9 September 2026 FCC Fact Sheet accompanying the draft item, the Further Notice seeks comment on reducing the maximum timeframe for honoring revocation requests, requiring the use of two-way texting protocols that allow consumers to revoke consent via reply text message, offering a means to revoke consent to all robocalls, and providing greater specificity to affiliates. The stated objective is to ensure the rules reflect advances in technology and regulatory changes that permit callers to process revocation requests in a timely and cost-efficient manner.
The Federal Register publication of 26 October 2026 frames the same four questions: reducing the timeframe callers must honor revocation requests, requirements for two-way texting functionality, requiring a revoke-all method, and the treatment of affiliates.
| Proposal | As framed in the 9 September 2026 FCC Fact Sheet | As framed in the 26 October 2026 Federal Register publication |
|---|---|---|
| Revocation timeframe | Reducing the maximum timeframe for honoring revocation requests | Reducing the timeframe callers must honor revocation requests |
| Two-way texting | Requiring the use of two-way texting protocols that allow consumers to revoke consent via reply text message | Requirements for two-way texting functionality |
| Revoke-all mechanism | Offering a means to revoke consent to all robocalls | Requiring a revoke-all method |
Alongside the Further Notice, the Commission's draft Report and Order would allow callers to interpret a revocation request as applying only to the specific category of informational robocalls to which the revocation was directed and not all robocalls for which consent was given; allow callers to designate an exclusive means to revoke consent; and modify the exemption from the consent requirement for financial institutions.
Those two tracks pull in opposite directions, and compliance teams should read them together. The Report and Order narrows the breadth of a single opt-out for informational traffic. The Further Notice asks whether consumers should nonetheless be given an explicit route to revoke everything at once.
Section 64.1200(a)(10) of the Commission's rules is the operative provision. As adopted in the 2024 TCPA Consent Order, it requires in relevant part that if a called party uses any reasonable method to revoke consent, that consent is considered definitively revoked and the caller may not send additional robocalls and robotexts. The Commission further clarified that, for those robocalls for which consent is required under the TCPA, once that consent is revoked the caller may no longer make robocalls or send robotexts to a called party absent an exemption to the consent obligation.
The 2024 Order did three things. First, it made clearer that revocation of consent can be made in any reasonable manner. Second, it required that callers honor company-specific do-not-call and consent revocation requests within a reasonable time from the date the request is made, not to exceed 10 business days after receipt. Third, it limited text senders to a one-time text message confirming a consumer's request that no further text messages be sent, and confirmed that any revocation of consent applies only to those robocalls and robotexts for which consent is required under the TCPA.
The legal basis for the 2026 proposed action is sections 1 through 4 and section 227 of the Communications Act.
The standard is conduct-based, not channel-based. Revocation may be made in any reasonable manner that the consumer uses to express a desire not to receive further calls or text messages, and the Commission's enumeration of methods is illustrative rather than exhaustive. Operationally, that means a revocation received on a channel your platform does not monitor is still a revocation.
The 2026 draft Report and Order would change this by allowing callers to designate an exclusive means to revoke consent. Until that item is published and effective, the any-reasonable-manner standard governs.
Every entity placing robocalls or sending robotexts subject to the TCPA is in scope, together with the texting platforms and contact-center systems that execute on their behalf. The draft Report and Order singles out financial institutions, whose exemption from the consent requirement would be modified.
The three Further Notice items with the largest systems impact are the shortened timeframe, two-way texting and affiliate treatment. A reduction from 10 business days toward the 24 hours originally proposed in 2023 removes any tolerance for manual suppression-list updates or batch synchronization between a CRM, a marketing automation platform and an outbound dialer. A two-way texting requirement means short codes and toll-free numbers configured as send-only would need inbound reply handling and automated parsing of opt-out keywords. Greater specificity on affiliates goes to the question of whether consent given to one legal entity reaches a sister company — a question that determines how suppression lists must propagate across a corporate group.
| Item | Systems impact |
|---|---|
| Shortened timeframe | A reduction from 10 business days toward the 24 hours originally proposed in 2023 removes any tolerance for manual suppression-list updates or batch synchronization between a CRM, a marketing automation platform and an outbound dialer |
| Two-way texting | Short codes and toll-free numbers configured as send-only would need inbound reply handling and automated parsing of opt-out keywords |
| Affiliate treatment | Goes to the question of whether consent given to one legal entity reaches a sister company — a question that determines how suppression lists must propagate across a corporate group |
No date applies yet. The 2026 item is in consultation; the Further Notice seeks comment and does not impose obligations. Comment and reply comment deadlines are set out in the header of the Federal Register publication (FR Doc. 2026-21820, 91 FR, 26 October 2026) and should be read directly from that document before diarising.
The draft Report and Order on category-specific revocation and exclusive revocation methods takes effect only on the schedule stated in the published document following Federal Register publication. Practitioner reporting has circulated specific effective and waiver dates for elements of the 2024 Consent Order; those dates are not confirmed in the official Commission documents reviewed here and should be verified against the Federal Register text before being relied on.
Measure your actual revocation processing time, in hours, from receipt to suppression across every channel — reply text, IVR key press, website form, inbound call, email to a published address. If your median is measured in days rather than hours, the 10-business-day backstop is masking an architecture problem that a shortened deadline will expose immediately.
Inventory every outbound number and short code and identify which are send-only. Those are the assets that would need reconfiguration under a two-way texting requirement, and provisioning changes with carriers and aggregators are not same-week work.
Map consent and suppression data flows across affiliated entities. Document, for each campaign, which legal entity obtained consent, on what date, through what mechanism, and which entities currently consume that consent record. If the Commission adopts specificity on affiliates, that map is the evidence base for whatever position you take.
Audit your opt-out confirmation messages against the one-time limit: a single confirmation text that merely confirms the opt-out request, with no marketing content, no promotional language and no further contact.
Finally, decide whether to file. The Further Notice is the only forum in which the cost and feasibility of a sub-10-business-day deadline will be weighed, and the record is built from comments filed in CG Docket No. 02-278.
The comment and reply comment deadlines stated in FR Doc. 2026-21820, and the Federal Register publication of the Report and Order on category-specific revocation and exclusive revocation methods, which sets the clock for its effective date.
Discuss this signal with compliance peers, get the weekly digest, and never miss an enforcement deadline that affects your products.
| Affiliates | Providing greater specificity to affiliates | The treatment of affiliates |