RCS Marketing: The Complete Guide for B2C Teams

RCS marketing gives brands a richer, more interactive way to reach customers directly on their phones. This guide covers everything you need to know: what RCS is, how it compares to SMS and MMS, what compliance requires, and how to integrate it into your existing campaigns. Whether you're just getting started or ready to go deeper, it's all here.

Note: This page covers a lot of ground, and the territory comes with a lot of abbreviations. Every term is defined on first use, and Section 3 has a full glossary if you need a quick reference at any point.

1. What Is RCS?

If you've landed here, you've probably heard that RCS is changing the way brands communicate with customers, and you want to understand what that actually means before deciding whether it belongs in your channel mix. This section covers the basics: what RCS is, how it compares to the messaging formats you already use, and what a customer actually experiences when they receive an RCS message.

What does RCS stand for?

RCS stands for Rich Communication Services. It is a messaging protocol — a set of rules that governs how messages are sent, received, and displayed — built to succeed SMS (Short Message Service) and MMS (Multimedia Messaging Service) as the standard for mobile messaging. Where SMS is text-only and capped at 160 characters, and MMS adds basic media support, RCS delivers an app-like experience directly inside a phone's native messaging app, with no download required.

What is RCS Business Messaging (RBM), and how is it different from RCS?

RCS Business Messaging, commonly abbreviated as RBM, is the commercial application layer built on top of the RCS protocol. RCS is the underlying technology. RBM is the specific implementation that allows a brand to send verified, branded messages to consumers at scale. When marketers talk about RCS business messaging, they are almost always referring to RBM. Google now uses the term "RCS for Business" interchangeably.

What's the difference between RCS and SMS? What about RCS vs. MMS?

The difference between RCS and SMS comes down to capability and architecture. SMS is a cellular protocol limited to 160 characters of plain text per message, with no support for branding, read receipts, or interactivity. It works on virtually every phone everywhere, which is exactly why it remains the fallback standard.

RCS vs. MMS is a closer comparison. MMS extended SMS by allowing images, audio, and short video — but still within significant size and quality constraints, and still without branding or interactivity. The difference between RCS and MMS is that RCS delivers a fundamentally richer messaging experience: verified sender identity, high-resolution images and video, interactive buttons, suggested replies, scrollable carousels, and real-time read receipts. RCS messages also travel over IP (internet protocol), the same infrastructure that powers apps like WhatsApp and iMessage, rather than through the cellular network.

Feature	SMS	MMS	RCS
Character limit	160	Varies	3,072
Rich media	No	Basic	High-res images, video, files
Verified sender	No	No	Yes
Read receipts	No	No	Yes
Interactive buttons	No	No	Yes
Branded sender profile	No	No	Yes
Delivery infrastructure	Cellular	Cellular	IP-based
SMS fallback	N/A	N/A	Yes (automatic)

Who created RCS? Who governs the standard?

RCS is governed by the GSMA (Global System for Mobile Communications Association), the international body that sets standards for mobile networks worldwide. The GSMA's Universal Profile is the technical specification that defines how RCS works across carriers and devices, making interoperability possible at scale. The most current version is Universal Profile 3.1, published in July 2025, which introduced improvements to media quality, network connectivity, and security.

Google has played a central role in accelerating RCS adoption through its Messages app on Android and the Jibe platform, which provides RCS infrastructure for carriers globally. Apple's adoption of RCS in iOS 18, released in September 2024, was the inflection point the channel had been waiting for: for the first time, brands could send rich, verified messages to both Android and iPhone users through their native messaging apps.

What does an RCS message actually look like to the customer?

From the customer's perspective, an RCS message arrives in their native messaging app — the same place they receive texts from friends and family. What looks different: the sender appears with a verified business name and logo rather than an unknown phone number or shortcode. The message itself can include a high-resolution image or video, a text block of up to 3,072 characters, and one or more interactive buttons that the recipient can tap without leaving the app. If the message includes multiple content units — say, three product options — they may appear as a scrollable carousel of rich cards.

Think of it as the engagement power of an email combined with the open rates of a text message — delivered natively to the inbox people actually check first.

What are the main features of RCS business messaging?

The core feature set of RCS business messaging includes:

Verified sender identity: customers see a confirmed business name, logo, and verified checkmark — not a random number
Rich cards: structured message units combining an image, text, and action buttons
Carousels: horizontally scrollable sequences of 2–10 rich cards in a single message
Suggested replies and suggested actions: tappable buttons that let customers respond or act instantly — shop, call, navigate, confirm
Read receipts: confirmation a message was opened, not just delivered
High-resolution media: images, video, audio, and files without MMS compression
3,072-character message limit: compared to SMS's 160

Automatic fallback to SMS/MMS: when a recipient's device doesn't support RCS

Does RCS require the customer to download an app?

2. RCS Reach and Device Coverage

Before adding RCS to your channel mix, you need to know whether it can reach your audience. This section covers which devices support RCS, what Apple's adoption changed for brands, how fallback works for customers who aren't on RCS yet, and what the coverage picture looks like across carriers and geographies.

What devices support RCS?

RCS is supported on Android and iPhone devices, covering both dominant mobile operating systems. On Android, RCS runs natively through Google Messages, the default messaging app on most Android phones sold today. Google's Jibe backend also provides RCS connectivity in regions where a carrier hasn't deployed it directly, giving Android users broad access regardless of carrier.

On iPhone, RCS is available on iOS 18 and later. With iOS 18.4, released in March 2025, Apple expanded support to cover nearly all US carriers, including MVNOs like Mint Mobile, Google Fi, and Metro by T-Mobile. All three major US carriers — AT&T, T-Mobile, and Verizon — support RCS on iPhone.

For RCS business messaging specifically, reach depends on an additional layer: whether the recipient's carrier has enabled business-grade (A2P) RCS, not just person-to-person. That picture is expanding steadily but is not yet uniform across every carrier and region.

When did Apple adopt RCS? What changed for brands?

Apple announced RCS support at WWDC in June 2024 and shipped it with iOS 18 in September 2024, with RCS for Business following in iOS 18.1 in October 2024. Apple's adoption of RCS on iPhone was the shift brands had been waiting for: for years, the channel's reach was limited to Android, which capped the audience for any RCS campaign. iOS 18 changed that completely.

iPhones represent around 57% of the US smartphone market, and as of early 2025, approximately 68% of compatible iPhones had upgraded to iOS 18 or later. For consumer brands with US customer lists, that's a meaningful share of previously unreachable devices now in scope for RCS campaigns.

A note on green bubbles: Apple-to-Android RCS conversations still appear as green bubbles on iPhones. That's a display distinction, not a functional limitation. The underlying experience — high-resolution media, read receipts, verified sender identity — is fully intact for branded business messages.

What happens when a customer's device doesn't support RCS?

When a recipient's device doesn't support RCS, the message falls back automatically to SMS or MMS. The customer still receives the message — they just don't get the rich formatting: no interactive buttons, no carousels, no read receipts. Content arrives as plain text or basic media. This is worth designing for, particularly for customer lists with international contacts where RCS carrier coverage is still expanding.

What is fallback logic, and who manages it?

RCS fallback logic is the system that detects whether a recipient can receive RCS and reroutes to SMS or MMS if they can't. Before a message sends, the platform runs a capability check against the recipient's device and carrier. If RCS is available, the full rich message goes through. If not, the message is automatically reformatted and delivered as SMS or MMS.

Fallback is managed by the aggregator or business messaging platform — not by your team, the carrier, or the recipient's device. You configure one message; the platform handles routing per recipient in real time. Sureshot manages fallback configuration as part of onboarding so your team doesn't maintain that logic manually.

Does RCS work internationally?

Yes, though coverage varies by region. RCS has full carrier coverage in Canada, Mexico, Brazil, the UK, Germany, France, Spain, Italy, and India, among others. Other countries have partial coverage, with some local operators supporting RCS while others have not yet deployed it. For brands with primarily US-based customer lists, the coverage picture is strong. For global programs, per-recipient capability checks and graceful fallback become especially important.

Which carriers support RCS in the US?

All three major US carriers (AT&T, T-Mobile, and Verizon) support RCS on both Android and iPhone, including RCS for Business. As of early 2025, support has extended to a wide range of MVNOs including Cricket, Metro by T-Mobile, Xfinity Mobile, Spectrum, Visible, Boost, TracFone, US Cellular, and others. The list continues to grow. RCS has reached mainstream carrier support in North America.

What share of my customer list can realistically receive RCS today?

It depends on your audience and geography, but the numbers are moving quickly in a favorable direction. In the US, with major carrier support covering both Android and iPhone, a meaningful share of any consumer list is RCS-capable today. The practical approach: run a capability check on your list before your first send. Your aggregator or platform will tell you exactly which contacts can receive RCS right now. Everyone else gets SMS fallback. As coverage expands, that RCS-capable share will grow without any changes on your end.

Globally, RCS had over 1.5 billion monthly active users in 2025. The market is projected to grow from roughly $3 billion in 2025 to around $9 billion by 2030.

3. Verification and Sender Identity

One of the most meaningful differences between RCS and SMS is that RCS senders are verified. Customers see your brand name, logo, and a checkmark rather than an unknown phone number or shortcode. That trust signal is built through a formal registration process, and it's required before you can send a single RCS business message.

What is a Verified Sender in RCS?

A verified sender in RCS is a business that has been authenticated by Google, carriers, or both, and whose identity is confirmed before any messages reach recipients. When a verified RCS message arrives in a customer's inbox, they see the brand name, logo, brand color, and a verification badge at the top of the conversation. This replaces the anonymous shortcode or 10-digit number customers see with SMS.[1]

Verification matters for two reasons. First, it protects customers from spam and phishing — only authenticated businesses can send branded RCS messages. Second, it protects your brand: your name and logo can only appear in a customer's inbox if you've gone through the verification process. No one can impersonate a verified RCS sender.[2]

What is an RCS Agent, and how do you create one?

An RCS Agent is the verified business profile that represents your brand in RCS messaging conversations. It is the sender identity customers interact with: your business name, logo, brand color, a brief description, and contact information. When a customer taps your name at the top of the conversation, they see this full profile.[3]

Creating an agent happens through the Google Business Communications Developer Console, typically via your aggregator or a platform partner like Sureshot. You define the agent profile, provide required assets and compliance documentation, and submit for review. Most brands work through a platform partner rather than directly through the Developer Console.[4]

What assets and information are required to register an RCS Agent?

Here is what you will need to have ready:

Brand name: your legal business name, consistent with your website and public records
Logo: 224×224 pixels, max 50KB, cropped as a circle — recognizable and consistent with your brand across channels
Hero/banner image: 1440×448 pixels, max 200KB
Brand color: hex code for your primary brand color
Agent description: up to 100 characters, displayed under your name in the messaging thread
Privacy policy URL: publicly accessible; must explicitly state phone numbers and consent are not shared with third parties for marketing
Terms of service URL: also publicly accessible
Business registration number or EIN: US businesses provide their Employer Identification Number
Brand contact email: a direct email for an authorized employee who will receive Google's mandatory authorization email
Use case description: specific explanation of what messages your agent will send and how recipients opted in — vague descriptions are a common cause of rejection
Opt-in and opt-out documentation: evidence of how customers consent and how STOP and HELP keywords are handled
Agent preview video: a recorded walkthrough of your messaging flow, opt-out flow, and secondary interactions

Who verifies RCS senders? How does the chain work?

RCS sender verification involves Google, carriers, and in some cases the aggregator. There are two types of launches:

Google-managed launches are handled by Google on behalf of the carrier. Google reviews your agent, sends a mandatory authorization email to your brand contact, and approves the launch. These typically take 1–3 business days for the Google review step if materials are complete and the brand contact responds promptly.

Carrier-managed launches require direct review by the individual carrier. Each carrier runs its own vetting process independently. This is where the overall timeline extends most significantly, particularly in the US.

What is the RCS onboarding process and how long does it take?

End to end, the RCS brand verification process in the US typically takes 8 to 16 weeks from submission to final carrier sign-off. The timeline breaks down roughly as follows:

Brand approval: 2–5 business days after submission of business details, website, and brand assets
Agent approval: 3–7 business days for review of agent name, logo, description, and welcome message
Use case / campaign review: 5–10 business days depending on message type and opt-in documentation
Carrier validation: the most variable step — US carrier reviews add additional days to several weeks, with each carrier reviewing independently

What causes verification to fail or be rejected?

Most rejections come down to preventable issues:

Inconsistent branding: brand name capitalized differently across website, agent profile, and application
Non-compliant privacy policy: must explicitly state SMS consent and phone numbers are not shared with third parties
Vague use case description: carriers want specifics, not "we plan to send marketing messages"
Missing or unclear opt-out flow: STOP handling must be documented and demonstrated
Poor-quality or incorrect-dimension assets: logos that don't meet the 224×224 spec will delay approval
No approved SMS program in place: RCS approval requires an existing 10DLC or shortcode registration as a prerequisite

What is the "verified checkmark" and what does it signal to customers?

The verified checkmark is a badge displayed in the RCS message thread confirming the sender has been authenticated. Customers see it alongside your brand name and logo at the top of the conversation. Research from Sinch found that nearly 80% of consumers say visual indicators like a logo and verification checkmark increase their trust in a message. In consumer marketing, where messages often arrive from unknown shortcodes, that trust signal has direct impact on whether someone opens, engages, or blocks.

Does verification need to be renewed or maintained?

Verification is submitted once per agent before the first launch and does not need to be resubmitted for ongoing sends on the same carrier networks. However, changes to your agent profile — updating your brand name, modifying your use case, or adding new carriers — may trigger a re-review. Branding inconsistencies between your agent profile and your public website are a common cause of compliance flags after launch.

Can Sureshot manage the verification process?

Yes. RCS onboarding through Sureshot includes managing the agent registration and verification submission on your behalf. We work with our aggregator partners to compile your brand assets, draft your use case documentation, coordinate the Google authorization step with your brand contact, and track carrier-level approvals.

Ready to start? The sooner you begin the verification process, the sooner you can send. Most teams underestimate the lead time required. If you're planning an RCS program in the next quarter, reach out now and we'll walk you through what's needed.

4. Compliance and Consent

RCS is a higher-trust channel than SMS, and that trust is maintained through stricter compliance standards. The verification process described in Section 4 gets you into the ecosystem. What keeps you in good standing once you're sending is how you handle consent, opt-outs, and record-keeping. Consumer messaging carries the highest compliance stakes in the business — TCPA violations can run $500–$1,500 per message, with no cap on total damages.

Nothing in this section is legal advice. Consult your legal counsel on how compliance requirements apply to your specific program and audience.

Do the same consent rules apply to RCS as SMS?

Yes. RCS compliance operates under the same legal framework as SMS in the United States. The Telephone Consumer Protection Act (TCPA), enforced by the FCC, governs consent requirements for A2P consumer messaging. The CTIA's Messaging Principles and Best Practices — while voluntary — are enforced by carriers and apply explicitly to SMS, MMS, and RCS.

Where RCS differs from SMS is in the additional layer of carrier-level enforcement built into the platform. Because RCS is a verified channel, carriers have direct visibility into how recipients interact with your messages — block rates, complaint rates, and engagement signals are monitored in real time. The compliance bar is the same on paper; the consequences of missing it are faster and more visible in practice.

What counts as valid opt-in consent for RCS?

Valid opt-in consent for RCS requires affirmative, explicit action from the recipient. A compliant opt-in must include:

A clear statement that the recipient is agreeing to receive messages from your business specifically
Your business name, so there is no ambiguity about who is sending
A description of the types of messages they will receive
Expected message frequency
Disclosure that message and data rates may apply
Instructions for opting out
A logged record of how and when consent was given — timestamp, source, and method

Enrolling a customer in multiple RCS programs from a single opt-in is prohibited. If your agent has multiple use cases, each must be clearly identified at the point of consent.[3]

What records do you need to keep, and why?

You need to be able to demonstrate for any contact in your program that you had consent, what it covered, when it was given, and how opt-out requests were handled. The TCPA's statute of limitations is four years. Retain records for at least that long:

Opt-in records: timestamp, source, and the exact language the customer agreed to
Message logs: what was sent, when, and to whom
Opt-out records: date a STOP request was received and confirmation no further messages were sent
Revocation documentation: under FCC rules effective April 2025, businesses must honor revocation requests via any reasonable method — not just STOP keywords — and process them within 10 business days

What are HELP and STOP requirements in RCS?

STOP and HELP keyword handling is required for all A2P RCS programs. When a recipient sends STOP, your agent must immediately cease non-essential messages and confirm the opt-out in a single reply that contains no marketing content. When a recipient sends HELP, your agent must reply with the program name and at least one contact method. Both responses must be built into your agent configuration before launch and are reviewed during carrier approval.

What happens if spam complaint rates get too high?

Carriers monitor block and complaint rates in real time. If your block rate exceeds roughly 3–5%, your agent is at risk of being throttled. Sustained high complaint rates can result in your agent being suspended or permanently removed from the RCS ecosystem. Because RCS is a verified channel, customers can see your brand name and logo before they even open a message — meaning disengaged customers can block you deliberately. Monitoring "User Block" events after every send is a basic operational practice.

Can you use purchased lists for RCS?

No. Full stop. Purchased lists are prohibited in the RCS ecosystem. Contacts on a purchased list have not provided affirmative consent to receive messages from your business, violating both TCPA requirements and carrier policies. Beyond the legal exposure, purchased lists generate the block rates that get agents suspended. This is not a gray area, and in consumer marketing, the exposure is particularly significant given TCPA's per-message damages structure.

How does RCS compliance differ from SMS compliance?

The legal requirements are the same. The enforcement mechanisms are different. SMS compliance violations are often discovered after the fact, through litigation or carrier complaints over time. RCS compliance violations are visible in real time — carriers can see exactly how recipients interact with your messages. A spike in block events after a send is immediately visible and can trigger action before you're even aware there is a problem.

What privacy policy disclosures are required?

Your privacy policy must be publicly accessible and must explicitly state that phone numbers and messaging consent are not shared with third parties for marketing purposes. This is a specific requirement for RCS agent registration. The policy must be linked in your agent profile and remain live throughout the life of your RCS program. It is also recommended to update your mobile terms of service and opt-in language to specifically reference RCS.

Are there geographic compliance differences?

Yes. In the US, TCPA and CTIA guidelines govern consent and opt-out requirements. In the EU, GDPR applies to any business processing personal data of EU residents. In California, CCPA introduces additional data rights. For global programs, each market may carry its own regulatory requirements. Your aggregator and legal counsel are both important resources for navigating market-specific requirements.

The bottom line on compliance: RCS rewards brands that treat consent as a genuine commitment rather than a legal checkbox. The channel's trust signals only work if the ecosystem is clean. Carriers enforce that actively. Build your consent practices as carefully as you build your message content.

5. RCS in a Consumer Marketing Stack

Understanding what RCS is and how it works is one thing. Knowing where it fits inside the customer engagement platforms consumer brands already run is another. This section covers how RCS connects to the tools you use today, what triggers can fire an RCS message, and how Sureshot approaches the integration layer.

Does RCS replace email or complement it?

RCS complements email and SMS. The three channels serve different purposes at different moments in the customer journey, and the strongest programs use all of them deliberately.

Email is the right channel for long-form content, detailed post-purchase sequences, newsletters, and anything that benefits from being searchable and reference-able. A customer can file, forward, and return to an email at their convenience.

RCS is the right channel for moments that benefit from immediacy, visual impact, and interactivity: an abandoned cart with a product image and a one-tap checkout button, a flash sale with a countdown and a "Shop Now" action, a loyalty reward notification with a carousel of redemption options. RCS messages are read at substantially higher rates than marketing emails and drive significantly higher click-through rates than SMS.

The practical model: email nurtures the relationship over time. SMS reaches everyone reliably. RCS converts at the high-value moments where a richer experience meaningfully outperforms a plain text message.

How does RCS integrate with platforms like Klaviyo, Braze, Iterable, or Salesforce Marketing Cloud?

RCS marketing automation works by connecting your customer engagement platform's campaign logic and customer data to an RCS-capable sending layer, typically through an aggregator or a platform like Sureshot that sits between them. Your platform remains the source of truth for audience segmentation, event triggers, journey logic, and campaign orchestration. RCS becomes an additional execution channel alongside email and SMS, triggered by the same events and data you already use.

In practice, your existing Klaviyo flow, Braze Canvas, Iterable journey, or SFMC Journey Builder can fire RCS messages using the same customer data, segment definitions, and behavioral triggers you already have in place. You are not building a separate RCS program from scratch. You are extending existing programs to use a richer delivery format at the moments where it performs best.

How does RCS connect to CRM data for personalization?

RCS message content can be personalized using any data your CRM or CDP holds on a customer: name, purchase history, browsing behavior, loyalty tier, last product viewed, location, and more. The data flow works the same way it does for personalized email — your platform pulls the relevant fields for each customer, populates them into the message template, and the RCS platform sends each recipient a message tailored to their record.

This is where RCS starts to look meaningfully different from SMS in a consumer context. A personalized RCS message can show the exact product a customer left in their cart, display their loyalty point balance in a rich card, surface a time-limited offer with a countdown, and include a one-tap action to complete the purchase, all without the customer leaving their messaging app.

What triggers can fire an RCS message?

RCS messages can be triggered by the same signals that trigger any other automated message in your stack. Common trigger types for consumer brands include:

Behavioral triggers: cart abandonment, product page visits, wishlist additions, browse abandonment
Purchase events: order confirmation, shipping update, delivery confirmation, return initiated
Time-based triggers: appointment reminders, subscription renewal dates, membership expiration
Loyalty and lifecycle events: points milestone reached, tier upgrade, win-back after lapse, birthday or anniversary
Promotional triggers: flash sale launch, limited-time offer, back-in-stock alert, price drop on a viewed item
Inactivity triggers: customer has not purchased in a defined window; re-engagement campaigns

What is the role of an aggregator in the sending chain?

An aggregator is the intermediary between your customer engagement platform and the carrier networks that deliver RCS messages. When a platform trigger fires an RCS message, the message payload travels from your platform to an aggregator (such as Twilio, Sinch, or Vonage), which performs a capability check on the recipient's device, routes the message to the appropriate carrier, handles fallback to SMS if RCS is unavailable, and passes delivery and engagement data back upstream.

Your team does not interact with the aggregator directly. What you see in your platform is a customer record updated with delivery status, read receipt data, and any button interactions — the same way email engagement data flows back into Klaviyo or Braze today.

How does Sureshot fit into the stack specifically?

Sureshot sits between your customer engagement platform and the RCS sending infrastructure, handling the data orchestration and integration work so your team configures campaigns in the tools they already know. That includes:

Validating phone numbers and confirming RCS capability per customer before sends
Passing customer and personalization data from your platform to the RCS layer at send time
Managing fallback logic so customers who cannot receive RCS get an SMS instead
Returning delivery, read, and interaction data back into your platform's customer records
Keeping opt-out suppression in sync so a STOP response in RCS is honored across your program

Sureshot integrates across consumer engagement platforms — Klaviyo, Braze, Iterable, Salesforce Marketing Cloud, and others — working with your existing stack rather than alongside a new one. On the sending side, Sureshot works with Twilio, Sinch, and Vonage, so your team doesn't manage those aggregator relationships directly.

Does RCS require custom development to implement?

How does fallback logic get configured technically?

Fallback is configured at the aggregator or platform level, not by your marketing team. When a message is triggered, the aggregator runs a real-time capability check. If RCS is available, the full rich message is delivered. If not, the aggregator automatically reformats and delivers the message as SMS using your existing sender. From your platform's perspective, both outcomes are logged back to the customer record — your journey logic does not need to branch for RCS vs. SMS.

The full sending chain at a glance:

Your platform: Klaviyo, Braze, Iterable, SFMC — holds customer data, segments, behavioral triggers, and journey logic
Sureshot: Data orchestration layer — validates data, passes customer and trigger signals to the RCS infrastructure, returns engagement data back
Aggregator: Twilio, Sinch, or Vonage — runs capability checks, routes messages to carriers, manages SMS fallback, passes delivery and engagement signals upstream
Carrier: AT&T, T-Mobile, Verizon, and others — delivers the message to the recipient's native messaging app
Customer: Receives a branded, verified RCS message (or SMS fallback) in their native messaging app — no download required

6. Consumer Marketing Use Cases

RCS is a consumer messaging channel. The brands deploying it today are retailers, hospitality companies, financial services providers, telecoms, airlines, and healthcare organizations — sending to customers, not to procurement managers. This section covers what RCS actually looks like in consumer marketing programs, with the trigger logic and use case framing that maps to how teams using Klaviyo, Braze, Iterable, and Salesforce Marketing Cloud actually build campaigns.

The core logic across all of these: use RCS at the moments where a rich, verified, interactive experience meaningfully outperforms a plain text message. Use SMS for everything that doesn't require that.

Abandoned cart and browse abandonment

Abandoned cart recovery with product carousel

Trigger: Customer adds to cart but does not complete purchase within a defined window

An RCS abandoned cart message can display the exact product left behind — high-resolution image, product name, price — with a one-tap "Complete Purchase" button and a suggested reply to ask a question or get help. The visual reminder of the specific item, combined with the frictionless action button, removes the barriers that cause cart abandonment in the first place. This is the use case where the difference between RCS and SMS is most immediately measurable.

Browse abandonment with product recommendations carousel

Trigger: Customer views multiple products without adding to cart

A carousel of the products a customer browsed — each card with an image, name, price, and "View Item" action — gives the customer a one-swipe path back to where they were. For customers who viewed multiple categories, the carousel can surface recommendations personalized to their browsing pattern using CDP data.

Appointment reminders and confirmations

Appointment reminder with confirm/reschedule actions

Trigger: Appointment is 24 hours and 1 hour away

Appointment no-shows are costly across retail, healthcare, hospitality, and service industries. An RCS reminder message includes the appointment date, time, location with a map action, and two suggested actions: Confirm and Reschedule. The one-tap confirmation eliminates the friction of replying with a keyword or calling to confirm. Businesses using RCS for appointment reminders consistently report meaningful reductions in no-show rates.

Loyalty and retention programs

Points milestone and reward notification

Trigger: Customer reaches a points threshold or earns a new reward

Loyalty programs suffer from low engagement because members forget they have rewards. An RCS notification showing a customer's current point balance, what they can redeem, and a carousel of redemption options — with one-tap actions to redeem or explore — is a dramatically more effective reminder than a generic "You have points!" SMS. The visual reward catalog turns a passive notification into an active shopping moment.

Tier upgrade announcement

Trigger: Customer achieves a new loyalty tier

A tier upgrade is one of the highest-sentiment moments in the customer relationship. An RCS message celebrating the upgrade with the new tier badge, a summary of new benefits, and a "Explore Your Benefits" action card makes the moment feel like an achievement rather than an automated notification. Customers who feel recognized at moments like this show measurably higher retention rates.

Order and shipping updates

Order confirmation with visual receipt

Trigger: Purchase completed

An RCS order confirmation can display product images, order details, an estimated delivery date, and a map or tracking action — all in one message from your verified brand profile. Customers expect this touchpoint immediately after purchase. Delivering it as a rich, branded experience rather than a plain text notification sets the tone for the post-purchase relationship.

Shipping and delivery updates with live tracking action

Trigger: Shipment status change in your logistics or OMS platform

Shipping update messages are among the highest-open-rate sends in consumer marketing because customers are actively looking for them. An RCS shipping update includes a package image, current status, estimated delivery window, and a "Track Package" action button. Delivered from a verified sender, these messages reinforce brand trust at a moment when customers are already engaged and attentive.

Promotional campaigns and flash sales

Flash sale launch with countdown and product carousel

Trigger: Sale begins; time-limited offer activated

Flash sales live and die by urgency and speed. An RCS flash sale message can include a countdown, a carousel of featured sale items with prices, and a "Shop Now" action — all delivered from a verified brand profile that customers recognize immediately. The interactive format means customers can browse and act without leaving their messaging app, which significantly reduces the friction between "I saw this" and "I bought this."

Personalized promotional offer based on purchase history

Trigger: Scheduled promotional campaign; audience segmented by purchase category

A promotional RCS message personalized to what a customer actually buys — showing products in their preferred category with a relevant offer — outperforms a generic broadcast because the content is immediately relevant. This is where CDP data integration earns its keep: the more accurately you can match offer to customer, the better the conversion rate and the lower the opt-out rate.

Transactional and operational messages

Payment failure or account alert with action button

Trigger: Failed payment, subscription renewal failure, or account flag

Transactional RCS messages for operational alerts benefit from the same trust signals as marketing messages: the customer sees your verified brand name and knows the message is legitimate. A payment failure alert with a one-tap "Update Payment" action, delivered from a verified sender, is more likely to be acted on immediately than the same message from an unknown shortcode — which many customers now dismiss as potential phishing.

Win-back and re-engagement

Lapsed customer re-engagement with personalized offer

Trigger: Customer has not purchased in 60, 90, or 120 days

Win-back campaigns are where RCS creates the most visible lift over SMS. A re-engagement message that shows products from a customer's previous purchase categories, acknowledges their lapse with a "We miss you" tone, and includes a personalized discount code with a one-tap action to shop is a fundamentally different experience than a plain text offer. The visual richness and verified brand identity signal that this is a meaningful communication from a brand the customer has a real relationship with, not a blast to a purchased list.

What use cases are not a good fit for RCS?

Where RCS is the wrong channel:

Long-form content: newsletters, detailed product guides, and content-heavy communications belong in email where customers can read at length and refer back
Universal reach at low cost: when you need to reach every customer regardless of device or carrier — transactional OTPs, critical alerts, high-volume broadcast to all subscribers — SMS remains the right tool
First-touch outreach to non-opted-in contacts: RCS requires explicit consent; any outreach to contacts who haven't opted in is non-compliant and will generate the block rates that damage your sender standing
High-frequency broadcast campaigns to your entire list: RCS is not a spray-and-pray channel. Message fatigue leads to blocks, and high block rates put your entire program at risk
Markets with limited RCS coverage: if a significant portion of your audience is in regions or on carriers without A2P RCS support, SMS fallback handles delivery — but RCS-specific content design loses its value

The framing that matters most: RCS is not a replacement for SMS or email. It is the upgrade you apply at the highest-value moments in your customer journeys — the moments where a richer, more interactive experience produces meaningfully better outcomes. Start by mapping your highest-stakes customer touchpoints, identify where SMS is underperforming, and those are your first RCS use cases.

7. Measurement and Performance

RCS gives you significantly more measurement surface than SMS and a fundamentally different kind of signal than email. Understanding what each metric actually means, how it compares to benchmarks, and how to connect it back to revenue is what separates teams that treat RCS as a novelty from teams that build it into their performance reporting.

What engagement data does RCS provide vs. SMS?

SMS tells you whether a message was delivered. That is essentially the extent of its native measurement. You can infer engagement by adding trackable links, but the baseline data is thin.

RCS provides a materially richer data set from the same send:

Delivery receipt: Confirmation the message reached the recipient's device
Read receipt: Confirmation the message was opened, not just delivered — a protocol-level signal, not image-based
Button interaction: Which suggested reply or action the customer tapped, and when — more specific than a link click
Rich card engagement: Whether the customer interacted with a carousel, scrolled through cards, or engaged with media
Reply content: For two-way conversational flows, the text of freeform customer replies
Block / opt-out events: When a customer blocks your agent or sends STOP — captured and usable for suppression

What is a read receipt in RCS, and how is it different from an email open?

An RCS read receipt confirms that a recipient opened the message in their native messaging app. It is a protocol-level signal — the messaging app sends a confirmation back to the sender when the message is opened, regardless of image loading behavior.

Email open tracking works by embedding a tiny invisible image in the message. That mechanism is increasingly unreliable: Apple Mail now pre-loads images by default, inflating open rates, while others block remote images entirely, suppressing them. RCS read receipts are not image-based and are structurally more trustworthy as a signal of genuine message exposure.

What are typical RCS engagement benchmarks?

Benchmarks vary by vertical, use case, and program maturity. Treat these as directional reference points, not guarantees.

Metric	RCS	SMS	Email
Open / read rate	70–95%	~98% delivered, ~80% read	20–42% (increasingly unreliable)
Click-through rate	15–30% (up to 51% in strong use cases)	4–7%	2–5%
Conversion rate	20–40% (60–80% in strong cases)	3–5%	<2%

The CTR and conversion figures depend heavily on relevance: a well-timed, personalized abandoned cart RCS message will dramatically outperform a generic promotional broadcast. Programs that personalize using purchase history and behavioral data consistently show results at the higher end of these ranges.

How does RCS engagement data flow back into a customer engagement platform?

RCS engagement data flows back into your platform through the integration layer between your sending infrastructure and your customer engagement stack. In Sureshot's implementation, delivery status, read receipts, and button interaction data are passed back to the customer's record as activity data — the same way email engagement events are logged in Klaviyo, Braze, or Iterable today.

This means an RCS button tap becomes a trackable event in the customer's activity history — usable for segment membership, journey logic, suppression, and campaign reporting. A customer who taps "Shop Now" in an RCS flash sale message can be automatically moved into a converted segment, suppressed from the next re-engagement send, or routed into a post-purchase flow — all triggered by the RCS interaction without manual intervention.

How do you attribute RCS touches to revenue?

RCS attribution follows the same logic as attribution for any other channel touchpoint. For consumer brands, the most direct measurement is conversion: did a customer who received and engaged with an RCS message make a purchase within a defined attribution window? Multi-touch attribution models can also be applied to understand RCS's role across more complex purchase journeys.

The data infrastructure that enables this: RCS engagement events logged to customer records in your platform, customer records synced to your CRM or analytics layer, and purchase data tied back to campaign attribution. If those three data flows are in place, RCS sits cleanly in your existing attribution framework without requiring a new measurement approach.

What metrics indicate a healthy RCS program vs. a troubled one?

Signals of a healthy program:

Read rates consistently above 70%
Button interaction rates above 15% on action-oriented sends
Block rates below 2%
Opt-out rates comparable to your SMS program
Engagement data flowing cleanly back into customer records in your platform.

Be on the lookout for:

Read rate trending down: Usually a content or timing problem. Review preview text, sender name display, and send timing relative to the trigger event.
Button CTR low despite high read rate: The message is being opened but the ask isn't landing. Review whether the suggested action matches what the customer actually wants to do at that moment.
Block rate above 3–5%: The most urgent warning signal. Common causes: messages reaching customers who haven't meaningfully opted in, frequency that feels intrusive, or content that doesn't match opt-in expectations. High block rates can trigger carrier throttling.
Fallback rate unexpectedly high: A segment of your list may be on carriers or devices without full RCS support. Review capability check data by segment.
No engagement data returning to platform: A technical signal. If RCS sends are going out but no read or interaction data is appearing in customer records, the data return path in the integration needs attention.

8. Getting Started

You understand what RCS is, how it fits your channel mix, and where it earns its place in a consumer marketing program. This section covers the practical side: what getting started actually requires, what to gather before you begin, and how long you should realistically expect the process to take.

What does it take to get an RCS program off the ground?

Standing up an RCS program has three distinct workstreams running in parallel: the brand verification and carrier approval process (covered in Section 4), the technical integration between your customer engagement platform and the RCS sending infrastructure, and the data readiness work that most teams underestimate.

That last one deserves attention. Before a meaningful RCS program can run, the contact data feeding it needs to be in good shape. Phone numbers need to be verified and confirmed as RCS-capable for each customer's device and carrier. Opt-in consent records need to be documented and accessible. Suppression lists need to be in sync. And fallback logic needs to know which customers get SMS when RCS isn't available. None of this is glamorous, but all of it determines whether your campaign logic performs the way you designed it to.

What do we need to have ready before we begin?

Your customer engagement platform configuration: Which platform you're running — Klaviyo, Braze, Iterable, Salesforce Marketing Cloud, or others — and how it's currently set up. Sureshot integrates across platforms, so this is about understanding your specific configuration, not determining eligibility.
Opt-in consent records: A clear picture of how customers have opted into mobile messaging, when consent was collected, and what language was used. RCS requires affirmative consent — this is the first thing to audit before anything else moves forward.
Brand assets: Logo (224×224px, max 50KB), hero image (1440×448px, max 200KB), brand color hex code, and your business name exactly as it should appear in the verified sender profile. These must match your public-facing brand — carriers check for consistency.
Live privacy policy and terms of service: Both must be publicly accessible. The privacy policy must explicitly state that phone numbers and messaging consent are not shared with third parties for marketing.
Business registration number or EIN: Required for the carrier compliance and Google registration process.
A specific use case description: What messages you will send, what triggers them, and how customers opted in. Vague descriptions are the most common cause of carrier rejection — the more specific, the better.
An existing approved SMS program: RCS approval in the US currently requires an existing 10DLC registration or shortcode as a prerequisite. The RCS program layers on top of your existing SMS sender rather than replacing it.

How long does RCS onboarding take end to end?

In the US, plan for 8 to 16 weeks from initial submission to your first live send. The timeline is driven almost entirely by carrier review, which is thorough, largely manual, and non-negotiable.

1. Data readiness and preparation

Audit your customer data, verify phone numbers, confirm RCS capability across your list, and ensure consent records are in order. Problems found here are much cheaper to fix than problems found mid-review.
Takes 1–2 weeks

2. Agent profile build and submission

Compile brand assets, finalize use case documentation, and submit your RCS agent profile through your aggregator. Your brand contact will receive a mandatory authorization email from Google that must be responded to promptly — delayed responses stall the entire process.
Takes 1–2 weeks to submit; Google review typically 1–3 business days once authorized

3. Carrier review

Each US carrier reviews your agent independently. AT&T, T-Mobile, and Verizon each run their own approval process. Complete, consistent materials reduce back-and-forth, but this step cannot be compressed beyond what carriers are willing to move.
6–12 weeks is typical

4. Integration configuration and testing

While carrier review runs, configure the integration between your platform and the RCS sending layer: trigger logic, personalization field mapping, fallback routing, opt-out sync, and the data return path. Run test sends on approved devices before go-live.
Parallel to carrier review; 2–3 weeks of active configuration

5. First live send

Once at least one carrier approves, you can begin sending to that carrier's subscribers. You do not need all carriers approved before going live. Most programs start with a limited pilot to validate delivery, engagement data flow, and fallback behavior before scaling.
Live within ~30 minutes of first carrier approval

The most common reason timelines extend: incomplete or inconsistent submission materials — branding that doesn't match your website, vague use case descriptions, a privacy policy missing the required language, or a brand contact who doesn't respond to Google's authorization email promptly. Getting these right before submission is the most effective way to compress the timeline.

Why work with a partner like Sureshot instead of going direct?

You could go direct. Aggregators like Twilio, Sinch, and Vonage have self-service onboarding paths, and the carrier submission process is technically open to anyone with an aggregator account. Some brands manage it themselves. The honest question is: what does a partner actually get you?

A few things. First, the data work. RCS onboarding surfaces data problems that most teams didn't know they had — unverified phone numbers, customers without confirmed RCS capability, consent records that don't hold up to carrier scrutiny, suppression lists that aren't in sync. A partner who handles data validation and enrichment as part of the process means those problems get caught and fixed before they delay your submission, not during carrier review when the timeline is already running.

Second, the submission quality. Most timeline extensions come from incomplete or inconsistent materials. Partners who have been through this process with multiple brands know what carriers flag and how to structure materials that move through review cleanly.

Third, the integration work. Getting RCS connected to Klaviyo, Braze, Iterable, or SFMC — trigger logic, personalization field mapping, fallback configuration, opt-out sync, engagement data flowing back into customer records — is real configuration work. A team learning it for the first time is learning on the job during a process that takes months. A partner who has built and maintained these integrations across multiple platforms gets it right faster and handles the edge cases you haven't thought of yet.

Sureshot integrates across consumer engagement platforms — Klaviyo, Braze, Iterable, Salesforce Marketing Cloud, and others — and works with Twilio, Sinch, and Vonage on the sending side. If you are planning an RCS program in the next quarter, the time to start that conversation is now. The onboarding timeline is fixed. Starting early is the only variable you control.

RCS is ready. Are you?

Talk to the Sureshot team about your platform, your audience, and what a pilot program could look like for your brand.

Get RCS-ready

Appendix: RCS Terminology Glossary

RCS comes with a dense alphabet soup of abbreviations, and they matter. Using the wrong acronym in a conversation with a carrier, aggregator, or platform partner signals that you're still getting up to speed. Use this glossary as a reference before your first vendor call. Every term here is relevant to running an RCS marketing program.

The Protocol

GSMA

RBM

RCS

Universal Profile

Legacy Messaging Standards

MMS

Multimedia Messaging Service. The extension of SMS that added basic media support: images, audio, and short video. MMS compresses media significantly and still lacks branding, interactivity, and read receipts. The difference between MMS and RCS is that MMS is a cellular protocol with significant size and quality constraints, while RCS delivers over IP with far higher fidelity and capability.

SMS

Message Types and Traffic

A2P

P2P

REGISTRATION AND COMPLIANCE

10DLC

TCR

The Sending Chain

Agent

Aggregator / CPaaS

Communications Platform as a Service. An aggregator is the intermediary between a brand and the carrier network. Aggregators like Twilio, Sinch, and Vonage handle brand registration, compliance, message routing, fallback logic, and throughput management. Most RCS programs run through an aggregator rather than connecting directly to carrier infrastructure. Sureshot works within this layer to connect your customer engagement platform to the aggregator sending chain.^[6]

CSP

MESSAGE COMPONENTS

Carousel

Chip / Suggested Reply / Suggested Action

Rich Card

DELIVERY AND OPERATIONS

Capability Check

Fallback

RCS Delivery

CUSTOMER ENGAGEMENT STACK

CDP

CRM

MAP / CEP

Marketing Automation Platform / Customer Engagement Platform. The platform used to build, automate, and manage customer communications. For consumer brands, this includes Klaviyo, Braze, Iterable, Salesforce Marketing Cloud, and similar tools. RCS marketing automation connects RCS messaging to these platform workflows so that sends can be triggered by behavioral data, purchase events, or lifecycle stage rather than managed manually.