Rich Communication Services is the GSMA's successor to SMS — an operator-standardised messaging protocol supporting rich media, read receipts, typing indicators, verified sender identity and interactive business messaging. Its Universal Profile is the interoperability specification operators and device makers implement.
RCS
RCS is the carrier industry’s attempt to keep messaging rather than cede it entirely to over-the-top applications, and it reaches developers almost exclusively through aggregators.
- Universal Profile - The GSMA specification that makes RCS interoperable across operators and devices.
- Business messaging - Verified sender identity and interactive cards are the commercial case, aimed squarely at the branded-messaging market.
- Distributed by CPaaS - Seven of the aggregators scored in The State of Telecom APIs ship an RCS channel; it sits alongside WhatsApp, Viber and LINE as one commoditised channel among several.
- A carrier asset in someone else’s product - RCS is an operator standard whose developer surface is almost entirely owned by the resellers.
RCS is the sector’s pattern in miniature: an operator-specified capability, standardised properly, that most developers will only ever meet as a line item in an aggregator’s channel list.
Referenced in API Evangelist papers
This standard shows up in my published research. These reports read the machine-readable evidence provider by provider — and put this standard in the context of a real sector.
The State of Telecom APIs
An operator-specified messaging standard whose developer surface is owned almost entirely by the seven aggregators that ship it as one channel among several.