This matters for businesses: because RCS is an open carrier standard rather than one company’s app, reaching customers doesn’t depend on them adopting a particular platform, it’s built into the phone.
It is easier to reason about if you separate the four roles, because each one can change independently.
| Role | Who holds it | What they control |
|---|---|---|
| Standard | GSMA | The Universal Profile specification and what compliant RCS must do |
| Backend | Google Jibe, plus some carrier stacks | Registration, capability discovery, routing, delivery |
| Network | AT&T, Verizon, T-Mobile, UScellular | Whether RCS is enabled for their subscribers, and business traffic policy |
| Client | Google Messages, Apple Messages, Samsung Messages | How a message renders on the handset |
Open standard is accurate about the specification and misleading about day-to-day access. Anyone may implement the Universal Profile, but sending business messages at scale means going through the RBM API, and access to that runs through approved partners rather than a self-serve signup, because brand and agent verification has to happen before traffic flows. So the standard is open while the commercial on-ramp is gated, and that gate is the reason a verified sender is trustworthy in the first place. The vetting that makes it slow to get in is the same vetting that makes the checkmark mean something.
For a business, the practical consequence is that no single vendor owns your presence on the channel. Your brand and agent are registered with the ecosystem rather than with your provider, and your phone number remains portable, so switching providers is a migration rather than a rebuild. That is a genuine structural difference from a proprietary messaging app, where the audience and the identity belong to the platform. It is worth confirming with any provider that the agent is registered to your brand rather than held under theirs, since that single detail decides how portable the programme really is.
- Standard owner: GSMA (RCS Universal Profile).
- Dominant backend: Google’s Jibe platform; Google Messages is the primary Android client.
- Apple supports RCS from iOS 18.1 (2024); it does not own the standard.
- Four separable roles: GSMA owns the spec, Google runs most of the backend, carriers control enablement, handset apps control rendering.
- The specification is open, but business sending is gated behind partner access and verification.
- Confirm your RCS agent is registered to your own brand, which is what keeps the programme portable between providers.