RCS vs SMS for marketing: reach, cost and results

RCS does a lot of things SMS can't. It shows a verified brand name and logo, supports carousels and suggested-reply buttons, sends high-resolution images and returns read receipts. If you run an SMS program, you have probably been asked whether to add it.

Our answer is to add it only if you already have a working SMS program and a reason that SMS can't cover. RCS does not reach every phone. Every serious RCS deployment falls back to SMS. The fallback is where a lot of the real cost and compliance work sits. This post covers reach, features, delivery and pricing so you can decide with numbers instead of demo videos.

We make Ready, which sends SMS and iMessage (our "blue line"). We don't sell RCS today. That's the bias you should account for, and it's also why we're direct about where RCS helps.

What RCS and SMS actually are

SMS is the 160-character text protocol every mobile phone supports. In the US, business SMS from a regular 10-digit number runs over A2P 10DLC. You register a brand and a campaign with the carriers, and unregistered traffic gets filtered. Our 10DLC explainer covers the mechanics.

RCS (Rich Communication Services) is the IP-based upgrade to SMS that lives in the phone's default messaging app. RCS Business Messaging (RBM) is the branded, business-to-consumer version. It requires a separately verified sender "agent," which is a different approval track from 10DLC.

The practical difference: SMS is a lowest-common-denominator channel that always arrives. RCS is a richer channel that arrives only when the recipient's phone, carrier and settings all support it.

Reach: who actually gets the rich version

This is the part demo decks skip.

• Android: Most current Android phones on major US carriers support RCS through Google Messages. Some users have it off, use a different messaging app, or are on a carrier or plan where it doesn't work.
• iPhone: Apple added RCS support in iOS 18. Business messaging to iPhones depends on carrier support and is still rolling out unevenly. Treat iPhone RCS reach as partial and growing, not universal. We cover the details in RCS finally shipped on iPhone but won't replace your SMS program in 2026.
• Everyone else: Older phones, phones with RCS disabled, and numbers on unsupported networks get the SMS fallback, or nothing if you didn't set one up.

We're not going to invent a percentage. Your RCS-capable share depends on your list's device mix, and that varies a lot between, say, a teen-apparel brand and a regional HVAC company. Before you budget for RCS, ask your provider for a capability check on a sample of your real list. A meaningful share of any list will still get plain SMS, and you have to design for that share.

Features: what RCS adds for marketing

RCS features that tend to matter for marketing:

1. Branded sender. Recipients see your name and logo instead of an unfamiliar number. That trust signal is the main reason teams try RCS.
2. Suggested replies and buttons. "Book now" or "Track order" taps cut friction compared with "reply YES."
3. Carousels. Several products in one message, which suits ecommerce catalogs.
4. Read receipts and engagement data. You see opens, not just deliveries.

None of these fix a weak offer or a cold list. An opted-in list with a relevant message usually performs well on plain SMS. RCS can raise engagement on top of that. It won't save a program that isn't already working.

Cost: how the two are priced

SMS is billed per segment. On Ready Standard it's $0.0075 per segment plus a $0.0045 carrier fee. Received replies are billed the same way. That all-in figure excludes the optional compliance surcharge: TCPA/DNC scrubbing and landline validation are $0.003 extra per segment each when switched on, and both are off by default. Raw CPaaS APIs such as Twilio (about $0.0083 per segment) are lower per segment. What Ready adds is registration handled in-app, a two-way inbox and compliance tooling. Our SMS marketing pricing buyer's guide lays out the full comparison.

RCS pricing has no single public rate card. Carriers and providers typically bill by message type, with distinct prices for basic text-only messages, single rich messages and conversational sessions. The prices vary by provider and carrier. Get written quotes for each message type you plan to send, plus the price of the SMS fallback, because you'll pay that too.

Worked example: a 5,000-contact promo on SMS

Assumptions: 5,000 opted-in contacts, Ready Standard, no compliance surcharge switched on.

• 160-character plain-text promo = 1 segment. Cost: 5,000 × $0.0075 = $38, plus 5,000 × $0.0045 in carrier fees.
• 175-character promo, no emoji = 2 segments (153 characters per multipart segment). Cost: 10,000 segments × $0.0075 = $75, plus 10,000 × $0.0045.
• The same 175 characters with one emoji = 3 unicode segments (67 characters per multipart segment). Cost: 15,000 segments × $0.0075 = $113, plus 15,000 × $0.0045.

The emoji alone adds 50% over the plain 175-character version. If you're testing RCS against SMS, compare against a tightly written SMS, not a bloated one.

Pricing the fallback into an RCS test

Suppose a share of your list turns out not to be RCS-capable. Every one of those contacts gets SMS at your normal SMS rate. Your blended cost is:

(RCS-capable contacts × RCS price per message type) + (non-capable contacts × SMS segments × SMS rate)

Run that formula with your provider's real quotes and your real capability check. It's the only honest way to compare.

Delivery and fallback: why SMS stays underneath

Fallback is the part that decides whether an RCS program works. When an RCS message can't be delivered, the provider resends it as SMS. Several things follow from that:

• Your fallback number must be 10DLC-registered. Unregistered SMS gets carrier-filtered, so a failed RCS message falling back to an unregistered number can simply vanish. Registration on Ready has no setup fee. You pay the first month ($25) at submit, then $25/mo for registration and $2 per number. Most approvals take 2 to 7 days.
• Write two versions of every message. A carousel with three buttons has to collapse into a sensible 160-character text with a link. If you don't write the fallback copy, someone's template engine will write it for you.
• Compliance applies to both channels. STOP handling, quiet hours and consent apply whether the message arrives rich or plain. On Ready's SMS side, STOP is honored automatically and propagates across campaigns. Sends are held outside permitted local hours, and litigator/DNC scrubbing is available. Those features reduce risk; they don't make you lawsuit-proof, and compliance stays the sender's responsibility. Campaigns, drip campaigns and automations wait up to 24 hours for the window; a one-to-one or API text is held only if the window opens within 6 hours, otherwise it is refused and must be resent; a one-to-one reply to someone who texted you in the last 24 hours goes out at any hour.
• Throughput limits still apply. Fallback SMS is subject to the same 10DLC caps as any other SMS. A fresh, unvetted campaign often runs at roughly 1 to 4 segments per second. A large RCS send that falls back heavily can queue up behind those limits.

For more on designing the backup path, see RCS business messaging: benefits, limits and how to back up with SMS.

Where iMessage fits

If the appeal of RCS is mostly the branded look on iPhones, there's a separate route. Ready's blue line sends texts as iMessage, so they show up blue with your business name and photo.

• Price: $99 a month per line, plus 6 cents a segment sent or received. Reactions are free.
• Registration: None needed for the blue line itself.
• Android: Texts to Android phones go from your regular number. If you already had a number they bill at the regular SMS price; if the blue line came with its green number, they bill at 6 cents a segment once you register or send through GoHighLevel.
• Limits:
• Each line can start up to 50 new conversations a day.
• It can send up to 2 texts to a person until they reply.
• Photos only go out after a reply.
• Campaigns: Campaigns and drip campaigns send from regular numbers, not the blue line.

The blue line is a tool for one-to-one sales and follow-up conversations, not bulk marketing. If your goal is a richer first impression in sales conversations, it may suit you better than RCS. If you want carousels in a promo to your whole list, it isn't the right tool. The iMessage and RCS for business FAQ compares the two in more depth.

When adding RCS is worth it

Add RCS if:

• You already run a registered, healthy SMS program with clean opt-ins.
• Your list skews toward RCS-capable devices, which you've confirmed with a capability check.
• Your messages benefit from visuals or buttons: product catalogs, appointment pickers, order tracking.
• You have the capacity to write and QA two versions of every message.

Stay on SMS for now if:

• Your SMS program isn't registered yet or isn't producing results.
• Most of your messages are short, transactional or conversational. Reminders, confirmations and replies don't need a carousel.
• You can't get clear per-message-type RCS pricing from a provider.

The practical takeaway

RCS is a layer you add on top of SMS. It doesn't replace SMS. It reaches some of your list with a richer, branded message, and everyone else gets SMS, so the SMS program underneath has to be registered, compliant and well written first.

If that foundation isn't in place yet, start there. You can sign up for Ready, register your brand and campaign in-app, and use the first 20 free one-to-one texts to check your copy before you register. Once SMS is working, test RCS on a segment of your list, price in the fallback, and judge it on the blended numbers.