--- title: "What RCS changed, and what it did not" summary: "Apple's adoption in iOS 18 turned a long-stalled standard into something with reach, and 2026 brought new versions and cross-platform encryption. Reach is still not the same as a business case." canonical: https://cpaas.co/en/learn/what-rcs-changed kind: explainer depth: foundation origin: original published: 2026-09-21T16:26:18.899Z updated: 2026-10-14T16:26:19.435Z topics: ["RCS", "Messaging", "Fundamentals"] language: en --- # What RCS changed, and what it did not ## What RCS is **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. ```diagram:compare | SMS | RCS Business Messaging A parcel notice | A line of text and a link | A card with a photo of the item, a "Track parcel" button and a "Change delivery day" reply chip The sender | A bare number | The brand's name, logo and a verification mark What else comes with it | — | Images and video, suggested replies, typing indicators, read receipts Where it appears | The phone's default messaging app | The same app ``` ## What changed **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. ```diagram:timeline # How a stalled standard became a live one September 2024 | Apple adds RCS in iOS 18 | Near-universal handset support on modern phones Early 2026 | Universal Profile 4.0 | In-chat video calling, richer formatting, richer business cards May 2026 | Cross-platform encryption begins | End-to-end encrypted iPhone–Android chats, in beta, on supported carriers July 2026 | Universal Profile 4.1 | Maintenance release refining interoperable encryption > Specified is not the same as deployed, and deployed is not the same as available to business messaging. Three different gates. ``` ## What did not change **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. ## The three gates between a standard and your customer | Gate | The question | What to know | |---|---|---| | Handset | Does the phone support RCS? | Close to universal on modern phones since iOS 18 | | Operator | Has the recipient's operator switched it on? | Varies a lot by country and operator | | Business messaging | Can a business send RBM to that subscriber? | A further commercial and technical gate | 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? ```diagram:decision # One rich message, three gates Does the phone support RCS? | | It arrives as the SMS fallback Has the recipient's operator switched RCS on? | | It arrives as the SMS fallback Can a business send RBM to that subscriber? | The rich version arrives | It arrives as the SMS fallback > Three exits out of four lead to the fallback, which is why the SMS version is design work, not an afterthought. ``` ## How to think about it 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? | Message | Worth upgrading? | |---|---| | Delivery notice with tracking | Often yes — the button changes what people do | | Appointment reminder with "reschedule" | Often yes | | Boarding pass or ticket | Often yes | | One-time passcode | Rarely — SMS is simple, universal and auto-filled by phones | Passcodes are a large share of business SMS volume, which is one reason the shift is gradual. ## The underrated feature: a verified sender 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. ## Planning the transition honestly 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. ```diagram:checklist # What running both channels costs Two versions of each message | And two previews to review Two failure modes | Both monitored A capability check in the send path | Can this number receive RBM right now? Reporting on the mix | How many messages went rich, and how many fell back ``` ## What to ask a provider - 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? ## Where to go next - [RCS in an existing SMS programme](/en/learn/rcs-in-an-existing-sms-programme) — the next step in this track. - [RCS adoption after iOS](/en/learn/rcs-adoption-after-ios) — what the numbers show. - [Channels are not interchangeable](/en/learn/channels-are-not-interchangeable) — how RCS compares with the others. ## Sources [^1]: [RCS Now in iOS: a New Chapter for Mobile Messaging](https://www.gsma.com/newsroom/article/rcs-nowin-ios-a-new-chapter-for-mobile-messaging/) — GSMA [^2]: [From Rich Text to Video: RCS Universal Profile 4.0 has arrived](https://www.gsma.com/newsroom/article/from-rich-text-to-video-rcs-universal-profile-4-0-has-arrived/) — GSMA, 2026 [^3]: [RCS Universal Profile 4.1: Stronger foundations for secure messaging](https://www.gsma.com/newsroom/article/rcs-universal-profile-4-1-stronger-foundations-for-secure-messaging/) — GSMA, July 2026 [^4]: [RCS Encryption: A Leap Towards Secure and Interoperable Messaging](https://www.gsma.com/newsroom/article/rcs-encryption-a-leap-towards-secure-and-interoperable-messaging/) — GSMA [^5]: [End-to-end encrypted RCS messaging begins rolling out for Android and iPhone users](https://blog.google/products-and-platforms/platforms/android/android-ios-end-to-end-encrypted-rcs-messaging) — Google, May 2026 --- Published by the company behind five products in this category. Those products appear in this site's directory alongside competitors under the same published criteria and are labelled as its own. Editorial content does not recommend them.