RCS, SMS, and What's Actually Changing in Business Messaging

Every few years a new messaging channel gets announced as the thing that finally kills SMS. RCS is the latest, and this time the excitement has a real basis: verified sender branding, rich cards with images and buttons, typing indicators, and read receipts, all inside the same thread your customer already uses for texts. The useful question isn’t whether RCS is better than SMS. It obviously is. The question is what it changes about how you should build — and the honest answer is: less than the headlines suggest.

This is a channel-strategy piece, not a spec sheet. If you run a front line — booking appointments, recovering missed leads, answering the same forty questions — you don’t need to become an expert in messaging protocols. You need to know what RCS actually delivers, where it still falls back to plain SMS, and how to avoid building something you’ll have to tear out in eighteen months. That’s the whole argument here: treat RCS as a richer way to render a conversation you already run, not as a new channel you rebuild for.

What RCS actually adds

Strip away the branding and RCS does four things SMS can’t. Each one is genuinely useful, and none of them changes the fundamental shape of a conversation.

• Verified sender identity.Your business name, logo, and a verification checkmark appear at the top of the thread instead of a random ten-digit number. This is the single biggest win: it attacks the “is this spam or my plumber?” hesitation that suppresses response rates on unknown numbers.
• Rich cards and suggested actions.Images, carousels, and tap-able buttons — “Confirm 2 p.m.,” “Reschedule,” “Get directions” — render inline instead of as a wall of text and a link. Fewer taps, fewer misreads.
• Delivery and read receipts. You can see that a message was delivered and opened, which turns follow-up from guesswork into something you can actually trigger on.
• Typing indicators. A small thing that makes an automated exchange feel like a live one, especially when an agent is composing a real response rather than firing a canned reply.

What hasn’t changed (and won’t soon)

Here is the part vendors gloss over. RCS is not universally deliverable, and won’t be for a while. Support depends on the recipient’s device, their operating system, their carrier, and whether they’ve got a data connection at that moment. Apple only began supporting RCS on the iPhone in late 2024, and rollout across regions and carriers is still uneven. In practice that means every serious deployment needs an SMS fallback — and will for years.

RCS doesn’t replace SMS. It sits on top of it. SMS is still the floor, and the floor is where a real share of your messages will land.

That’s not a reason to ignore RCS — it’s a reason to be honest about the architecture. If a message can’t be delivered as RCS, it has to gracefully downgrade to SMS without the customer noticing and without your team maintaining two separate conversation flows. A rich card with three buttons has to become a clean line of text and a link. That downgrade logic is the actual engineering problem, and it’s the thing most “we added RCS” announcements quietly skip.

Why SMS still earns its keep

It’s worth remembering why texting became the workhorse channel in the first place. People read their texts, fast, and they reply. SMS marketing platforms consistently report open rates well above 90% and response behavior an order of magnitude better than email — figures Attentive and its peers publish (vendor-published, so treat the exact numbers as directional). Even discounting for vendor optimism, the gap between “a text” and “an email” is real and large. RCS inherits that behavior — it lives in the same inbox — which is exactly why it’s worth caring about. It makes an already high-intent channel clearer and richer. It doesn’t invent a new one.

When it’s worth building for

So when do you actually invest? The honest timing guidance is less exciting than “now, before your competitors.”

• Turn on verified branding as soon as you can. This is the low-risk, high-return move. The trust bump from a verified sender costs you nothing in conversation design and helps on every message that renders as RCS.
• Use rich cards where taps matter. Confirmations, rescheduling, appointment reminders, order status — anywhere a button beats a sentence. Skip them for open-ended conversations, where they add little.
• Do not rebuild your flows around RCS-only features. Any experience that breaks when it downgrades to SMS is a liability, because a real share of your audience will hit that downgrade today.

In other words: adopt the presentation upgrades that degrade gracefully, and refuse to make anything depend on RCS being present. That’s the posture that ages well no matter how fast — or slow — adoption climbs.

The mistake to avoid during the transition

The costly error isn’t adopting RCS too early or too late. It’s letting your RCS experience and your SMS experience become two different products maintained by two different people. That’s how you end up with a rich card that offers “Reschedule” and “Confirm” buttons, while the customer who fell back to SMS gets a truncated message with a broken link — same business, two personalities, and a support ticket to show for it.

The way out is to design the conversationonce and let the channel decide how to render it. A confirmation is a confirmation: the logic that knows the appointment, checks the calendar, and understands “can we move it to Thursday?” is identical whether the customer taps a button or types a reply. Only the surface changes. When you build that way, RCS support becomes a setting you enable, not a project you staff — and the day adoption jumps in your market, you’re already there with nothing to migrate.

This is also why RCS doesn’t deserve its own strategy meeting. It’s a rendering layer on the channel you already run, and it slots neatly under the broader shift toward agentic customer experience: the front line becomes a system you design once and tune, rather than a set of channel-specific flows you rebuild every time the platforms move.