After SMS: what RCS changes, and what it doesn't

There is also a practical reason to look at it now rather than later. Verification and template work take lead time, and businesses that wait until the channel is unavoidable discover that the preparation, not the technology, is what stands between them and using it. Rich communication services have been discussed for long enough that scepticism is reasonable. What has changed is that support is now broad enough for businesses to plan around it rather than pilot it. It is worth being precise about what it changes, because the enthusiasm around it tends to blur the line between a genuinely different capability and the same message in nicer packaging.

What genuinely differs

The clearest difference is verified sender identity. A business message can carry a name, a logo and a verified mark, displayed by the messaging application itself rather than as text the sender chose. For anyone whose customers have been trained to distrust unexpected messages — which is now everyone — that matters more than any formatting improvement. The second difference is that the message becomes interactive: buttons, carousels, replies handled in the thread. A delivery notification can offer to reschedule without sending the customer to a browser. The third is that the sender learns whether the message was read and what the recipient did with it, which is closer to what businesses expect from a messaging channel than a delivery receipt has ever been.

What does not change

The channel does not remove the need for SMS. Not every handset and not every network supports the richer format, so any serious deployment has a fallback path, which means maintaining both and deciding which is used when. Nor does it change the rules about consent: a message a customer did not ask for is unwelcome regardless of how well it renders, and a richer format makes an unwanted message more intrusive rather than less. Registration and verification of the sender remain necessary, and take time. And it does not make delivery free of the routing questions that shape SMS today.

• →Fallback to SMS is part of the design, not an afterthought — the same message content has to work in both forms.
• →Sender verification takes lead time, so it belongs in the schedule before the launch date is fixed.
• →Consent and frequency rules apply unchanged; a richer channel raises expectations rather than lowering them.
• →Interactive messages need someone to handle what the customer sends back, which is an operational commitment.

A reasonable way to approach it

The businesses that get value from the richer channel start with a use case where interactivity genuinely helps — a delivery that may need rescheduling, an appointment that may need changing — rather than converting their entire message catalogue. They keep the SMS version working, because it will carry a meaningful share of the traffic for some time. And they treat verified identity as the primary benefit, because that is what customers notice first and trust fastest.

It is also a channel that rewards restraint. Because messages can carry images, buttons and carousels, the temptation is to use all of it, and a business message that behaves like a web page tends to be read as advertising even when it is not. The deployments customers respond well to look, at a glance, like a message from a company they recognise, with one obvious thing to do next. If you are weighing this for a specific flow, the useful question is not whether the channel is ready. It is whether that particular message becomes materially better when the customer can act on it without leaving the thread.