📡 The Big Story
Juniper Drops the RCS Number Everyone's Been Waiting For: 485 Billion by 2030
OK, we finally have a real number to argue about. Juniper Research just put out its business RCS forecast and the headline stat is a doozy: 485 billion business RCS messages by 2030, up from 125 billion this year. That's 286% growth in four years, with operators pocketing north of $7 billion in the process. Not a rounding error. Not a "pilot phase." This is the migration actually happening.
Here's why this matters beyond the shiny number. For a decade, RCS has been the "next year" of enterprise messaging. Apple's iOS 18 support flipped the switch, Universal Profile 3.0 gave the ecosystem an actual standard, and now the money is showing up. Banks, retailers, and healthcare are the sectors moving A2P volume off SMS first, according to Telemedia, with the US and India leading the pack. That's not a coincidence. Those are the verticals where verified sender + rich content actually moves the needle on conversion and fraud loss.
But before we throw a parade: $7B in operator revenue by 2030 is not "SMS money." Global A2P SMS is still a $25B+ market today. RCS isn't replacing SMS on a dollar-for-dollar basis. It's carving out the high-value slice while SMS quietly keeps humming along for OTPs and everything else. Anyone telling you SMS is dead is selling something. 🔥
🔥 What's Moving
iOS 27 Adds Threaded Replies to RCS Chats 👀
Per MacRumors, iOS 27 will let iPhone users reply inline to green-bubble messages, and reactions will show up as actual emoji instead of "David liked an image." Small feature, huge signal. Apple is quietly treating RCS as a first-class citizen instead of the digital equivalent of an unwashed cousin. Every one of these paper cuts they close makes RCS more usable, which makes enterprise investment less risky. Keep shipping, Cupertino.
Google Messages Bricks RCS on New Samsungs with Error 3100 💀
And then there's this. Users on the latest Samsung devices are hitting Error 3100 trying to activate RCS in Google Messages. Timing? Immaculate. Enterprises are being told to bet the farm on RCS while the backend can't reliably provision it on flagship Android phones. This is exactly the kind of quiet reliability tax that makes CIOs nervous. If you're a brand routing OTPs, "sometimes it just doesn't work" is not a value proposition.
Pennsylvania's Mini-TCPA Amendments Land October 18 😴
Another state, another mini-TCPA. Starting October 18, PA's telemarketer law explicitly covers texts and ringless voicemails with tighter consent rules. It's not shocking. It's the same script we've seen in Florida, Oklahoma, Washington, and Maryland. But add them up and the compliance surface for anyone running national campaigns is now a patchwork quilt that would make a lawyer cry with joy. If your consent management is still "we have a checkbox somewhere," fix it before Q4.
Wrong-Number Robocall Class Actions Are Heating Up 🤡
Plaintiff firms are actively soliciting consumers who received wrong-number robocalls, dangling that sweet $500 to $1,500 per-violation TCPA payday. Translation: if your list hygiene sucks, someone is building a class action on your back right now. Reassigned numbers, stale CRM data, "we bought this list from a vendor in 2019," all coming home to roost. Scrub your lists. Actually scrub them.
🏆 Winner of the Week: Carrier RCS teams, who finally have a Juniper report to wave at their CFO.
📉 Loser of the Week: Anyone with a new Galaxy trying to send a group chat via Google Messages.
📊 By the Numbers
- 286%: Business RCS message growth from 2026 to 2030 per Juniper. For context, that's faster than A2P SMS grew in its best five-year stretch.
- $7B+: Operator revenue from business RCS by 2030. Sounds huge until you remember carriers were making that from SMS termination fees a decade ago. Same movie, new bubble color.
- $500 to $1,500: Per-violation TCPA damages. Multiply by a class of 50,000 recipients. Now go look at your dialer's DNC scrub logs. I'll wait.
🔮 What We're Watching
October 18, PA mini-TCPA effective date. More important than it sounds. Pennsylvania is a big enough market that national brands can't just geofence it out. Expect a flurry of "how do we comply" panic in late September, and probably the first enforcement action by early 2027.
iOS 27 general release next month. If Apple ships threaded RCS replies and richer reactions cleanly, expect Universal Profile 3.0 adoption to snowball with the carriers still dragging their feet. If it ships buggy, expect Android Twitter to have a field day. Either way, popcorn.
💡 The Hot Take
Here's my controversial opinion for the week: the RCS gold rush is going to produce more disappointed enterprises than success stories over the next 18 months, and it won't be RCS's fault.
The 485 billion number is real. The demand is real. But most brands rushing into RCS are treating it like "SMS with pictures," which is like treating email like "letters, but faster." The channel rewards conversational design, verified branding, and actual customer journeys. Meanwhile, half the enterprises I talk to want to blast the same "FLASH SALE 40% OFF" copy with a carousel slapped on top and call it transformation. That's not going to hit the ROI numbers that justified the migration.
Meanwhile, Error 3100 on new Samsungs, uneven carrier support outside the US and India, and a compliance environment where Pennsylvania just added another layer of consent rules? RCS is going to look like a leaky ship to anyone who didn't invest in the infrastructure to run it properly. The winners in 2027 won't be whoever migrated fastest. They'll be whoever migrated smartest, kept SMS as the reliable backbone, and treated RCS as a premium channel instead of a shiny replacement.
Bet accordingly. See you next week. 📡
