Google RCS for Business vs smsmode RCS API
Google RCS for Business
developers.google.comsmsmode RCS API
smsmode.comSide by side
| Figure | Google RCS for Business | smsmode RCS API |
|---|---|---|
| Price from | — | €9/mo |
| Free plan | — | — |
| Free trial | — | Yes |
| Open source | — | — |
| Web | Yes | Yes |
| iOS | Yes | — |
| Android | Yes | — |
| API | Yes | Yes |
| Plans published | 1 | 7 |
| Spec score · RCS Messaging Platforms | 7.5 (#14) | 7.6 (#13) |
| Spec score · RCS Business Messaging Software | 7.5 (#12) | 7.6 (#11) |
| 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. | For devices that cannot receive RCS, smsmode says it offers fallback to SMS. |
| Support | Google provides an RCS for Business support page with a contact option for support and expertise. | The manufacturer advertises 24/7 technical support and a knowledge base. |
| Use cases | Google lists four agent use cases: one-time passwords, transactional, promotional, and multi-use, with rules that can vary by country. | The company presents RCS for marketing, notifications, booking confirmations, delivery alerts, order notifications, customer service, and OTP messages. |
Plans
Google RCS for Business
- Carrier rate card billingPriced on request
smsmode RCS API
- Basic€9 a month
- Classic€69 a month
- Medium€159 a month
- Premium€499 a month
- Medium subscriptionPriced on request
- Premium subscriptionPriced on request
- Standard SubscriptionPriced on request
In their own words
Google RCS for Business
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.
smsmode RCS API
smsmode RCS API lets businesses build rich messaging conversations through a REST API. It supports images, maps, action buttons, carousels, sessions, statuses, and RCS agent authentication; messages can also carry video, audio, documents, QR codes, geolocation, payments, and links. Listed uses include marketing, notifications, booking confirmations, delivery and order alerts, customer service, and one-time passwords. Where a device cannot receive RCS, the service offers SMS fallback. Customers must register their RCS agent with Google and carriers before sending. The RCS page says campaigns can reach more than 10 countries, including France, the United Kingdom, Spain, Italy, and Germany. Reporting includes real-time delivery receipts, read rates, and click rates. Listed integrations include HubSpot, Salesforce, Oracle Eloqua, Selligent, Customer.io, Google Calendar, Zapier, Klaviyo, and Adobe Campaign. Account controls can hash content or recipients, truncate the last four digits of recipient numbers, shorten retention, or delete message content after sending. A free trial is available, but there is no free plan; listed message plans start at €9 a month excluding taxes, while the pricing note says from €69/mo.