Key takeaways
- RCS adds a verified sender identity, images, carousels and buttons to the message app.
- It works only on RCS-capable phones, networks and platforms, and availability differs by country.
- Keep SMS as the fallback so every recipient is reached.
- Measure by channel, and design the RCS and SMS versions together.
What RCS adds
- A verified sender name and logo, so the message is easier to trust
- Images, video and carousels in the message itself
- Buttons and suggested replies for actions such as confirm, reschedule or open a link
- Richer status information than a plain SMS, where the platform supports it
- A conversation that can continue in the same thread
Where the limits are
RCS needs a phone, an operator or platform and a country that support it, and the recipient’s phone must have it switched on. That means that for the same list of numbers some recipients will get RCS and others will not.
Brand and sender verification are also part of the setup, and the steps differ by country and operator.
Plan for SMS fallback
A message that cannot be delivered as RCS should be sent as SMS, so that the person is reached either way. Write the SMS version as a complete message in its own right: it cannot show buttons or images, so it needs a short link or an instruction instead.
Test both versions on real devices in the countries you serve.
Good uses
- Order and delivery updates with a tracking button
- Appointment reminders with confirm and reschedule options
- Promotions with images, for recipients who have opted in
- Customer service conversations that start from a message
How ZafeConnect fits
ZafeConnect provides RCS and iMessage alongside A2P SMS, email, chat apps and a CPaaS platform, and states up to 40% lower cost than traditional SMS when RCS and iMessage are used. Savings depend on your traffic and countries, so ask us what that means for your volumes.