What RCS changed, and what it did not

RCS — Rich Communication Services — is the mobile industry's successor to SMS. It is defined by the GSMA (the global association of mobile operators) in a shared specification called the Universal Profile, and it works inside the phone's default messaging app — Google Messages on most Android phones, Messages on iPhone.

Compared with SMS it adds images and video, buttons, suggested replies, typing indicators and read receipts. For businesses, RCS Business Messaging (RBM) adds a verified sender: the brand's name, logo and a verification mark instead of a bare number.

Example: a parcel notice by SMS is a line of text and a link. By RCS it can be a card with a photo of the item, a "Track parcel" button and a "Change delivery day" reply chip, from a sender labelled with the retailer's verified name.

RCS spent roughly a decade as the technology that was about to matter.

Apple added RCS in iOS 18 (September 2024). That moved the standard from "Android only, so ignorable in many markets" to near-universal support on modern phones.

The standard kept moving in 2026. The GSMA announced Universal Profile 4.0 in early 2026, adding video calls started from a chat, richer text formatting and business features such as streaming video in rich cards. Universal Profile 4.1 followed in July 2026, a maintenance-focused release that refined interoperable end-to-end encryption.

Encryption across platforms began. In May 2026, Apple and Google began rolling out end-to-end encrypted RCS between iPhone and Android in beta, for person-to-person chats on supported carriers.

It still runs through operators. Reach depends on mobile operators launching RCS and RBM, not just on handset support. In a market without RBM, your rich message arrives as a fallback SMS.

It is still business messaging. Registration, brand verification and content rules apply. Rich formatting does not make a promotion anything other than a promotion.

The fallback is mandatory design work. Every RCS programme is really two: the rich version and the SMS version it falls back to. If the fallback is an afterthought, part of your audience receives the afterthought.

A provider quoting "RCS reach" without saying which gate it means is quoting the largest number available. Ask for the third gate, for your countries. New features (such as Universal Profile 4.0 video calling) add a fourth question: has the user's app actually shipped them?

The honest framing: RCS is a presentation upgrade on an existing channel, not a new channel. It uses the same address (a phone number), much of the same regulation and many of the same commercial relationships as SMS.

That makes the business case easier to judge: is a richer version of a message you already send worth the extra cost and the two-path complexity?

Passcodes are a large share of business SMS volume, which is one reason the shift is gradual.

SMS has no real sender authentication, which is why it is a favourite channel for phishing by text ("smishing"). RBM shows a verified brand. If your messages are the ones criminals imitate — banks, delivery firms, public services — a channel where impersonation is harder can matter more than any carousel.

Nobody switches to RCS. They add it, run both, and shift the mix over years. Budget for:

• two versions of each message, and two previews to review;
• two failure modes to monitor;
• a capability check in the send path (can this number receive RBM right now?);
• clear reporting on how many messages went rich and how many fell back.

• What is your RBM reach, by operator, in each of my countries today?
• How do you decide when to fall back to SMS, and how is the fallback billed?
• Who handles brand verification, and how long does it take in each market?
• Which RCS features (read receipts, rich cards, suggested replies) are available to me in each market?

• RCS in an existing SMS programme — the next step in this track.
• RCS adoption after iOS — what the numbers show.
• Channels are not interchangeable — how RCS compares with the others.