Skip to content
SPECIFICTION
Get listed

Google RCS for Business

developers.google.com

WebiOSAndroidAPI
Visit developers.google.com
Spec score 7.5 #14 of 34 in RCS Messaging Platforms

What it is

Google RCS for Business lets brands send rich-media messages to customers on Android and iOS, including read receipts, analytics, and a Verified icon. Agents can send one-way notifications or support two-way conversations about transactions, customer service, promotions, and other business needs. Rich cards, media, and suggested interactions can guide users through conversations. Agents send messages through an API using HTTP requests with JSON payloads; configured webhooks deliver user messages and events. Agent logic can use a natural language understanding module such as Dialogflow to choose responses. Google lists one-time password, transactional, promotional, and multi-use agent categories, with rules that may vary by country. Businesses typically work with messaging partners to build and maintain agents, and launches require brand verification and approval by Google, carriers, or both. Carriers set rates through their rate cards; billing methods differ for conversational and non-conversational messages, and no fixed public price is listed. Unsupported devices receive a 404 response, so agents should use another channel such as SMS. RBM does not provide end-to-end encryption, and Google says it is not HIPAA compliant.

Spec sheet

Purpose
RCS for Business lets brands engage customers on Android and iOS with branded rich media messaging, read receipts, analytics, and a Verified icon.Read 3 Oct 2026 · developers.google.com
Support
Google provides an RCS for Business support page with a contact option for support and expertise.Read 3 Oct 2026 · developers.google.com
API and webhooks
Agents send messages through the RCS Business Messaging API using HTTP requests with JSON payloads, and receive user messages and events through configured webhooks.Read 3 Oct 2026 · developers.google.com
Billing
Messaging is billable under Standard or US models, and carriers determine rates through their rate cards; conversational and non-conversational categories use different billing methods.Read 3 Oct 2026 · developers.google.com
Business messaging
Agents can send one-way notifications or support back-and-forth conversations about transactions, customer service, promotions, and other business needs.Read 3 Oct 2026 · developers.google.com
Compliance limits
Google states that RBM is not HIPAA compliant; healthcare messages are supported only when they exclude protected health information.Read 3 Oct 2026 · developers.google.com
Encryption limits
Messages are encrypted between user devices and Google servers and between Google servers and messaging partners, but RBM does not provide end-to-end encryption and businesses cannot control the encryption keys.Read 3 Oct 2026 · developers.google.com
Fallback
If a user’s device does not support RCS, the platform returns a 404 error and the agent should use another technology such as SMS.Read 3 Oct 2026 · developers.google.com
Integration
Agent logic can use a natural language understanding module such as Dialogflow to decide how to respond to a user.Read 3 Oct 2026 · developers.google.com
Launch requirements
Launching an agent involves brand verification and approval by Google, carriers, or both, and carrier-managed launches require a direct carrier agreement.Read 3 Oct 2026 · developers.google.com
Partner access
Businesses typically work with messaging partners such as aggregators, CPaaS providers, carriers, and other RCS solution providers to build and maintain agents.Read 3 Oct 2026 · developers.google.com
Rich interactions
Agents use rich cards, media, and suggestions to guide conversations with users.Read 3 Oct 2026 · developers.google.com
Security certifications
Google says RBM and its RCS infrastructure are independently audited annually and hold ISO 27001, SOC 2, and SOC 3 certifications.Read 3 Oct 2026 · developers.google.com
Use cases
Google lists four agent use cases: one-time passwords, transactional, promotional, and multi-use, with rules that can vary by country.Read 3 Oct 2026 · developers.google.com

Plans and prices

Carrier rate card billing Priced on request Carrier rate card; pricing depends on destination region and the agent’s conversational or non-conversational billing category. No fixed public price stated · US carriers set prices · non-US rates follow carrier rate cards Read 3 Oct 2026 · developers.google.com

Every Google RCS for Business plan and price →

Strong points and limits

Strong points

  • Supports rich media, read receipts, and analytics.
  • Provides API messaging and webhooks.
  • Supports one-way notices and two-way conversations.
  • Messages carry a Verified icon.
  • Google states annual independent audits and ISO 27001, SOC 2, and SOC 3 certifications.

Limits

  • No fixed public price is listed; carriers set rates.
  • Unsupported devices require another messaging channel.
  • Messages are not end-to-end encrypted.
  • Not HIPAA compliant; healthcare messages must exclude protected health information.

Who it suits

It suits businesses planning branded customer messaging on Android and iOS that can work with messaging partners and carrier-dependent billing. Healthcare use must exclude protected health information.

Verdict

RCS for Business offers branded rich messaging with API and webhook support, but launching involves verification and typically a messaging partner. Carrier-set pricing, encryption limits, and the HIPAA restriction merit attention before choosing it.

Where Specifiction places it

Alternatives to Google RCS for BusinessAll alternatives →