TL;DR
The FCC published two different revocation documents on October 26, 2026: a final rule effective November 25, 2026, and a further notice of proposed rulemaking with comments due the same day. They are not interchangeable.
The final rule permits category-specific revocation for informational robocalls and texts, and allows callers to designate certain disclosed, exclusive opt-out methods. It does not let marketers split promotional campaigns into separate opt-out categories. The maximum processing period remains a reasonable time not exceeding ten business days. A shorter deadline, mandatory two-way texting, and additional revoke-all and affiliate provisions remain subjects of the proposal.
For lead buyers, the immediate assignment is to classify communications correctly, document the opt-out method actually disclosed, and test suppression across campaigns before changing production behavior. Publication is not the effective date.
Overview: One Publication Day, Two Different Legal Tracks
The primary sources are the FCC’s final rule, “Enhancing the Ability of Consumers To Control the Robocalls”, and its proposed rule, “Modernizing the Ability of Consumers To Control Robocalls”. Both concern CG Docket No. 02-278 and FCC 26-67, adopted September 30 and released October 1. This week’s development is their Federal Register publication and the associated dates—not a claim that the Commission voted yesterday.
Keep three dates on the implementation calendar:
- October 26, 2026: Federal Register publication of the final rule and proposal.
- November 25, 2026: Final rule effective date; separately, the deadline for initial comments on the proposal.
- December 28, 2026: Reply-comment deadline for the proposal, not a new compliance deadline.
The final rule’s effective-date section expressly says the amended section 64.1200(a)(10) supersedes the relevant delayed effective date previously extended to January 31, 2027. Teams still working from a January-only implementation plan need to revisit it.
This guide describes the published documents as of October 27. The preparation controls below are operational recommendations, not additional recordkeeping mandates created by the FCC.
Informational Categories Are Not Marketing Campaign Categories
The final rule allows a caller to interpret a revocation responding to an informational call or text as applying to that specific category of informational communications rather than all communications. The amended text defines the relevant informational communication as one that does not contain advertising or telemarketing.
That distinction matters more than the labels in a CRM. A payment reminder and a fraud alert may serve different informational purposes. A promotion for one product and a promotion for another product do not become informational merely because different teams send them.
The amended rule states that revocation responding to advertising or telemarketing calls or texts revokes consent to all future advertising or telemarketing calls or texts from that caller. The final rule’s discussion emphasizes that a consumer need only make one revocation request to stop future telemarketing robocalls from the caller.
For example, suppose a buyer receives a home-improvement lead and sends promotional messages for roofing and windows. Treating a response to the roofing promotion as “roofing only” because the windows campaign has a separate campaign ID would misapply the informational-category flexibility. Campaign architecture does not determine the legal scope of the opt-out.
Before November 25, map actual message content to purpose, identify the caller or entity on whose behalf the communication is made, and review mixed-purpose templates. A message that adds an offer to an otherwise informational notification deserves a fresh classification review. Do not let a database field silently decide that question.
Exclusive Opt-Out Methods Come With Specific Conditions
The final rule permits callers to designate certain methods as the exclusive means of revoking consent:
- An automated, interactive voice or key-press opt-out mechanism on a call.
- A reply to an incoming text using the standardized words listed in the rule.
- A website or telephone number designated to process opt-out requests.
The caller must clearly and conspicuously disclose the designated method on the call or in the text. A preference hidden in an old landing-page footer is not the on-call or in-message disclosure described by this rule.
For text replies, the listed words are stop, quit, end, revoke, opt out, cancel, and unsubscribe. A sender may disclose just one—for example, “Reply STOP”—but must recognize every standardized word as a valid request. The permission to shorten the disclosure is not permission to narrow the parser to one keyword.
Callers that properly designate an exclusive method under the amended rule are not required by that provision to process requests through other methods. Callers that do not designate one must continue processing revocations made by any reasonable means. This is an option with conditions, not an automatic switch for every sender.
The FCC also expressly preserves existing opt-out requirements for exempted calls and calls containing advertising or telemarketing. In particular, the order points to section 64.1200(b)(3)’s automated interactive opt-out requirement for covered artificial or prerecorded voice calls. An exclusive-method policy should not be used to replace a separately required mechanism.
A prudent rollout therefore starts with a template inventory and end-to-end tests. Verify what the consumer receives, not only what the messaging vendor says its platform supports. Keep the prior workflow operating until the effective date and the replacement controls have been reviewed.
Ten Business Days Remains a Ceiling, Not a Waiting Period
The amended final-rule text retains a requirement to honor covered revocations within a reasonable time not exceeding ten business days after receipt. It does not authorize routinely continuing outreach for ten business days when a request can reasonably be implemented sooner.
The separate proposal asks whether that maximum should be reduced. It discusses a joint-letter suggestion involving seven business days and asks whether timing should vary for callers that designate exclusive methods. Those questions do not themselves establish a seven-day rule.
For operations teams, separate three timestamps: receipt of the request, the suppression decision, and enforcement by every relevant sending system. A CRM update alone does not demonstrate that a dialer queue, text campaign, or scheduled retry stopped.
Test delayed jobs and disconnected integrations. If a lead was exported before an opt-out, a later import should not erase the suppression state simply because the source file still says “consent: yes.” The original consent event and a later withdrawal are different events. Preserve both, with the later event affecting eligibility for the relevant outreach.
The broader evidence problem is covered in this lead consent documentation guide: retain the facts needed to explain the decision, not just the final status flag.
What Is Still Proposed—and What Has Not Become Permission
The October 26 proposal seeks comment on several further changes:
- A shorter revocation-processing timeframe. The FCC asks about costs, benefits, and different approaches.
- Two-way texting. It asks whether senders should be required to support reply-text revocation instead of relying on a disclosed alternative for one-way protocols.
- A revoke-all method. It asks whether category-specific informational revocation should be conditioned on an option to revoke consent across all covered message types, including an automated mechanism.
- Affiliates, business lines, and divisions. It asks whether existing standards need more specificity or expansion.
The final rule still permits one-way texting protocols subject to clear disclosures about the technical inability to reply and reasonable alternative revocation methods in each text. The proposal is not a present prohibition on all one-way messaging.
Likewise, the affiliate discussion does not mean affiliated companies are automatically outside every opt-out. The final rule reminds telemarketers of the existing residential do-not-call standard, including affiliated entities a consumer would reasonably expect to be covered. Entity relationships and consumer-facing identification still matter. For the distinct DNC layer, see this outbound-team guide.
There is also a separate, narrow final-rule change for certain financial-institution informational communications: telephone numbers may come from specified reliable sources under that exemption. This is not a general permission to buy marketing numbers and call them without appropriate consent. The amendment preserves other exemption conditions; do not transplant a fraud-alert exception into a lead-generation campaign.
Build a Revocation Record That Survives a Handoff
The useful operational unit is not merely “this phone number opted out.” It is a traceable event tied to the communication and the applicable scope.
As a recommended internal control, record:
- The recipient number, request time, and raw response or request evidence.
- The communication that prompted the request, including its actual content and sender identity.
- The disclosed opt-out method and the version of the template in use.
- The informational or marketing classification and the reason for that classification.
- The suppression scope selected, systems notified, and enforcement timestamps.
- Any exception, failed delivery to an internal system, or manual decision requiring review.
This schema is not prescribed by the new rule. Its value is practical: it lets a compliance reviewer reconstruct what happened without guessing from today’s template or a vendor’s generic policy.
For purchased leads, avoid overwriting the original acquisition record. Keep the initial permission evidence linked to later withdrawal events and contact decisions. A new vendor delivery of the same number should trigger a reconciliation, not silently reset the consumer’s preferences. A claim of fresh permission needs its own evidence and review; the new rule does not establish automatic re-consent when data is resold.
This is also why a lead-buying checklist should address downstream contact controls as well as source evidence. Good acquisition documentation does not make subsequent opt-outs disappear.
November 25 Readiness Checklist
Use the next month to prepare a controlled change rather than treating publication as immediate authorization:
- Replace the outdated January-only milestone with the November 25 effective date for these amendments.
- Keep proposed changes on a separate watchlist with November 25 and December 28 comment deadlines.
- Inventory caller identities, sending systems, templates, and communication purposes.
- Review mixed informational/promotional messages before assigning categories.
- Ensure one marketing opt-out reaches the caller’s other marketing campaigns and channels within the applicable scope.
- If choosing an exclusive method, verify the permitted mechanism and clear disclosure on each relevant call or text.
- Test all seven standardized text keywords, not just the one displayed.
- Preserve any independently required opt-out mechanism and other applicable obligations.
- Measure request-to-enforcement time across queues and integrations; do not treat ten business days as a default delay.
- Test repeat lead imports, retries, disconnected systems, and suppression recovery.
- Have the policy owner approve the effective-date transition and retain the test results.
Key Takeaways
The October publication creates a concrete implementation date, but it does not collapse every revocation issue into one new rule. November 25 is the final rule’s effective date and, separately, a proposal’s comment deadline.
Informational-category flexibility is not marketing-campaign flexibility. Exclusive opt-out methods require the specified mechanisms and clear disclosures. Ten business days remains the outer limit in the published final text, while shorter timing and further structural changes remain under consideration.
Start with one real customer journey: inspect the message, submit an opt-out, and trace it through every relevant sending system. That exercise will expose more implementation gaps than a policy document that never leaves the compliance folder.