The Federal Communications Commission has rewritten how consent revocation works under the TCPA, and the coverage reads it as a win for callers. For sales teams it is mostly a relocation. The question stops being whether you honoured an opt-out and becomes whether every single touch told the buyer how to send one.
At its open meeting on 30 September, the FCC voted 3–0 to adopt a Report and Order and a Further Notice of Proposed Rulemaking revising its rules on revoking consent to robocalls and robotexts. The changes replace the so-called revoke-all rule, which had been postponed repeatedly and was due to take effect on 31 January 2027. The new rules take effect 30 days after publication in the Federal Register, which means earlier than the date most compliance teams had in their diaries.
Two changes matter.
The first concerns scope. Under the draft circulated on 9 September, a caller may treat a revocation as applying only to the category of informational calls or texts it was made in response to. Telemarketing is treated differently: revoking consent to one telemarketing message still revokes it for all future telemarketing calls and texts from that caller.
The second concerns the channel. A caller may now designate one exclusive method for revoking consent, chosen from three: an automated key-press or voice opt-out on the call, a reply text using one of seven standard words (stop, quit, end, revoke, opt out, cancel, unsubscribe), or a website or phone number set up for the purpose. If it does, it need not process revocations that arrive any other way. The condition is that the caller must "clearly and conspicuously disclose the designated method to revoke consent on the call or in the text."
The ten-business-day window for honouring a revocation is unchanged. Chairman Brendan Carr said the old approach "did not align with consumer expectations".
Read the carve-out carefully
The category carve-out has been reported as a relief for businesses. For a sales organisation, it largely isn't. Prospecting calls and texts are telemarketing, and telemarketing is precisely what the carve-out leaves out. A prospect who replies STOP to one sequence has still opted out of everything that sequence was selling.
Where the carve-out does bite is at the edges of the revenue team, in customer success, onboarding, billing and renewals, where messages are often informational. That raises a classification question most teams have never had to answer formally. A renewal reminder is informational. A renewal reminder that mentions an upgrade may not be. Under the new rules, the difference decides whether an opt-out covers one programme or all of them.
Exclusivity is earned per message
The more consequential change is the exclusive opt-out method, and its value to sellers is real. A designated method protects against what the industry calls opt-out evader litigation: recipients who send unusual phrasings that automated systems fail to recognise, then sue when messages continue.
But the protection holds only for messages that carry the disclosure. The obligation is per call and per text, which means it lives wherever messages are written and generated. In a modern revenue stack that is a long list: sequence templates in the engagement platform, SMS steps built by individual reps, voicemail drops, dialler prompts, and the scripts and prompts behind AI voice agents. One template without the disclosure line, or one agent that improvises its sign-off, and that message falls back to the old position, where a revocation by any reasonable means counts.
The rule rewards consistency. A revenue team whose messages are written in twenty places will find that hard to prove.
Where B2B teams are actually exposed
The TCPA's consent rules turn on the technology used and the type of number reached, not on whether the buyer is a business. Direct dials for many B2B buyers are mobile numbers. Exposure concentrates in a few places.
Where the disclosure has to live
Touch | Who usually builds it | Typical gap |
|---|---|---|
Automated SMS steps in sequences | RevOps, sometimes individual reps | Rep-edited templates drop the opt-out line to save characters |
AI voice agents | Sales systems, vendor configuration | Generated sign-offs vary; disclosure is not guaranteed on every call |
Prerecorded and ringless voicemail | SDR teams via dialler tools | Treated as voicemail, not as a call that needs disclosure |
Dialler IVR and key-press | Telephony or contact-centre team | Key-press opt-out exists but is not announced |
Free-text replies | Nobody in particular | "Please take me off your list" is caught by no keyword filter |
Multiple brands on one dialler | Shared services after acquisitions | Suppression held per brand, not per caller |
Editorial assessment, not survey data. The FCC has previously ruled that AI-generated voices count as artificial voices and that ringless voicemail is a call for TCPA purposes, which is why both appear here.
The last row points to the most interesting question in the further notice. The FCC is asking how a revocation should apply across affiliates and business lines. For private-equity roll-ups that run several brands through one engagement platform, and for groups that cross-sell between divisions, the answer will decide whether a STOP to one brand stops them all. The notice also asks whether to shorten the ten-day window, require two-way texting and mandate a one-step revoke-all option. None of that is settled.
What revenue leaders should take from this
The pre-existing obligation has not gone away: an opt-out received through the designated channel still has to be honoured, across every tool that can reach the buyer, within ten business days. In a stack where the dialler, the engagement platform, the SMS provider and the CRM each hold their own suppression list, that synchronisation is usually the weak point, and it is a RevOps problem rather than a legal one.
Before the rules take effect
Inventory every place an outbound call or text is generated, including AI voice tools and rep-built templates.
Choose the designated method that matches each channel (reply keywords for SMS, key-press for voice) and lock the disclosure into templates reps cannot edit.
Test AI voice agents for the disclosure on every call, not on a sample.
Agree with counsel which customer messages are informational and which are telemarketing, and tag them that way in the systems that send them.
Prove suppression syncs across every tool inside ten business days, and keep the logs.
Nothing here is new work in kind. It is old work, made visible. The FCC has given callers a defence, and the evidence for that defence is the template library.
Sources. Provisions from the FCC draft fact sheet of 9 September 2026 (CG Docket 02-278); vote, commissioner remarks and effective-date mechanics from the E-Commerce Innovation Alliance, 1 October 2026, and law-firm summaries (Troutman, Greenberg Traurig). The adopted text had not been published at the time of writing and may differ from the draft; check the Federal Register version. SalesHubMedia is independent journalism, not legal or procurement advice. Corrections are made openly on this page.
