RCS: Google RBM and Twilio RCS, rich cards and SMS fallback
The RCS (Rich Communication Services) channel sends rich cards, images and suggestion chips to the Android messaging app. Devices that do not support RCS receive the text equivalent of the same message through the app's SMS channel (ADR-0029 §3).…
The RCS (Rich Communication Services) channel sends rich cards, images and suggestion chips to the Android messaging
app. Devices that do not support RCS receive the text equivalent of the same message through the app's SMS channel
(docs/adr/0029-whatsapp-rcs-iki-yonlu-sms-eposta-isindirma.md §3). The channel requires SMS as a plan feature.
1. Providers
| Provider | Requirements | Notes |
|---|---|---|
google_rbm | RBM agent ID, service account JSON, webhook client_token | Device capability is checked before sending; unsupported devices fall back directly to SMS |
twilio | Account SID, Auth Token, Messaging Service SID with an RCS sender, optional Content SID | Rich content via the Twilio Content API (HX…); fallback happens in Pushizo's SMS channel, not in Twilio |
mock | — | Local development and E2E; a recipient whose number ends in 0006 is treated as not supporting RCS |
PUT /internal/v1/apps/{appId}/channels/rcs
{
"provider": "google_rbm",
"agent_id": "markam_agent",
"service_account": { "project_id": "rbm-proj", "client_email": "rbm@rbm-proj.iam.gserviceaccount.com", "private_key": "-----BEGIN PRIVATE KEY-----…" },
"client_token": "rbm-istemci-belirteci",
"sms_fallback": true
}The service account private key, client token and Twilio auth token are stored with envelope encryption and are not returned in responses. Copy the webhook
URL (/hooks/rcs/{provider}/{token}) from the channel card and enter it in the RBM Partner Console or in the Twilio Messaging Service
"Incoming messages" field. RBM events are verified with X-Goog-Signature, Twilio requests with X-Twilio-Signature.
2. Content
contents: plain text (up to 3072 characters).rcs_card: standalone rich card —title(≤ 200),description(≤ 2000),media_url(https),media_height(SHORT/MEDIUM/TALL),orientation.rcs_suggestions: suggestion chips — reply (reply), link (url), call (dial); text ≤ 25 characters; at most 4 on a card, at most 11 on text.rcs_content_sid+rcs_content_variables: Twilio Content API template (variables support Liquid).rcs_fallback_text: text to send on SMS fallback.
For notifications and campaigns with RCS-only content (card, Content SID), channels: ["rcs"] must be set explicitly in the
target.
3. SMS fallback
sms_fallback is on by default. In the following cases, the delivery is sent through the SMS channel and the delivery record
shows fallback_channel = sms:
- The device does not support RCS (RBM capability check returns 404, or Twilio reports an invalid recipient).
- The RCS send hit a permanent error.
- A delayed delivery failure arrived via webhook after sending (Twilio
failed/undelivered, mockfailed): the delivery is requeued and routed to SMS; thesentcounter is not double-counted.
The SMS text is built, in order of preference, from rcs_fallback_text, the card title + description, or contents, plus the first link suggestion.
There is no fallback to a number that has opted out of SMS with STOP; if the app has no active SMS channel, the delivery
fails with SMS_FALLBACK_UNAVAILABLE. Fallback costs are attributed to the SMS provider.
4. Inbound messages
The person's text reply, suggestion chip selection (content.payload = postback) and any file they send appear in the Inbox as an RCS
conversation; keywords also work on RCS (if rcs has been added to the keyword's channels). RCS replies from the
inbox are sent as text.
5. Reporting
Delivery and read receipts are applied to the delivery through RBM DELIVERED/READ and Twilio status callbacks; sms_fallback
is tracked separately in the message counters.
WhatsApp (Meta Cloud API): setup, templates, session window and inbox
Pushizo sends WhatsApp messages directly through Meta's Cloud API; no BSP or extra hosting is needed (ADR-0029). The channel requires SMS as a plan feature. For development and testing without an external account, the mock…
Telegram and Viber: bot messaging, deep-link subscriptions and the inbox
The Telegram and Viber channels send text, image and button messages through your business bot; replies land in the Inbox (ADR-0086). Both channels work with a bot identity rather than a phone number: you cannot message someone who…