Rich Communication Services (RCS) extends the simple text message into an interactive experience. For businesses, RCS business messaging offers a way to engage customers with app-like features directly in their phone's native messaging inbox. Unlike proprietary apps, it is built on an open industry standard for carrier messaging.
Key takeaways
- RCS Business Messaging (RBM) enhances SMS with interactive features like rich cards, carousels, and buttons within the default messaging app. However, its availability depends on the recipient's device, mobile carrier, and messaging app.
- It is based on the GSMA Universal Profile, an open standard for interoperable carrier messaging, unlike proprietary platforms like WhatsApp (GSMA Universal Profile).
- A successful RBM strategy requires a "capability check" to confirm if a user can receive RCS. You must also design a clear SMS fallback message for users who cannot receive the rich version.
- Success with RCS requires navigating a complex ecosystem of carrier approvals, sender verification processes, and variable feature support across different devices and deployments.
What is RCS Business Messaging?
RCS Business Messaging is a communication protocol that lets businesses send rich, interactive messages to customers' default texting apps. It extends traditional SMS with features like branded sender profiles, carousels, and quick-reply buttons. The goal is to provide an app-like experience without requiring the customer to download a new app.
RCS stands for Rich Communication Services. It is a standard created by the GSMA, an organization representing mobile network operators worldwide (GSMA RCS overview). The technical foundation for modern RCS is the GSMA Universal Profile, which ensures that different phones and carriers can communicate using a common set of features (GSMA Universal Profile).
Key features of RCS business messaging include:
- Verified Sender Profiles: Messages come from a business name with a logo and brand colors, not an unknown phone number. This builds trust and brand recognition (From Notifications to Conversations).
- Rich Media: Send high-resolution images, videos, and GIFs. Universal Profile 4.0 adds support for streaming video within a message (RCS Universal Profile 4.0 has arrived).
- Rich Cards and Carousels: Display products or information in a structured, scrollable format with images, text, and buttons.
- Suggested Replies and Actions: Guide the conversation with pre-written reply buttons (e.g., "Yes," "No") or action buttons (e.g., "Track Package," "View Website").
- Read Receipts and Typing Indicators: See when a message has been delivered, read, and when the user is typing a reply.
The Universal Profile that underpins RCS also defines broader capabilities including group chat, file transfer, audio messaging, multi-device support, enriched calling, location sharing, and live sketching, though not all features are used in every business messaging implementation (GSMA Universal Profile).
These features enable businesses to build simple automated workflows, like an RCS chatbot for customer support or for completing a transaction.
How RCS Business Messaging Works: A Step-by-Step Guide
The process of sending an RCS message involves several technical steps to ensure the rich content is delivered correctly, or gracefully falls back to SMS if needed.
Here is the end-to-end flow:
Sender Registration and Verification A business first partners with an RCS business messaging provider. Through this provider, the business registers an "agent," which is its official sender profile. This profile includes the brand name, logo, and contact information. The provider and mobile carriers vet this information to verify the business is legitimate, which helps prevent spam.
API Integration The business integrates its software (like a CRM or e-commerce platform) with the provider's API. This connection allows the business's systems to trigger messages automatically based on customer actions, such as a new purchase or a shipping update.
Capability Discovery Before sending a message, the provider's system must check if the recipient can actually receive it. This is called a capability check. The system queries the mobile network to determine if the user's phone number, device, messaging app, and carrier plan all support RCS.
Message Delivery (RCS) If the capability check is successful, the business's system constructs the rich message using JSON or a similar format. The message is sent through the provider to the user's mobile carrier and delivered to their default messaging app. The user sees the message from the verified brand profile and can interact with its rich elements.
Message Delivery (SMS Fallback) If the capability check fails, the system does not send the RCS message. Instead, it triggers an SMS fallback. This is a pre-written, plain-text version of the message. This ensures every user gets the core information, even if they miss out on the interactive experience.
Interaction and Governance When a user interacts with a message, the platform logs the event, such as a button tap. The behavior of these interactions—as well as delivery receipts, read receipts, and typing indicators—is governed by the specific RCS profile, operator deployment, and client. The Universal Profile includes enablers for business messaging, privacy controls, and spam protection, but their implementation is not identical everywhere (GSMA Universal Profile).
RCS vs. SMS vs. WhatsApp: A Comparison
Choosing the right messaging channel depends on your audience, goals, and technical resources. While RCS business messaging extends SMS, it exists in an ecosystem alongside proprietary apps like WhatsApp. Each has distinct advantages and disadvantages.
| Attribute | RCS Business Messaging | SMS | WhatsApp Business |
|---|---|---|---|
| Foundation | Open standard (GSMA) | Open standard (legacy) | Proprietary (Meta) |
| Reach | Growing but fragmented; depends on carrier, device, and app support. | Nearly universal reach to any mobile phone. | Limited to users who have the WhatsApp app installed. |
| Features | Rich cards, carousels, buttons, high-res media, branding. | Plain text, standard-res MMS media, links. | Rich media, buttons, product catalogs, lists, location sharing. |
| Sender Identity | Verified brand profile with logo and colors. | Phone number or alphanumeric ID (in some regions). | Verified business profile with logo and description. |
| Encryption | Encrypted in transit (not end-to-end by default) (RCS versus WhatsApp comparison). | Generally unencrypted. | End-to-end encrypted by default. |
| User Experience | Delivered to the phone's native messaging app. | Delivered to the phone's native messaging app. | Requires the user to open the separate WhatsApp app. |
Worked Example: An E-commerce Order Confirmation Flow
Let's make this concrete. Imagine a customer named Alex just bought a pair of shoes from a website. The e-commerce store wants to send an interactive order confirmation.
Scenario: Send an order confirmation with a tracking link and a receipt link.
Capability Check: The store's messaging system sends a capability discovery request for Alex's phone number. The network responds that Alex's Android phone and carrier support RCS.
RCS Message Payload: The system constructs an RCS message. The following is a simplified, illustrative example of the data structure for a rich card.
JSON { "agent": "ShoeWorld", "recipient": "+15551234567", "message": { "type": "richCard", "content": { "title": "Your order is confirmed!", "description": "Order #SW-8675309", "media": { "url": "https://example.com/shoes.png", "height": "MEDIUM" }, "actions": [ {"label": "Track Package", "url": "https://example.com/track/8675309"}, {"label": "View Receipt", "url": "https://example.com/receipt/8675309"} ] } } }User View (RCS): Alex receives a message in their default texting app. It appears from "ShoeWorld" with the company's logo. The message contains an image of the shoes, the order number, and two clear buttons: "Track Package" and "View Receipt." Tapping a button opens the corresponding link in a web browser.
SMS Fallback: Now, imagine a different customer, Sam, made the same purchase. The capability check for Sam's number fails because they have an older phone that doesn't support RCS. The system automatically sends the fallback message instead:
ShoeWorld: Your order #SW-8675309 is confirmed. Track your package here: https://ex.co/track/8675309. View your receipt here: https://ex.co/receipt/8675309.
Sam gets the same essential information and links, but the experience is less visually appealing and interactive.
When Should You Not Use RCS Business Messaging?
While powerful, RCS is not the right tool for every job. The complexity of its ecosystem means that sometimes a simpler channel is more effective.
- When your audience is primarily on devices that do not support RCS. RCS adoption is centered on Android. A user base dominated by iPhone users often means a high fallback rate to SMS, so the effort of creating rich content may not provide a good return on investment.
- For mission-critical alerts requiring universal reach. For things like one-time passwords, fraud alerts, or emergency notifications, the near-100% deliverability of SMS is paramount. The added complexity of a capability check and potential fallback logic can be a liability.
- If you operate in regions with poor carrier support. Before investing in an RCS project, research its adoption among carriers in your key markets. If major carriers haven't enabled it, you are effectively building a complex SMS campaign, as most of your messages will fall back.
- When your budget is zero. Unlike sending a basic SMS from a number, setting up a verified RCS sender profile involves a formal onboarding process with a messaging provider. This process can involve setup fees, monthly costs, and per-message charges that may be higher than SMS.
What Are the Common Mistakes and Limits of RCS?
Implementing RCS business messaging requires careful planning to avoid common pitfalls that stem from its fragmented ecosystem.
Common Mistakes
- Assuming Universal Support: The biggest mistake is designing a campaign that only works with rich features. Always design the SMS fallback experience first to ensure the core message is clear and functional for all recipients.
- Neglecting the Onboarding Process: Businesses often underestimate the time required for sender verification. Getting your brand profile and messages approved by carriers can take days or even weeks. Start this process early.
- Designing for a Single Client: An RCS rich card may look different on a Google Messages app versus a Samsung Messages app. Always test your messages on multiple devices and clients to ensure a consistent experience.
- Failing to Manage Consent and Privacy: RCS is subject to the same legal regulations as SMS. You must have explicit consent from users to send them messages, and you must respect anti-spam requirements and provide a clear, functional way to opt out.
- Using a Chatbot for Every Interaction: Avoid using a chatbot for every use case without providing clear escalation paths to a human agent or a standard web or app workflow.
- Ignoring Channel Context: Sending frequent promotional content without considering that RCS is an interruptive channel can damage user trust, which depends on a recognizable sender identity and relevant messages.
Technical and Practical Limits
- Lack of End-to-End Encryption: Standard RCS business messaging only encrypts data in transit (RCS versus WhatsApp comparison). This is less secure than platforms like WhatsApp that use end-to-end encryption by default, making RCS potentially unsuitable for transmitting highly sensitive personal information.
- Inconsistent Feature Support: Even if a user's device supports RCS, it may not support the latest features from the Universal Profile. For example, support for video or specific button types can vary. Campaigns should rely on widely supported core features.
- Evolving Standards: The GSMA Universal Profile standard evolves to address limitations. For example, Universal Profile 4.1 was introduced to improve transport-layer efficiency and add formal support for messaging-initiated video calls and standardized spam reporting (RCS Universal Profile 4.1). However, deployment of new profile features is not immediate or uniform across all networks.
- Complexity in Measurement: Analyzing an RCS campaign is more complex than SMS. You need to track not just delivery rates, but also RCS-capable rates, fallback rates, and interaction rates for each button or rich element. This requires robust Chatbot Analytics Metrics: A Practical Guide and reporting.
What to learn next
- Conversation Design Chatbot: A Practical Guide: Learn how to structure interactive conversations that guide users effectively, a key skill for building RCS chatbots.
- Chatbot Analytics Metrics: A Practical Guide: Discover the key metrics for measuring the performance of an automated messaging campaign, from user engagement to fallback rates.
- Intent Classification vs LLM: Which to Choose?: Understand the different AI technologies you can use to power the logic behind your RCS chatbot's responses.
