--- title: "RCS after iOS: what changed in the numbers, and what to distrust" summary: "Adoption figures for RCS are widely quoted and rarely defined. What can be said confidently, and what is being counted loosely." canonical: https://cpaas.co/en/learn/rcs-adoption-after-ios kind: research depth: advanced origin: original published: 2026-07-05T16:26:18.899Z updated: 2026-10-14T16:26:19.604Z topics: ["RCS", "Market", "Messaging"] language: en --- # RCS after iOS: what changed in the numbers, and what to distrust ## Why this matters RCS (Rich Communication Services) is the operator-run upgrade to SMS: branded senders, images, buttons and read receipts inside the phone's default messaging app. Since Apple added it to the iPhone, vendors have quoted ever larger adoption numbers. If you are deciding whether to invest in RCS, you need to know which numbers describe *your* potential reach and which describe something else. This piece separates what is firmly established from what is loosely counted, and gives a simple way to estimate reach for your own markets. For the basics, start with [what RCS changed](/en/learn/what-rcs-changed). ## What is firmly established **Apple added RCS support in iOS 18**, released in September 2024. This is a matter of record, not an estimate. **The GSMA keeps extending the standard.** Universal Profile 4.0, published in March 2026, added video calls started from inside a message thread, richer text formatting, and business features such as video inside rich cards and control over how links open. Universal Profile 4.1, published in July 2026, focused on making end-to-end encryption work reliably between different apps, building on encryption work the GSMA had already published. Together these are the substance: the standard is supported on both major smartphone platforms, and it is still being actively extended. But a specification is not a deployment. New profile features reach people only when messaging apps, phone makers and operators implement them, which typically takes months or years after publication. ```diagram:timeline # On the record September 2024 | iOS 18 | Apple adds RCS support March 2026 | Universal Profile 4.0 | In-thread video calls, richer formatting, video in rich cards, control over how links open July 2026 | Universal Profile 4.1 | End-to-end encryption that works reliably between different apps > A specification is not a deployment: features reach people months or years later. ``` ## What is quoted loosely Almost every adoption statistic you will meet. Widely repeated figures put the active RCS user base in the billions and describe large multiples in traffic growth since Apple's move. They may be directionally right. They are also, in most cases, sourced to vendor blog posts that do not define what they are counting. The exceptions worth knowing are Google's own dated figures: more than one billion monthly active users with RCS in Google Messages, reported by March 2024, and more than one billion RCS messages a day in the United States, reported in May 2025. Both count people's messages, not business traffic. Three questions to ask of any RCS number: **Users or devices?** A device that supports RCS is not a person who receives RCS business messages, because operator deployment is a separate condition. **Capable or reachable?** Handset support, operator deployment and business-messaging availability are three different gates. A figure counting the first can be several times larger than one counting the third. **Consumer or business traffic?** Person-to-person RCS and RCS Business Messaging are different volumes with different economics. Mixing them inflates the number that matters to a business buyer. | The claim | What it counts | What it does not | |---|---|---| | "RCS reaches N billion users" | Handsets with a compatible messaging app | Whether the operator has enabled it, and for business messages | | "iOS supports RCS" | The capability shipped in iOS 18 | Which carriers enabled it, and for which message types | | "RCS engagement beats SMS by X" | Two different audiences | That RCS recipients may own newer phones in richer markets | | "Universal Profile 4.0 adds video" | What the specification defines | Whether any app your customers use has shipped it | None of these is false. Each answers a question next to the one a buyer is asking. ## The chain a message has to survive Reach is not one number. It is the product of several, and a buyer's actual reach is decided by the weakest link rather than the headline. ```diagram:flow # What must be true for one RCS message to arrive as RCS The handset supports it | Since iOS 18 and on modern Android, mostly yes. This is the number that gets quoted. The operator deployed it | Varies by market and by operator. This is where reach is actually decided. The sender is verified | Brand verification per market, with its own timeline and its own rejections. The feature set matches | Differences in app and profile versions mean a rich element may degrade or drop. It arrives as RCS | And if any link failed, your SMS fallback runs, which is why it must be a designed path. > The gates multiply rather than average. In an illustrative market with 95% capable handsets and 40% operator coverage, reach is about 38%, not 95%. ``` ```diagram:bars # The illustrative market from the caption above Capable handsets | 95% | The number that gets quoted Operator coverage | 40% | Where reach is actually decided Reach | 38% | 95% of 40%: the gates multiply ``` ## What a buyer should conclude **Reach is a market-by-market question, not a platform question.** The honest way to size it is to ask your provider for RCS Business Messaging reach in the specific countries and operators you send to. A global percentage averages markets you do not serve. A provider that cannot give per-market figures is quoting a press release. **Design the fallback as a first-class path.** Whatever the true reach is, it is not 100%, and the share that receives SMS is not a rounding error. If removing the RCS branch would leave you without a working programme, the architecture is upside down. **Do not compare RCS recipients with SMS recipients.** They are different populations. A randomised split within the RCS-capable group is the only comparison that measures the format rather than the audience. **Budget time for verification.** Brand verification is per market, can take weeks, and is a prerequisite, not a launch task. It is the same lesson as US 10DLC registration in different clothes; see [sender registration around the world](/en/learn/sender-registration-around-the-world). ```diagram:checklist # Before investing in RCS RCS Business Messaging reach per country and operator | Not a global percentage The SMS fallback designed as a first-class path | The share that gets SMS is not a rounding error A randomised split within the RCS-capable group | The only comparison that measures the format Time budgeted for brand verification | Per market, weeks, and a prerequisite ``` ## The methodological point This is the same pattern as the market-size disagreement: a widely quoted number, a stable underlying trend, and definitions loose enough that the number can be almost anything. The trend is real and worth acting on. The specific figure in the deck in front of you is probably not worth defending. ## What to take away Handset support is largely solved and is no longer the main constraint. Operator deployment and sender verification are, both are per market, and reach is their product. Design the SMS path as the real one, verify per market on a realistic timeline, and treat any engagement comparison without a control group as a description of who owns a newer phone. ## Where to go next - [RCS in an existing SMS programme](/en/learn/rcs-in-an-existing-sms-programme): how to add RCS without breaking what works. - [GSMA on RCS, encryption and the future of operator messaging](/en/learn/the-mobile-economy-a2p): the primary sources, read carefully. ## Sources [^1]: [New features to celebrate Messages' 1 billion RCS users](https://blog.google/products-and-platforms/platforms/android/7-new-messages-features/) — Google, accessed 2026-10 [^2]: [A billion RCS messages are sent every day in the U.S.](https://blog.google/products/android/billion-rcs-messages/) — Google, May 2025 [^3]: [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 [^4]: [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, March 2026 [^5]: [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 [^6]: [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 --- 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.