RCS, with SMS behind it.
RCS is planned for Release 3. You will manage brand agents, check which recipients can receive RCS, and fall back to SMS only once non-delivery is confirmed.
What you get
Brand agents
Manage agents, use cases, test devices, launch regions and carrier launch status in one place.
Capability checks
Check whether a recipient can receive RCS before sending, with an explanation when they cannot.
No double sends
Fallback to SMS waits for confirmed non-delivery, unless your policy explicitly accepts the risk of a duplicate.
Agent assets checked before submission
Logo, banner, colours and policy links are checked against the current specification before they go to Google or carriers.
RCS template versions
Add an RCS version to an existing template alongside its WhatsApp and SMS versions.
Questions
When will RCS be available?
It is planned for Release 3. We will announce it on the roadmap when it is ready.
What happens if a recipient cannot receive RCS?
The capability check says why, and your routing can send SMS instead.
Will I need my own RCS agent?
Yes. RCS messages come from a verified brand agent launched with carriers for your use case.
Related
- SMSAvailableSend SMS to Indian numbers under your DLT registration, with headers, categories and variables checked before anything goes out.
- RoutingAvailableEvery message tries WhatsApp and falls back to SMS after a confirmed failure or timeout. Override the channel per send.
- RoadmapAvailableThe beta today, then four planned releases: launch, automation and reporting, campaigns and RCS, then email, push and in-app.
Start with the beta.
Hopwire is free during the invite-only beta. Tell us what you send and we will reply by email.