Google RCS for Business
developers.google.com
- Web
- iPhone and iPad
- Android
- API
What Google RCS for Business is
Google RCS for Business lets brands communicate with customers on Android and iOS using branded messages, rich media, read receipts, analytics, and a Verified icon. Agents can send one-way notifications or support two-way exchanges about transactions, customer service, promotions, and other business needs. Rich cards, media, and suggested interactions can guide users through a conversation. Agents send messages through an API using HTTP requests with JSON payloads, while configured webhooks deliver user messages and events. An agent’s response logic can use a natural language understanding module such as Dialogflow.
Google lists agent categories for one-time passwords, transactional, promotional, and multi-use messaging; rules may differ by country. Businesses typically work with messaging partners to build and maintain agents. Launch requires brand verification and approval by Google, carriers, or both; carrier-managed launches also require a direct carrier agreement. Carriers set rates through their rate cards, with different billing methods for conversational and non-conversational messages. Unsupported devices return a 404, 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.
Who it suits
It suits brands and businesses that want to build rich, branded messaging agents for Android and iOS, typically with a messaging partner. Teams should be prepared for carrier-based billing, launch approvals, and the stated encryption and healthcare limits.
Good to know, and what to watch
- Supports rich cards, media, and suggested interactions
- Offers one-way notices and two-way conversations
- API and webhooks support message exchange and events
- Google says RBM holds ISO 27001, SOC 2, and SOC 3 certifications
- No fixed public price; carriers set rates
- Brand verification and launch approval are required
- Unsupported devices need another channel, such as SMS
- No end-to-end encryption; not HIPAA compliant
Plans
Every plan and priceCarrier rate card billing
Pricing on request
The verdict
RCS for Business combines branded messaging with API and webhook tools for agent-based communication. Assess carrier rates, launch requirements, fallback handling, and the limits on encryption and healthcare content before choosing it.
What the maker publishes
- 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. source
- 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. source
- Business messaging
- Agents can send one-way notifications or support back-and-forth conversations about transactions, customer service, promotions, and other business needs. source
- Compliance limits
- Google states that RBM is not HIPAA compliant; healthcare messages are supported only when they exclude protected health information. source
- 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. source
- 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. source
- Integration
- Agent logic can use a natural language understanding module such as Dialogflow to decide how to respond to a user. source
- Launch requirements
- Launching an agent involves brand verification and approval by Google, carriers, or both, and carrier-managed launches require a direct carrier agreement. source
- Partner access
- Businesses typically work with messaging partners such as aggregators, CPaaS providers, carriers, and other RCS solution providers to build and maintain agents. source
- Purpose
- RCS for Business lets brands engage customers on Android and iOS with branded rich media messaging, read receipts, analytics, and a Verified icon. source
- Rich interactions
- Agents use rich cards, media, and suggestions to guide conversations with users. source
- Security certifications
- Google says RBM and its RCS infrastructure are independently audited annually and hold ISO 27001, SOC 2, and SOC 3 certifications. source
- Support
- Google provides an RCS for Business support page with a contact option for support and expertise. source
- Use cases
- Google lists four agent use cases: one-time passwords, transactional, promotional, and multi-use, with rules that can vary by country. source
Checked against the maker's pages on 3 Oct 2026.