Unless specified otherwise, RCS volumes are billed as a part of the "Connected Channels" SKU. If you use WhatsApp with MoEngage, volumes for the same are also included in this.
If an RCS message was successfully sent but failed to deliver, it will be counted towards your "Connected Channels" volume. The fallback SMS is subject to your contract terms.
Delivery rates for RCS vary considerably depending on which geography you operate in. As of June 2025, reach for India stood at ~50%, SEA at ~40%, MEA at ~20%, and after iOS 18 support for RCS, EU and US at ~60%. You can also check the reach with your RCS service provider.
No, currently the primary RCS as well as the fallback SMS needs to be sent through senders belonging to the same service provider.
Yes, MoEngage supports the collection of click data for suggestions. However, your RCS sender must send this data back to MoEngage for it to be tracked.
RCS supports URLs in Simple Text messages, but not in Rich Cards.
A user's reachability for RCS messages depends on three primary variables:
- Device Support: The user's device needs to inherently support RCS (e.g., some older Android phones and Apple devices in India currently do not).
- Recipient App Settings: The recipient must explicitly enable RCS messages within their messaging application. While some Android phone manufacturers default this setting to 'Yes,' users retain the option to disable it.
- Active Data Connection: Unlike SMS, RCS messages transmit over the data layer; the subscriber must maintain an active data connection at the moment of delivery. Without connectivity, the system cannot reach the user.