Concepto Móvil RCS API vs Google RCS for Business

Concepto Móvil RCS API lets businesses send interactive RCS messages and manage campaigns through the Broadcaster RCS web portal. Messages can contain images, video, GIFs, carousels, and interactive cards; buttons can open URLs, place calls, show locations, or provide predefined replies. Businesses can use a name and logo verified by Google. The product lists delivery, read, click, and interaction metrics, along with real-time webhooks for delivery, read, and interaction events. If a recipient’s device does not support RCS, the API provides automatic SMS fallback. The API uses HTTPS REST, access tokens, and JSON encoded as UTF-8. Customers must request registration of their public IP address to receive authentication credentials. Broadcaster RCS includes a visual editor, templates, exclusion lists, campaign scheduling, and reports, and is designed for campaign management without programming. The API can integrate with existing applications such as CRMs, ERPs, and payment gateways. Pricing is on request; the listed trial lasts 14 days with no commitment. Concepto Móvil is based in Mexico City and lists ISO 27001 as its information security management certification.

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.