Connect RCS Business Messaging (Sinch/Vonage) (coming soon)
Coming soon: connect your RCS Business Messaging agent (via Sinch, Vonage, or Infobip) to Omnifox for rich Android messaging.
Coming soon. The RCS Business Messaging channel is built but can't be connected in Omnifox yet; in Settings → Channels → Connect New Channel its card shows as "Coming soon". This article describes how it will work. In the meantime, you can reach your Android customers by SMS (with your own Twilio account) or WhatsApp. See Channel catalog: what Available, Beta, and Coming soon mean.
RCS Business Messaging is Android's successor to SMS: it supports buttons, carousels, and read receipts right inside the native Messages app. Since Google doesn't onboard businesses directly, you need an aggregator (Omnifox defaults to Sinch, but Vonage and Infobip work the same way) to verify your RBM agent.
Requirements
- An RBM (Rich Business Messaging) agent verified by Google through your aggregator
- That agent's Project ID and Agent ID
- An OAuth access token issued by the aggregator
Steps to connect (once available)
- Register and verify your RBM agent with Google through your aggregator's console (e.g., Sinch → Projects).
- Copy the Project ID and Agent ID from that console.
- Generate an access token for your service plan (in Sinch: dashboard → Access Keys).
- In Omnifox, go to Settings → Channels → Connect New Channel, pick RCS Business Messaging, and fill in the Project ID, Agent ID, Access Token, and optionally the Service Plan ID.
- Save, then paste the webhook URL Omnifox shows you into your aggregator's dashboard.
Configuration
- Project ID / Agent ID: identify your verified RBM agent.
- Access Token: OAuth bearer token used to authenticate sends.
- Service Plan ID: informational only — the send API doesn't require it on every call.
- Webhook URL: Sinch signs each request with HMAC-SHA256 in the
x-sinch-signatureheader.
Example
An Android customer receives an RCS message with a product card and two buttons ("View order" / "Talk to an agent"); tapping one will arrive in the Omnifox Inbox as a reply on that conversation.
Tips
- RCS only works on Android devices with Google Messages enabled; on iPhone the message typically falls back to SMS depending on your aggregator.
- Google's agent verification process can take several days — kick it off early.
Troubleshooting
- Sends fail with an auth error: the access token may have expired — regenerate it from the aggregator.
- No events arriving: confirm the webhook URL in your aggregator's dashboard exactly matches the one Omnifox generated.
Related articles
-
WhatsApp (Meta) error codes: what they mean and what to do
A table of the most common Meta error codes when sending on WhatsApp (131026, 131047, 131049, 130497, 141006, 131031, 131056, 132000, 190, 368…) and how to fix each one.
-
How to connect Telegram
Connect a Telegram bot to your Omnifox inbox in minutes using BotFather.
-
Instagram and Facebook comments: reply and moderate from Omnifox
See and answer comments on your Facebook and Instagram posts and ads, publicly or privately, and set up automatic replies.
-
Sending and receiving videos on each channel: formats and size limits
Which videos you can send and receive on WhatsApp, Instagram, Messenger, Telegram, web chat and email, the real size limits, and what to do with a large video.
-
Move from WhatsApp QR to Coexistence or Cloud API
Once you're done testing with the QR code, move your number to the official connection: no caps, with templates and broadcasts, and no volume-based ban risk.