🇪🇸 Español 🇬🇧 English 🇧🇷 Português
Omnifox Omnifox
Sign up

Connect RCS Business Messaging (Sinch/Vonage)

Connect your RCS Business Messaging agent (via Sinch, Vonage, or Infobip) to Omnifox for rich Android messaging.

Jul 11, 2026

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

  1. Register and verify your RBM agent with Google through your aggregator's console (e.g., Sinch → Projects).
  2. Copy the Project ID and Agent ID from that console.
  3. Generate an access token for your service plan (in Sinch: dashboard → Access Keys).
  4. In Omnifox, go to Channels → Connect New Channel, pick RCS Business Messaging, and fill in the Project ID, Agent ID, Access Token, and optionally the Service Plan ID.
  5. 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-signature header.

Example

An Android customer receives an RCS message with a product card and two buttons ("View order" / "Talk to an agent"); tapping one arrives 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.
Was this helpful?

Related articles