📡 The Big Story
The FCC's TCPA "Reprieve" Is a Trap, and Half the Industry Just Walked Into It
Look, I get it. When the FCC's Consumer and Governmental Affairs Bureau dropped Order DA 26-12 back in January, every TCPA lawyer with a blog raced to declare victory. "Revoke-all delayed to January 31, 2027!" The trade press ran with it. Compliance teams exhaled. Marketing teams started planning Q3 campaigns like nothing happened.
Here's the problem: the FCC only deferred ONE clause inside 47 C.F.R. § 64.1200(a)(10), specifically the cross-topic revoke-all requirement. The rest of the revocation framework went live April 11, 2026. That means honoring opt-outs through any reasonable method, the expanded definition of revocation language ("stop," "quit," "end," "cancel," "unsubscribe," "remove," and any reasonable variation), and the 10-business-day processing window. All live. All enforceable. All generating class action complaints right now.
The deferral trap is real because it sounds like a reprieve when it's a partial extension on the most aggressive piece of an otherwise fully active rule. If your compliance team is operating on the vibe that "TCPA stuff got pushed to 2027," congrats, you're the plaintiff's bar's favorite kind of defendant. The cross-topic piece (one revocation kills all consent across all your campaigns and brands) is what got delayed. Everything else is your problem today. 🔥
🔥 What's Moving
Apple Finally Fixes the "Liked: [text]" Cringe on RCS 👀
iOS 27 beta 2 brings native emoji reactions, photomoji, and inline threaded replies to cross-platform RCS chats. Translation: when your Android friend hearts your message, you'll actually see a heart, not "Loved 'sounds good.'" Welcome to 2019, Apple.
But here's why it matters for brands: every RCS Business Messaging deck pitched to a CMO in the last 18 months has shown threaded replies and reactions as core to the experience. Until now, that experience broke the second an iPhone entered the chat. iOS 27 closes that gap, which means brands building RBM journeys can finally design for one consistent UX instead of two. This is the kind of boring infrastructure win that quietly makes RCS actually viable for enterprise.
SMS Firewalls Are Eating A2P Economics 🔥
Cytech's breakdown of how MNOs are flipping from passive carriers to active gatekeepers is required reading if you sell A2P. The volume-driven model (cheap rates, aggregator routing, carriers as dumb pipes) is dying. Firewalls are now monetization engines, classifying traffic, blocking grey routes, and charging premiums for verified delivery.
This is bad news if your business model assumed arbitrage on international routes or relied on creative routing. It's great news if you've been doing things the legitimate way and competing against people who weren't. The race to the bottom is officially over. The race to verified, compliant, premium-priced messaging is on.
Twilio Goes After Toll Roads 😴
Twilio published a piece pitching RCS to toll and transit agencies as the answer to those "you owe $4.67 in unpaid tolls click here" scam texts everyone's mom has fallen for. The angle: verified sender, branded logo, can't be spoofed.
It's a reasonable pitch and toll scams are genuinely the #1 SMS fraud vector right now. But selling RCS into government procurement is a five-year sales cycle, and most state DOTs are still on rotary phones, metaphorically. I respect the play. I do not envy the AEs assigned to it.
Reminder: Unregistered 10DLC = Zero Delivery 💀
In case anyone needs to hear it again: AT&T, T-Mobile, and Verizon aren't throttling unregistered A2P. They're blocking it. Have been since February 2025. We still get inbound from Zoom Phone and UCaaS customers every week shocked their texts aren't going through. They've never been going through. You just didn't notice until someone complained.
🏆 Winner of the Week: Legitimate A2P providers, who've been telling customers to register for two years and are now vindicated by both firewall economics and carrier blocking.
📉 Loser of the Week: Every compliance team that read "TCPA delayed" headlines in January and stopped reading at the bolded part.
📊 By the Numbers
- 9 months: How long the FCC pushed the revoke-all clause (April 2026 to January 31, 2027). Also roughly how long you have before this becomes a much bigger problem.
- 0%: Delivery rate for unregistered 10DLC traffic across the Big 3 US carriers since February 2025. Not low. Zero.
- 72 hours: How long it took the entire TCPA trade press to mischaracterize Order DA 26-12 as a broad reprieve. Group dynamics are a hell of a drug.
🔮 What We're Watching
Samsung Messages shutdown in July. Per 9to5Google, Samsung is killing its native Messages app and pushing users to Google Messages. That's tens of millions of Android users consolidating onto a single RCS client with a consistent feature set. For brands designing RBM experiences, the Android side is finally becoming testable as one surface instead of three.
The first revoke-all class action. Somebody's getting sued in Q3 for misreading Order DA 26-12. I don't know who yet. Neither do they. But it's coming.
💡 The Hot Take
The A2P SMS business as we've known it for 15 years is dead, and 2026 is the year the obituary gets printed. Carrier firewalls are repricing traffic. 10DLC blocking killed the grey market in the US. RCS is finally good enough that brands will start migrating their highest-value journeys off SMS entirely. And TCPA is becoming a compliance burden so heavy that the only players who can absorb it are the ones already operating like regulated entities.
Here's the bold part: by the end of 2027, the term "SMS aggregator" is going to sound as dated as "long distance carrier." The winners won't be the cheapest routes. They'll be the platforms that treat messaging as a regulated, verified, multi-channel product where SMS is one rail among many. The race-to-the-bottom guys are done. The ones who built for compliance and quality are about to have a very good two years.
And if your vendor still pitches you on price-per-message as the headline metric? Run.
See you next week.
David
