Sentikko Docs
Connect

Google RCS Business Messaging

Connect your business to Android users via Google's RCS for Business (the successor to Google Business Messages)

Google RCS for Business (RBM)

[!WARNING] Google Business Messages (GBM) was shut down on July 31, 2024. It no longer works. The official replacement is RCS for Business (RBM). This guide covers the current, working integration.

Connect your brand to Android users with rich, verified, interactive messages — directly in Google's Messages app.

What is RCS for Business?

RCS (Rich Communication Services) is the next-generation SMS standard. RCS for Business lets your brand:

  • Send branded, verified messages with your logo in the conversation header
  • Send rich cards, carousels, images, and video
  • Add quick reply buttons and action buttons (URL, call, location)
  • Reach customers on Android and iOS (iOS support via carrier RCS)
  • Get delivery and read receipts
  • Fall back to SMS automatically if the user's device doesn't support RCS

Unlike GBM, RBM is outbound-first — your business initiates conversations (users cannot start a chat with you).


Prerequisites

Before connecting in Sentikko, your team must complete these steps with Google:

  1. Apply to become an RCS for Business partner

    • Fill out the Partner Interest Form on Google's developer site.
    • Google reviews and approves your application. This can take a few business days.
  2. Create a Google Cloud Project

    • Enable the RCS Business Messaging API in the Google Cloud Console.
    • Create a Service Account and download the JSON key — this is what Sentikko uses to authenticate.
  3. Create an Agent in the Developer Console

    • Go to the Business Communications Developer Console.
    • Create a Brand → then create an Agent under that brand.
    • Fill in your business name, logo, and contact details.
    • Set your webhook URL to: https://your-convex-url.convex.site/webhooks/rbm
  4. Verify your brand and submit the agent for launch review by Google.

[!IMPORTANT] New agents start in test mode — messages only reach your pre-registered test phone numbers. Apply for launch to reach all users.


How Conversations Work

FeatureGBM (OLD — shut down)RBM (Current)
Who starts conversationUser or AgentAgent only
User identifierConversation ID (UUID)Phone number (E.164 format)
Entry pointsGoogle Search, MapsTriggered by your app logic
Auth methodOAuth 2.0 tokensService Account (JWT)
iOS supportAndroid onlyAndroid + iOS (via carrier)
SMS fallbackNoYes (automatic)
Status❌ SHUT DOWN✅ Active

Integration Steps in Sentikko

  1. Go to Settings → Integrations
  2. Click "Google RCS Business Messaging"
  3. Upload your Service Account JSON key (downloaded from Google Cloud)
  4. Enter your Agent ID from the Business Communications Developer Console
  5. Sentikko will verify the connection and display your agent's details
  6. Your agent is now ready to send messages from the Inbox or Campaigns

Sending Messages

Once connected, you can send messages to any Android user by their phone number:

  • Text messages — simple text up to 2,048 characters
  • Rich cards — image/video + title + description + action buttons
  • Carousels — swipeable set of 2–10 rich cards
  • File messages — images, video, PDF
  • Suggested replies — quick reply chips the user taps
  • Action buttons — open URL, dial phone, share location

[!NOTE] You can only message a phone number if the user's device supports RCS. Sentikko automatically checks capability before sending and falls back to SMS if needed.


Campaigns

RBM is ideal for outbound campaigns (notifications, promotions, reminders) because:

  • You can initiate conversations without user consent to start a chat
  • But you must have appropriate opt-in consent for marketing messages (per Google's Acceptable Use Policy)
  • Rich content dramatically increases engagement vs. plain SMS

SaaS / Multi-Tenant Notes (for Sentikko customers)

If you are building on top of Sentikko as a platform operator:

  • Each organization gets its own Agent in the Google Business Communications Console
  • Each agent has its own Service Account credentials, stored encrypted per organization
  • Webhook events are routed to the correct organization by matching the agent ID in each payload
  • You can manage multiple agents from one Sentikko account

Webhook Events Received

Sentikko handles all standard RBM webhook events automatically:

EventWhat Sentikko Does
agentMessageStores incoming user reply in the conversation
deliveryReceiptUpdates outgoing message status to Delivered
readReceiptUpdates outgoing message status to Read
userStatus (typing)Shows typing indicator in the inbox
surveyResponseLogs CSAT response

On this page