RCS messaging
Send a branded card with an image, a headline and buttons where RCS is available, and fall back to plain SMS everywhere else. One payload, one receipt, no branching in your code.
- automatic
- Fallback
- 6
- Card types
- included
- Verified sender
Rich cards where the handset supports them
- Automatic capability check per handset, with SMS fallback in the same request
- Rich cards, carousels and suggested replies, all defined in the template
- Verified sender registration with the brand name and logo shown in the thread
- Read receipts and typing indicators where the network exposes them
- Per-market availability reporting, so you know what share of a list can receive rich
- Identical delivery states across both channels, so reporting stays one pipeline
Build order
- 1Register the brandSubmit the brand name, logo and colour once. We handle the carrier side.
- 2Build the templateDefine the card and the plain-text fallback together in one template.
- 3Send as normalPost to the same endpoint with channel set to auto. Capability is resolved for you.
- 4Read the splitReporting shows what was delivered rich and what fell back, per market.
Put rcs messaging to work
Sandbox keys cost nothing and mirror the live gateway, rejections included, so your ops team can watch a message land on a handset before anything is signed.