A claimant texts "STOP" to your SMS line on day 14 of a completion campaign. Under the old rules, most admin platforms treated that as a full opt-out. SMS, email, voice, everything. Gone. You paid $600 to sign that claimant, and a single keyword just zeroed out the asset.
The FCC voted on September 30 to replace the blanket "revoke all" rule with a channel-specific framework. A consumer who opts out of text messages is opting out of text messages, not phone calls, not emails, not every future communication from your office. The rule narrows the revocation to the specific message type and the specific caller or sender.
This is genuinely good news for plaintiff firms running mass arb completion campaigns. But it creates a new operational problem that most firms are not set up to handle.
What the Rule Actually Says
The FCC's revised framework, which replaces the 2023 "revoke all" approach, says that when a consumer revokes consent, the revocation applies to the type of communication the consumer is responding to and the entity sending it. A "stop" reply to a marketing text revokes consent to marketing texts from that sender. It does not revoke consent to informational calls, transactional emails, or outreach from a different entity acting under a separate consent.
The ABA and other industry groups pushed for this change specifically because the blanket approach was causing operational chaos: a single opt-out keyword was being interpreted as revoking consent across channels, entities, and message categories that the consumer never intended to block.
For mass arb, the distinction matters because claimant outreach is not marketing. It is case administration. A claimant who signed a retainer and is being contacted about their own settlement release is receiving transactional or informational communications, not telemarketing. The channel-specific framework gives you a path to keep that claimant reachable even after they opt out of one channel, as long as your system can distinguish between channels and track revocation at that level.
The Problem: Most Admin Stacks Can't Track This
Here is where it gets uncomfortable. The rule change is only useful if your outreach infrastructure can do three things:
- Track consent and revocation per channel (SMS, email, voice) independently.
- Route outreach to the channels that remain open after a partial revocation.
- Document the distinction between marketing and transactional/informational communications for every touchpoint in the audit trail.
If your claims administrator licenses SMS from one vendor, email from another, and voice from a third, those systems almost certainly do not share a unified consent state. When a claimant opts out of SMS, the SMS vendor marks them as opted out. But does that status propagate to the email platform? To the voice dialer? In most legacy stacks, no. The platforms are siloed. So the firm either over-revokes (killing all channels when only one was revoked) or under-revokes (continuing to text a claimant who said stop, which is a per-violation TCPA problem).
Neither outcome is acceptable. Over-revocation bleeds your completion rate. Under-revocation creates liability. The only fix is a unified consent layer that sits across all channels and updates in real time.
Why This Hits Mass Arb Harder Than Any Other Practice Area
In a typical plaintiff practice, you sign a client, communicate with them about their case, and the relationship is one-to-one. Consent management is a paralegal task.
In mass arb, you are running outreach campaigns to thousands of claimants simultaneously across SMS, email, and voice, often over 90 to 180 days. Every claimant who partially revokes consent is not lost. They are rerouted. But only if your system knows which channels are still open.
Consider a 10,000-claimant matter where 8% of claimants opt out of SMS during the first 30 days. That is 800 claimants. Under the old blanket rule, those 800 were effectively dark. Under the new channel-specific rule, you can still reach them by email and voice, if your stack supports it. On a matter where your release threshold is 80%, those 800 claimants are the difference between hitting threshold and missing it.
At $9.99 per fully signed claimant, 800 additional completions is roughly $8,000 in admin cost. But the settlement value those 800 claimants unlock, when they push you from 72% to 80% and trigger the release, could be seven figures. The admin cost is a rounding error next to the threshold economics.
What This Means for Your Vendor Selection
If you are evaluating claims administrators right now, add this question to your scorecard: does your platform maintain a single consent record per claimant across all outreach channels, and can it honor a partial revocation without killing the other channels?
If the answer involves the phrase "we'll coordinate with our SMS provider," you are looking at a stack that was not built for this. You are looking at a purchasing department that will need to manually reconcile opt-out lists across vendors, which means delays, errors, and either over-revocation or under-revocation on every partial opt-out.
The administrators that own their outreach infrastructure, where SMS, email, voice, and document signing all run on the same platform, can implement channel-specific revocation as a software update. The ones licensing five tools from five vendors need five integration projects, five vendor agreements on data sharing, and a prayer that the consent states stay synchronized.
The Compliance Nuance You Cannot Skip
One important caveat. The FCC's rule narrows revocation scope, but it does not eliminate the obligation to honor the revocation that was made. If a claimant texts "stop," you must stop texting them. Period. The channel-specific framework gives you permission to continue reaching them through other channels, not to ignore the opt-out they already gave you.
And "transactional versus marketing" classification is not a label you slap on after the fact. It needs to be baked into your outreach design from day one. Every message in your completion sequence should be classifiable as case-related, transactional communication, not a marketing solicitation. If your outreach looks like marketing (pushing new matters, cross-selling, or using promotional language), the channel-specific framework may not protect you. Confirm the classification approach with your own compliance counsel before you build the sequences.
The Monday Takeaway
The FCC just gave you a tool to keep more claimants reachable across a 180-day completion window. But the tool only works if your outreach infrastructure can track consent at the channel level, route around partial revocations in real time, and document the distinction between transactional and marketing communications for every single touchpoint.
If your admin stack can do that today, you just got a completion rate lift for free. If it cannot, this rule change is a prompt to fix the plumbing before your next campaign launches.
This is the kind of operational detail that determines whether a matter hits threshold or misses it. If you want to see how GroupSettle handles channel-level consent tracking across its native document signing, SMS, email, and AI voice stack, reach out to Kasia at (813) 737-7025 or visit massarb.groupsettle.com.
Harry Hedaya is the founder of Send It By Text, the native document signing, SMS, and email platform behind GroupSettle's mass arbitration completion stack. Their AI super agent handles over 80% of claimant inquiries on its own, which lifts engagement rates further. He works with plaintiff firms running live mass arb campaigns.
This is the kind of operational detail that determines whether a matter hits threshold or misses it. If you want to see how GroupSettle handles channel-level consent tracking across its native document signing, SMS, email, and AI voice stack, reach out to Kasia at (813) 737-7025 or visit massarb.groupsettle.com.