Google RCS for Business

Web · Android · iPhone · API

Freedom report

Two barsScore 5.5

  • Free tierNo free tier on record
  • Open codeNo open-source code on record
  • Runs widely3 of 6 device platforms
  • DocumentedPlans, terms and facts published

Google RCS for Business lets brands send branded rich-media messages to customers on Android and iOS, with read receipts, analytics, and a Verified icon. Agents can deliver 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 a conversation. Agents send messages through an API using HTTP requests with JSON payloads, while configured webhooks receive user messages and events. Agent logic can use a natural language understanding module such as Dialogflow to decide on responses. Google lists one-time password, transactional, promotional, and multi-use agent types, though rules can vary by country. Businesses typically work with messaging partners to build and maintain agents; launches require brand verification and approval by Google, carriers, or both. Carriers set rates through rate cards, with billing methods differing by message category. 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 states it is not HIPAA compliant.

Who it is for

RCS for Business suits brands building customer messaging agents for Android and iOS, including notification and conversational use cases. Businesses should be prepared to work with messaging partners and meet launch approval requirements.

What is good

  • Supports branded rich media and Verified icons
  • Offers API access and webhook support
  • Supports one-way notifications and two-way conversations
  • Provides read receipts and delivery analytics

What to know first

  • Pricing depends on carrier rate cards
  • Unsupported devices require another messaging channel
  • Messages are not end-to-end encrypted
  • Not HIPAA compliant

Verdict

RCS for Business provides API-based branded messaging, with carrier pricing and launch approvals to plan for. Its encryption and healthcare compliance limits may rule it out for some uses.

Google RCS for Business plans and pricing

All plans
Carrier rate card billing Not published 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 developers.google.com · 3 Oct 2026

Compared on RCS messaging platforms

Two-way messaging
Yes

Best Google RCS for Business alternatives

See all 20