RCS in 2030

The honest caveat: timelines in messaging slip, and rollout of each new capability depends on carriers and device makers. But the direction is well-supported by current trajectory, rising adoption, Apple’s entry, E2EE, UP 4.0, and the AI/commerce convergence all point the same way.

For businesses, the implication is to build RCS competence now. Those running real RCS programs today will have a structural advantage as video, richer formatting, and AI agents become mainstream, rather than starting from zero when competitors are already at speed.

It is more useful to name what the projection depends on than to restate it. Four things have to hold. Carrier and device rollout of new Universal Profile versions has to keep taking a year or two rather than stalling, since the gap between a spec being finalized and being usable is where optimism usually dies. Apple has to keep pace on business messaging features rather than only on person-to-person ones, because a feature that works on Android alone is not something a US brand can build a programme on. Pricing has to stay close enough to SMS that rich formats are the default rather than a treat. And the consent and verification regime has to stay strict enough that the channel does not fill with the spam that drove people out of every previous messaging channel.

The last of those is the real risk, and it cuts the other way from how it is usually framed. RCS is valuable because a verified sender in a personal inbox is trusted. That trust is a shared resource, and it degrades if volume outruns relevance across the whole channel rather than just for one brand. The scenario where RCS underdelivers by 2030 is not one where the technology fails, it is one where it succeeds commercially and people start ignoring it, exactly as happened to email.

A slower scenario is easy to describe too. Rich formats stay a premium tier, so most business traffic remains text with a chip list; video and in-conversation calling arrive but see little business use; and RCS ends up as a better SMS rather than a new surface. That outcome still justifies building on it now, which is the useful conclusion: the no-regret moves are the same either way.

Those moves are unglamorous. Get the verified sender and the registrations done, since they take calendar time you cannot compress later. Build the consent and suppression layer once, properly, because it is the thing every future use case depends on. Move transactional messaging over and learn the operational rhythm on traffic that has clear value. None of that is a bet on any particular 2030, and all of it pays now.