Your competitor's promotional message arrives with a product carousel, a branded logo, and a "Buy Now" button — all inside the customer's native messaging app. Your message, sent via SMS, shows up as 160 characters of plain text from an unrecognized number. The customer taps your competitor's button. They never read yours.
This gap is what Rich Communication Services closes. An RCS message replaces the limitations of SMS with rich media, interactive elements, and verified business branding — without requiring the customer to download anything. After years of fragmented rollout, RCS hit a turning point when Apple added support in iOS 18 in late 2024. The channel now reaches the majority of smartphones in major markets, and businesses that rely solely on text-only messaging are losing ground.
This guide covers what RCS messaging is, how it compares to SMS and MMS, where coverage stands in 2026, and how to start sending RCS messages through a single API integration.
RCS (Rich Communication Services) is a messaging protocol developed by the GSMA to replace SMS as the default standard on mobile devices. Where SMS runs over the cellular voice network and caps out at 160 text characters, RCS operates over data connections — Wi-Fi or mobile data — and supports images, video, carousels, suggested replies, and action buttons natively inside the phone's default messaging app.
The distinction matters for business. An A2P RCS message shows the customer a verified business name, logo, and color scheme instead of a random phone number. The customer sees who sent it before they read a word. That verification layer alone addresses the single biggest trust problem in SMS-based communication: impersonation.
At BSG, we've seen that businesses adding RCS to their messaging mix report measurably higher tap-through rates on promotional campaigns compared to SMS-only sends — particularly in markets where Android dominates and BSG RCS messaging platform is supported by local carriers. The mechanism is straightforward: richer content per message means fewer messages needed to drive the same action.
RCS is not an app. It's not WhatsApp, Viber, or Telegram. Those are OTT (over-the-top) platforms that require the customer to download software and create an account. RCS works inside the messaging app the phone ships with — Google Messages on Android, the Messages app on iOS 18 and later. No download, no sign-up, no additional opt-in friction.
The practical difference between SMS, MMS, and RCS comes down to three things: what you can put in the message, whether the customer knows who sent it, and what data you get back.
SMS delivers text. Up to 160 characters per segment over the GSM network. No images, no branding, no confirmation that the message was read. MMS extends SMS with media attachments — photos and short video — but file sizes are compressed, quality degrades, and support varies by carrier and region. Neither SMS nor MMS tells you whether the customer opened the message.
RCS changes each of those constraints. Messages support high-resolution images, carousels of up to ten cards, action buttons (call, visit URL, add to calendar), and suggested replies. The sender appears as a verified business profile with a name, logo, and description. And RCS provides read receipts and typing indicators — giving the sender confirmation that the message was seen, not just delivered.
| Feature | SMS | MMS | RCS |
|---|---|---|---|
| Media | Text only | Images, short video | Images, video, carousels |
| File quality | N/A | Compressed | High-resolution |
| Max size | 160 chars/seg | ~300KB–600KB | Up to 10MB |
| Branding | None | None | Verified sender profile |
| Interactivity | None | None | Buttons, suggested replies |
| Read receipts | No | No | Yes |
| Typing indicator | No | No | Yes |
| Delivery method | Cellular/GSM | Cellular/GSM | Data (Wi-Fi / mobile) |
| Fallback | N/A | N/A | SMS fallback recommended |
For a product manager evaluating channel performance, this is the core shift: RCS turns a broadcast channel into a measurable, interactive one. A retailer promoting a flash sale can send a carousel of five products with "Add to Cart" buttons. A bank can send a transaction alert with a "Report Fraud" button. The customer acts inside the message thread instead of being redirected to a browser.
RCS business messaging traffic reached approximately 50 billion messages globally in 2025, and Juniper Research forecasts this will exceed 200 billion by 2027 (Juniper Research, 2026). That growth is driven by a simple calculation: when engagement per message increases, the total number of messages a business needs to send decreases. We've worked with teams who switched promotional campaigns from SMS to RCS and found that click-through rates improved significantly while message volume dropped — because fewer messages were wasted on customers who never saw the content.
For a detailed comparison of when RCS, SMS, and other channels fit best, see the practical business case for RCS.
RCS Business Messaging is the A2P (application-to-person) version of RCS — what businesses use to send messages to customers at scale. It operates through a verified agent profile registered with Google's Jibe platform or directly through carrier hubs.
Every RCS business message arrives from a verified sender. The customer's messaging app displays the business name, logo, brand color, and a verification badge before the message body loads. This is not a cosmetic upgrade — it's a trust mechanism. SMS-based phishing (smishing) works because the recipient cannot tell whether a message genuinely came from their bank or from a spoofed number. RCS sender verification makes impersonation structurally harder.
In our experience working with fintech clients in Europe, the shift to branded RCS messages reduced customer-reported phishing confusion — because the verified badge gave customers a visual signal they could trust before interacting with the message content.
An RCS message can include standalone images, video, file attachments, and interactive carousels. Carousels display multiple cards — each with an image, title, description, and action button — that the customer swipes horizontally. Action buttons trigger specific outcomes: opening a URL, initiating a phone call, sharing a location, or loading a pre-filled reply.
Consider a travel company sending a booking confirmation. Via SMS, the customer gets a text with a booking reference number and a URL. Via RCS, the same confirmation includes the hotel image, check-in time, a "Get Directions" button linking to maps, and a "Modify Booking" button connecting to support. The information and the action live in the same place.
RCS provides delivery confirmation, read receipts, and typing indicators. For marketing teams, read receipts mean the difference between knowing a message was delivered to a device and knowing a customer actually opened it. For support teams using 2-way messaging, typing indicators signal that the business is actively responding — reducing the anxiety gap that causes customers to abandon chat threads.
The practical impact: open-rate visibility from RCS read receipts gives marketing teams far more accurate campaign performance data than SMS delivery reports alone, which only confirm that the carrier accepted the message — not that the customer read it.
RCS coverage depends on two factors: device support and carrier enablement. Both have expanded rapidly since 2024, but gaps remain — and those gaps determine whether a business can rely on RCS alone or needs a fallback strategy.
Android is where RCS started. Google has pushed RCS as the default messaging protocol in Google Messages since 2019, and today RCS is enabled by default on most new Android devices. With Android holding over 70% of global mobile OS market share (Statista, 2025), the Android side of RCS coverage is close to universal in markets where carriers have enabled it.
The Juniper Research projection of 3.8 billion active RCS users by end of 2026 (Juniper Research, 2025) is largely driven by Android's installed base. In practice, if a customer has a modern Android phone and a carrier that supports RCS, they're already reachable.
Apple introduced RCS support in iOS 18 in September 2024 for person-to-person messaging, and added RCS for Business (A2P) support with iOS 18.1 in October 2024. This was the inflection point the industry had waited on for years — Apple's absence was the single largest barrier to RCS becoming a viable business channel.
By mid-2025, iOS 18 adoption had expanded carrier support across major US carriers (AT&T, T-Mobile, Verizon), with European carriers like Orange, Vodafone, EE, and Deutsche Telekom following through iOS 18.4 and 18.5 updates. RCS messages on iPhone still appear as green bubbles — Apple has kept the visual distinction from iMessage — but the messaging experience now includes read receipts, high-resolution media, and interactive elements.
Coverage is still carrier-dependent. In the US, RCS on iPhone reaches an estimated 70% or more of iPhone users on supported carriers. In Europe, rollout is ongoing and uneven — some carriers support both P2P and A2P RCS on iPhone, others are still in the process. In emerging markets across Africa and parts of Southeast Asia, carrier-level RCS enablement remains limited.
This is why cascade routing matters. A message sent via RCS that cannot be delivered — because the recipient's carrier doesn't support it, or because the device is too old — should automatically fall back to SMS. Without that fallback, the message simply doesn't arrive. At BSG, we built SMS fallback directly into our cascade routing logic specifically because we've seen what happens when businesses launch RCS without it: delivery gaps in markets where coverage is partial, and no visibility into which messages failed.
RCS is not a channel that fits every message type. It performs best where an RCS message adds clear value through visual content, interactive elements, or verified branding — situations where plain-text SMS creates friction or loses engagement.
A fashion retailer sends a weekly "New Arrivals" campaign. Via SMS, the message includes a short text and a link to the website. Via RCS, the same campaign arrives as a carousel of five products — each with an image, price, and "View Details" button. The customer browses and taps without leaving the messaging app. For eCommerce teams looking to reduce the steps between awareness and purchase, RCS carousels compress the funnel inside the conversation itself. See how BSG supports omnichannel marketing for retail and eCommerce.
A bank sends a transaction notification. Via SMS: "Purchase of $247.50 at Store X. Reply STOP to block." Via RCS: the same alert arrives with the bank's verified logo, a "View Transaction" button linking to the mobile banking app, and a "Report Fraud" button that connects directly to the fraud team. The customer doesn't need to call a helpline or navigate a website — the action is embedded in the alert.
What our clients have found is that interactive RCS alerts in financial services reduce call center volume for routine transaction inquiries, because customers can self-serve directly from the message thread instead of calling in to verify a charge.
An airline sends a check-in reminder 24 hours before departure. Via SMS: a text with a link. Via RCS: a branded message with the flight details, a "Check In Now" button, and after check-in, the boarding pass rendered as a rich card with a barcode — all inside the default messaging app. No email to search for, no app to open.
Additional use cases span healthcare (appointment reminders with "Confirm" or "Reschedule" buttons), logistics (delivery tracking with real-time status updates and "Reschedule Delivery" options), and insurance (claims status with document upload prompts).
Sending RCS at scale requires a CPaaS provider with carrier connections, message template management, and fallback logic. BSG handles all three through a single integration.
BSG's One API unifies SMS, RCS, Viber, WhatsApp, Email, and Voice through a single integration point. Instead of building separate integrations for each channel, a development team connects once and routes messages to the appropriate channel based on availability and business logic. For RCS specifically, BSG manages the verified agent profile registration, message template approval, and carrier-level delivery routing.
The development team writes one API call. BSG determines whether the recipient's device and carrier support RCS, and routes accordingly. If RCS is available, the rich message is delivered. If not, the message falls back — automatically and in real time.
This is where partial RCS coverage becomes a solvable problem instead of a dealbreaker. BSG's cascade routing with SMS fallback ensures that every message reaches the customer regardless of RCS support on their device or carrier. The logic is simple: attempt RCS first; if delivery fails or RCS is unsupported, fall back to SMS through BSG's direct carrier routes.
For the businesses we work with across multiple markets, cascade fallback is not an optional add-on — it's the default. Launching RCS without SMS fallback in 2026 means accepting that a portion of your customers won't receive the message at all. With BSG's 60+ direct MNO connections globally, the fallback SMS is delivered through 0-hop routes — meaning even the fallback path has higher delivery rates and lower latency than many primary SMS routes through aggregators.
If you're evaluating RCS for promotional campaigns, transactional alerts, or customer support — BSG has deployed RCS with cascade SMS fallback across multiple markets. One API integration. Verified sender profiles. Automatic fallback when RCS isn't available. Talk to BSG about launching RCS and we'll walk through your specific channels, markets, and use case.
A regular text (SMS) delivers up to 160 characters of plain text over the cellular network with no media, no branding, and no read confirmation. An RCS message operates over data connections and supports images, carousels, interactive buttons, verified sender branding, and read receipts — all inside the same messaging app. The customer experience is closer to a messaging app like WhatsApp, but without requiring a separate download.
No. RCS messages arrive in the default messaging app on your phone — Google Messages on Android, the Messages app on iPhone (iOS 18 or later). There is nothing to install, no account to create, and no additional opt-in step. If the device and carrier support RCS, messages are received automatically.
Yes. Apple introduced RCS support with iOS 18 in September 2024 and expanded it through subsequent updates in 2025. RCS availability on iPhone depends on the carrier — most major US and European carriers now support it. RCS messages on iPhone appear as green bubbles but include rich features like high-resolution images, read receipts, and interactive buttons.
Yes. Businesses send RCS messages through a CPaaS provider that handles verified agent registration, message template management, and carrier routing. BSG's One API allows businesses to send RCS at scale through a single integration — with automatic SMS fallback for devices or carriers that don't yet support RCS.
30% of SMS fail — not because of content, but numbers. Verify before you send.
Marketing is a nuanced endeavor that requires diverse strategies to attract and retain customers. The
The outbreak of the COVID-19 pandemic led to customers’ high patronage of e-commerce stores due
