RCS vs iMessage
TL;DR
RCS and iMessage split along hardware lines. Neither covers a full US list alone, which is why a real strategy runs both with fallback. But which to build around depends on timeline and buyers. Android-heavy and weeks to spare: RCS first. iPhone-majority and month of launch: iMessage first with RCS fallback.
On this page
- 01RCS vs iMessage: the short version
- 02Which one reaches more of your list?
- 03What does verification actually cost you in time?
- 04Branding: verified logo, or a thread that reads like a person
- 05Do read receipts work on both?
- 06What carries over when a message falls back?
- 07Where RCS is the better build
- 08Which should a B2B business build outreach on?
- 09How Blue Reacher runs the chain
- 10Frequently asked questions
RCS vs iMessage: the short version
RCS and iMessage differ on four things that matter: reach, approval, message format, and SMS fallback. Everything else is detail.
The headline gap is registration. RCS requires brand verification and launch approval before any send; iMessage requires no A2P 10DLC registration. TCPA applies to both equally.
| iMessage | RCS | |
|---|---|---|
| Reaches | Apple devices | Android, plus iPhone on iOS 18 or later where the carrier supports it |
| Carrier support required | No | Yes. AT&T, Verizon, T-Mobile and UScellular support RCS in the US |
| Sender registration | No A2P registration required | Brand verification plus a carrier launch approval, and A2P 10DLC on the SMS fallback leg |
| Wait before first send | No carrier or A2P review to clear | US brand approvals commonly quoted at eight to sixteen weeks to final carrier sign-off |
| How it looks | Blue bubble from a dedicated line | Verified brand name, logo and badge |
| Read receipts | Yes, recipient controlled | Yes, delivery and read |
| Rich content | Photos, links, attachments, tapbacks | Rich cards, carousels, suggested replies, tappable buttons |
| End-to-end encryption | Yes | Person-to-person only, in beta from iOS 26.5 and current Google Messages. Business traffic sits outside it |
Which one reaches more of your list?
iOS holds 58.35% of US mobile OS share, Android 41.62%. No single channel covers your whole list.
RCS reach depends on carrier support and app setting. AT&T, Verizon, T-Mobile and UScellular all support it. iPhones on iOS 18+ can receive RCS, same carrier condition.
iMessage reach carries no carrier dependency. If the contact is signed into iMessage, the message arrives.
What does verification actually cost you in time?
RCS requires a verified sender. You register the legal entity, submit brand name, website and logo, and get the use case reviewed. That review earns the verified badge.
Launch approval moves timelines. Twilio quotes 1-3 weeks; OneSignal says brand approvals run 8-16 weeks from submission to final sign-off in the US. Inconsistent details cause rejections.
You register twice for one program. Verified sender covers RCS; SMS fallback needs A2P 10DLC through The Campaign Registry, a separate approval.
- iMessage sits outside that queue. A2P 10DLC governs US carrier SMS routes, not iMessage, so no A2P registration is required. TCPA governs both channels equally.
Branding: verified logo, or a thread that reads like a person
Branding works opposite ways on these channels. RCS gives a verified profile with logo, badge and rich cards; recipient knows it's a company.
That's an asset when the recipient knows you. Order confirmations, reminders, shipping updates and payment links land better with logo proof.
Verified branding announces as marketing before the first word. iMessage looks like one person, driving 2-3x reply rate versus email's 27.7% open rate.
Do read receipts work on both?
Read receipts exist on both channels. RCS carries delivery receipts, read receipts and typing indicators, and surfaces signals back as campaign reporting.
iMessage read receipts sit with the recipient, who controls the setting. Delivery confirmation always comes through; read confirmation comes when the recipient allows it.
For B2B senders, neither channel leaves you blind. Underlying behavior matters more: 98% open, 90% read in three minutes, under 3% flagged as spam against 85% for email.
What carries over when a message falls back?
Fallback strips a message down to what the next channel can carry. Plain text and links survive; images only with MMS; rich cards and buttons vanish and need URL rewrites.
Branding doesn't carry over. Verified profile, logo and badge are RCS features; fallback arrives from a plain number with no trust markers.
Messages built on carousels or buttons become confusing on fallback. You can't pick which version recipients see. SMS version must make sense standalone.
| Element | Survives fallback? |
|---|---|
| Plain text | Yes |
| Links | Yes, as raw URLs |
| Images | Only with MMS fallback configured |
| Rich cards and carousels | No, stripped |
| Tappable buttons | No, must be rewritten as URLs |
| Brand name, logo, verified badge | No |
| Read receipts and RCS engagement data | No |
Where RCS is the better build
RCS wins on specific jobs: known brands, high volume, transactional messages, value from rich formatting not conversation.
Order tracking, rebooking, appointment management, payment reminders and Android-heavy lists belong on RCS. Branded cards work, suggested replies handle routing, and verification is worth it for long-term programs.
That fits a branded, transactional program that is already approved: moving to conversational channels costs the formatting. Large CPaaS providers carry RCS and handle onboarding.
Which should a B2B business build outreach on?
Match channel to buyer. US B2B skews Apple: iOS 58.35%, iPhone income $85k versus Android. Don't build primary channel around smaller, lower-value half for formatting options.
iMessage has no carrier review. RCS can take a quarter in review before anyone reads a word; cold outbound tested late yields no learnings.
Format is the third argument. Outbound is smaller half of money; bigger half is converting traffic already paid for. Conversation performs better in person-like thread.
- Fallback resolves the rest. Android contacts still get reached, just second. Coverage is the chain's job; channel choice is the buyer's job.
How Blue Reacher runs the chain
Blue Reacher runs iMessage first, RCS second, SMS last from a dedicated line. $249 per line per month or $1,949 per year; unlimited iMessages at 50 opted-in / 30 cold daily; no A2P registration required.
White-glove activation is normally $449 and is waived on annual billing. Mobile-validated B2B leads run $0.03 per contact from 700 million records, billed monthly with the line.
Frequently asked questions
Does RCS work on iPhone in 2026?
Yes. RCS landed in Messages in September 2024 alongside iMessage. Delivery depends on carrier support; AT&T, Verizon, T-Mobile and UScellular all support it in the US. Users can disable RCS in settings, so reach is never guaranteed by the device alone.
Is RCS end-to-end encrypted?
Person-to-person RCS is encrypted; business RCS is not. GSMA UP 3.0 (March 2025) defines encryption using MLS. Apple rolling out beta with iOS 26.5. App-to-person traffic sits outside it. iMessage always encrypted.
Does RCS require A2P 10DLC registration?
Yes for SMS fallback leg, and RCS adds its own approval. RCS needs brand verification and launch approval; 10DLC needs A2P registration through Campaign Registry. That's two reviews for one program. iMessage sits outside and requires no A2P.
How long does RCS brand verification take?
Verification and launch run on two clocks. Twilio quotes 1-3 weeks. For US, OneSignal says 8-16 weeks from submission to final sign-off. Inconsistent details cause rejections.
Do read receipts work on both RCS and iMessage?
Yes, both carry different controls. RCS delivers receipts and typing indicators, with Business reporting signals back to sender. iMessage read receipts are user-controlled in Messages settings. Delivery confirmation comes through on iMessage regardless.
What happens to an RCS message when the recipient can't receive it?
Fallback drops to SMS or MMS and strips what can't carry. Plain text and URLs survive; images only with MMS. Rich cards, buttons and branding disappear. Campaigns with buttons need rewritten SMS versions.
Should a B2B company use RCS or iMessage for cold outreach?
iMessage is stronger for cold B2B with RCS/SMS fallback. iOS 58.35%, iPhone income $85k; iMessage has no carrier review vs RCS 8-16 weeks; blue bubble reads like person vs brand card that reads like an ad.
Can one platform send both iMessage and RCS?
Yes. A single platform can run both, and a chain is how it should be built. Blue Reacher sends iMessage first with RCS and SMS fallback so Android gets reached. Primary channel determines replies; fallback chain ensures coverage.
Does RCS give better deliverability than SMS?
RCS deliverability tracks your carrier standing, same as SMS. Real gain is presentation: verified branding and rich media. Texting runs 98% open, 90% read in three minutes, under 3% spam vs 85% email.
Keep reading
More on channel comparisons
Apple Messages for Business Can Now Text First. It Still Cannot Prospect
For years the rule was simple: on Apple Messages for Business, the customer texts first. Apple has added invitations, so an approved brand can now open the thread. Our own site had the old rule on more than a dozen pages until today. Here is what changed and why a sales team still cannot prospect there.
FaceTime Audio Calling from Your iMessage Line
FaceTime audio lets your sales team place calls from the same dedicated line that sends iMessages, so prospects answer a familiar number instead of a dialer, and the conversation stays in one thread from text to call.
RCS vs SMS: What It Adds, What It Costs, When to Switch
RCS gives SMS a visual upgrade with logo, verification, and rich cards. But it stacks registrations instead of replacing them, carries higher carrier fees on three of four major networks, and still needs SMS fallback through A2P 10DLC. Here's when it pays.
Put this on your pipeline
Blue Reacher runs outbound iMessage for B2B sales teams, from your CRM, with setup handled for you.
Book a demo