- Home
- RCS Business Messaging Software
- Google RCS for Business
Google RCS for Business
What it is
Google RCS for Business gives brands a way to send branded messages to customers on Android and iOS, including rich media, read receipts, analytics, and a Verified icon. Agents can deliver one-way notices or conduct two-way conversations about transactions, customer service, promotions, and other business needs. Rich cards, media, and suggested responses can help guide exchanges. Messages are sent through an API using HTTP requests with JSON payloads; configured webhooks return user messages and events. Agent logic can use a natural language understanding module such as Dialogflow to determine responses. Google lists one-time password, transactional, promotional, and multi-use agent categories, with rules varying by country. Businesses typically rely on messaging partners to build and maintain agents, and launches require brand verification and approval by Google, carriers, or both. Messaging is billed under Standard or US models, with rates set by carrier rate cards and billing methods varying by message category. Pricing is on request. If a device does not support RCS, the platform returns a 404 and agents should use another channel, such as SMS. Messages are not end-to-end encrypted, and the service is not HIPAA compliant for messages containing protected health information.
For and against
For
- Supports branded rich media and Verified icons.
- Enables both one-way and two-way messaging.
- API and webhook support for agent messaging.
- Analytics and read receipts are included.
- Supports rich cards, media, and suggestions.
Against
- Pricing is available on request.
- Carrier rates vary by rate card and category.
- Unsupported devices require another channel such as SMS.
- No end-to-end encryption; not HIPAA compliant for PHI.
The verdict
Google RCS for Business combines branded messaging, interactive content, and API-based agent workflows for business communication. Before adopting it, businesses should consider carrier billing, launch requirements, and its limits for encryption and protected health information.
Who it suits
It suits businesses that need branded customer messaging, notifications, or two-way service conversations across Android and iOS. Teams should account for partner access, launch approvals, carrier-set rates, and the stated encryption and healthcare limits.
Plans and prices
Carrier rate card billing
No fixed public price stated · US carriers set prices · non-US rates follow carrier rate cards
Read 3 Oct 2026 · developers.google.com
On the record
- 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.developers.google.com · read 3 Oct 2026
- 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.developers.google.com · read 3 Oct 2026
- Business messaging
- Agents can send one-way notifications or support back-and-forth conversations about transactions, customer service, promotions, and other business needs.developers.google.com · read 3 Oct 2026
- Compliance limits
- Google states that RBM is not HIPAA compliant; healthcare messages are supported only when they exclude protected health information.developers.google.com · read 3 Oct 2026
- 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.developers.google.com · read 3 Oct 2026
- 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.developers.google.com · read 3 Oct 2026
- Integration
- Agent logic can use a natural language understanding module such as Dialogflow to decide how to respond to a user.developers.google.com · read 3 Oct 2026
- Launch requirements
- Launching an agent involves brand verification and approval by Google, carriers, or both, and carrier-managed launches require a direct carrier agreement.developers.google.com · read 3 Oct 2026
- Partner access
- Businesses typically work with messaging partners such as aggregators, CPaaS providers, carriers, and other RCS solution providers to build and maintain agents.developers.google.com · read 3 Oct 2026
- Purpose
- RCS for Business lets brands engage customers on Android and iOS with branded rich media messaging, read receipts, analytics, and a Verified icon.developers.google.com · read 3 Oct 2026
- Rich interactions
- Agents use rich cards, media, and suggestions to guide conversations with users.developers.google.com · read 3 Oct 2026
- Security certifications
- Google says RBM and its RCS infrastructure are independently audited annually and hold ISO 27001, SOC 2, and SOC 3 certifications.developers.google.com · read 3 Oct 2026
- Support
- Google provides an RCS for Business support page with a contact option for support and expertise.developers.google.com · read 3 Oct 2026
- Use cases
- Google lists four agent use cases: one-time passwords, transactional, promotional, and multi-use, with rules that can vary by country.developers.google.com · read 3 Oct 2026
