--- title: "GSMA on RCS, encryption and the future of operator messaging" summary: "A guide to the GSMA's own primary material on where operator-run messaging is heading, the standards body's account rather than a vendor's summary of it, and how to read it." canonical: https://cpaas.co/en/learn/the-mobile-economy-a2p kind: research depth: foundation origin: syndicated published: 2026-06-26T16:26:18.899Z updated: 2026-10-14T16:26:19.652Z topics: ["Market", "A2P", "Messaging"] language: en --- # GSMA on RCS, encryption and the future of operator messaging We include this as syndicated rather than original because the substance belongs to the GSMA, the global association of mobile operators. The useful thing we can do is point to it accurately, explain what it covers, and show how to read it, rather than restate it. ## Why this matters Business text messaging (often called A2P, "application-to-person") works because almost everyone has a mobile number. The GSMA's *The Mobile Economy 2026* report counts about 5.8 billion unique mobile subscribers, roughly 70% of the world's population, and estimates that mobile technologies and services generated US$7.6 trillion of economic value in 2025, about 6.4% of global GDP. The same organisation develops RCS, the operator-run upgrade to SMS. If you are deciding how much to invest in operator messaging (SMS and RCS) versus messaging apps, these primary sources are where the facts start. Much of what is written elsewhere is a summary of a summary. ```diagram:share # Unique mobile subscribers, against the world's population Unique mobile subscribers | 70% | About 5.8 billion people — The Mobile Economy 2026 > Business text messaging works because almost everyone has a mobile number. ``` ## Why the primary source matters here A great deal of trade-press coverage of RCS traces back to a handful of GSMA announcements, often via a vendor's summary of them. The restatements accumulate errors, particularly about what has shipped versus what has been specified. The GSMA's own newsroom is where the difference between "the profile defines this" and "operators have deployed this" is stated most precisely. ```diagram:steps # Three claims that get compressed into one Specified | The profile defines it — what a GSMA announcement says Deployed | Operators in a given market have switched it on Available for business messages | A further gate, in your market > When a vendor cites a release as proof a feature is available to you, all three steps are inside one sentence. ``` ## What the material covers | GSMA material | What it says | What it does not tell you | |---|---|---| | *The Mobile Economy 2026* (March 2026) | Subscribers, connections, economic contribution, 5G, AI and operator strategy | How much of that traffic is business messaging, or how apps like WhatsApp are used | | RCS reaching iOS | Apple's adoption in iOS 18 and what it means for the standard's addressable base | Which operators have enabled RCS business messaging for iPhone users in your market | | Universal Profile 4.0 (March 2026) | In-thread video calling, richer formatting, business features such as video in rich cards | When those features will reach the apps your customers use | | Universal Profile 4.1 (July 2026) | Stronger foundations for secure messaging and encryption interoperability | Whether business messages in your market are end-to-end encrypted today | | RCS encryption work | End-to-end encryption framed as a step toward secure, interoperable messaging | Timelines for any particular app or operator | ## How to read it as a buyer The standards body's announcements describe **capability that has been specified**. That is a different claim from availability in a given market, which depends on operator deployment, and different again from business-messaging availability, which is a further gate. When a vendor cites a GSMA release as evidence that a feature is available to you, that is three steps of inference compressed into one sentence. The primary source is where you can see the steps. Operator figures also have a boundary. Traffic that never touches an operator's messaging network (WhatsApp, in-app chat and other "over-the-top" services) is outside them. That traffic is a large part of the picture for many buyers, and its absence is a boundary decision, not an oversight. Read operator figures and app figures from their own sources, and do not add them together: they count different things and the overlap is undefined. ```diagram:flow # Reading any industry-body figure without being misled Find the counting unit | Messages, revenue, subscribers or connections. These move independently and are often conflated. Find who is counted | Operators, aggregators, enterprises. An association naturally counts its members' view of the world. Find the boundary | Whether over-the-top app traffic is inside the number or outside it. This changes the trend, not just the level. Ask what the framing serves | Not cynically. Every industry body has a position, and knowing it makes the data more usable, not less. Take the direction, not the level | A consistent multi-year series from one source beats a precise figure from a new one. > Step five is the discipline. A consistent series is evidence; a single impressive number is a slide. ``` ## Our position We have no relationship with the GSMA and no interest in RCS succeeding or failing. We link to it because it is the authoritative account of a standard that a large share of business messaging may run on, and because secondary coverage is unusually unreliable. ## What to take away Go to the primary source. Note the counting unit, who is counted, and the boundary. Separate "specified" from "deployed" from "available for business messages in my market". Take the multi-year direction rather than the single-year level. And read operator-carried and over-the-top volumes as two separate accounts of the world, because that is what they are. ## Where to go next - [Regional messaging in the Gulf](/en/learn/regional-messaging-in-the-gulf): how one region's rules and habits change the picture. - [RCS after iOS](/en/learn/rcs-adoption-after-ios): estimating RCS reach for your own markets. ## Sources [^1]: [The Mobile Economy 2026](https://www.gsma.com/solutions-and-impact/connectivity-for-good/mobile-economy/) — GSMA, March 2026 [^2]: [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 [^3]: [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 [^4]: [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 [^5]: [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.