--- 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/insights/rcs-adoption-after-ios kind: research depth: advanced origin: original published: 2026-05-30T11:34:07.986Z updated: 2026-09-08T11:34:08.217Z topics: ["RCS", "Market", "Messaging"] language: en --- # RCS after iOS: what changed in the numbers, and what to distrust ## What is firmly established **Apple added RCS support in iOS 18**, released September 2024. This is a matter of record, not estimate. **The GSMA has continued to develop the standard.** Universal Profile 4.0 was finalised in March 2026, adding video calling initiated from within a message thread and richer text formatting. Universal Profile 4.1 followed with a focus on secure messaging foundations, and encryption work has been published as part of the same programme. Those two facts, together, are the substance: the standard is on essentially every modern handset, and it is still being actively extended rather than maintained. ## What is quoted loosely Almost every adoption statistic you will encounter. Widely repeated figures put the active RCS user base in the billions and describe large multiples in traffic growth following Apple's adoption. These may well be directionally right. They are also, in most cases, sourced to vendor blog posts that do not define what they are counting. Three questions to ask of any RCS number: **Users or devices?** A device that supports RCS is not a user 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 will 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. Conflating them inflates the number that matters to a business buyer. Three numbers get repeated in vendor material about RCS, and each conceals a different assumption. ```diagram:compare The claim | What it counts | What it does not "RCS reaches N billion users" | Handsets with a compatible messaging client | Whether the operator has deployed it for those handsets "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 own newer phones in richer markets > None of these is false. Each answers a question adjacent to the one a buyer is asking. ``` ## What a buyer should conclude **Reach is now 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 markets you send to. Any global percentage is answering a different question than the one you have. **Design the fallback as a first-class path.** Whatever the true reach is, it is not 100%, and the portion that receives SMS is not a rounding error. **Do not compare RCS recipients to 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. ## 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. ## The chain a message has to survive Reach is not one number. It is the product of four, 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 enormously by market. 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 | Universal Profile version differences 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. > Four gates, multiplied not averaged. A 95% handset figure and a 40% operator deployment is 38% reach, not 95%. ``` ## What to take away Handset support is solved and is not the constraint. Operator deployment and sender verification are the constraints, both are per market, and reach is their product. Design the SMS path as the real one, verify per market on a real timeline, and treat any engagement comparison without a holdout as a description of who owns a new phone. ## Sources - [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 - [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 - [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.