Automatic RCS and SMS Fallback
The short answer
Automatic fallback ensures delivery regardless of device: iMessage first, then RCS, then SMS. One send, one thread, replies into your CRM. No separate Android campaign.
Key takeaways
- The ladder runs per message, per contact: iMessage (98% open), then RCS, then SMS.
- The ladder resolves at send time, stepping to RCS if iMessage is unavailable, then SMS if RCS is not supported.
- RCS is universal on paper, uneven in practice.
- Message text carries across all three channels.
- A2P registration applies to carrier routes, not iMessage.
- Fallback reaches everyone where iMessage cannot.
How a message falls back
What is automatic RCS and SMS fallback?
The ladder runs per message, per contact: iMessage (98% open), then RCS, then SMS. One campaign reaches your whole file from one line.
How does the fallback ladder work?
The ladder resolves at send time, stepping to RCS if iMessage is unavailable, then SMS if RCS is not supported. Resolution runs fresh on each send because people switch phones between campaigns.
- Every message records its channel on your CRM timeline and in per-channel reports. Read signals show on iMessage and RCS.
- Inbound replies include {from, content, channel, external_id}, enabling automations to branch on channel without extra lookups.
Reading how it works is not the same as watching it answer one of your own leads. The Blue Funnel Map does the second one.
See it on your own listWhat is the real state of RCS in 2026?
RCS is universal on paper, uneven in practice. Carriers support it, Android defaults to it, Apple added RCS in iOS 18. GSMA published Universal Profile 3.0 (March 2025) with encryption, editing, and Tapbacks.
- Apple and Google shipped encrypted RCS beta on May 11, 2026, requiring iOS 26.5, current Google Messages, and UP 3.0. Encrypted chats show a lock icon. Most live RCS traffic still runs 2.x features.
- RCS sits on rung two because feature sets vary by profile version. iMessage sits on rung one because it has no variance, so the ladder tries every message on iMessage first.
What carries over between channels and what does not?
Message text carries across all three channels. Read receipts and typing work on iMessage and RCS but not SMS. Tapbacks render on iMessage and on RCS where Universal Profile 3.0 is supported.
- Media and messages vary. Full on iMessage and RCS; 160 chars on SMS. iMessage photos full quality, RCS high-res, SMS compressed. Encryption: iMessage always, RCS on UP 3.0, SMS no. Links preview on iMessage and RCS.
- Everything on Blue Reacher's side carries over untouched: dedicated line number, contact record, sequence state, opt-out list, reporting, and webhook shape.
iMessage
- Bubble on an iPhone
- Blue
- Read receipts and typing
- Yes
- Media
- Full-quality photos and video
- Message length
- Sends whole
- Encryption
- End-to-end, always on
RCS
- Bubble on an iPhone
- Green
- Read receipts and typing
- Yes on supported versions
- Media
- High resolution
- Message length
- Sends whole
- Encryption
- End-to-end on the 2026 beta path (UP 3.0 plus MLS)
SMS and MMS
- Bubble on an iPhone
- Green
- Read receipts and typing
- No
- Media
- Compressed MMS, carrier size caps
- Message length
- Splits into 160-character SMS segments
- Encryption
- None
Does A2P registration apply to RCS and SMS fallback?
Does A2P registration apply to RCS and SMS fallback?
A2P registration applies to carrier routes, not iMessage. iMessage runs as data through Apple's service. Your volume never sits in a 10DLC registry. Blue Reacher requires no A2P registration.
- SMS and RCS require carrier registration. Traffic stepping down to SMS follows that route's registration rules. RCS adds brand and agent verification before going live.
- iMessage-only lines need no registration. Turn on lower rungs and white-glove activation sets them up with nothing for you to install.
How do teams use fallback across the funnel?
How do teams use fallback across the funnel?
Fallback reaches everyone where iMessage cannot. iMessage drives the outcomes: 98% open, 90% read in three minutes, under 3% spam-flagged. Fallback keeps non-iPhone contacts in the same campaign, thread, and report.
- Per-channel reporting shows how much pipeline came over blue bubbles versus lower rungs. That read sharpens per campaign and tells you whether to run iMessage-only or the full ladder on the next list.
- Speed-to-lead follow-up: a form fill deserves a text inside the first minute. When that lead is on Android, fallback sends inside that same minute instead of dropping them into an email queue where cold open rates now sit at 27.7%.
- Dead-list reactivation: old lists are a mix of device types with no reliable phone data attached. One send covers the whole file, and per-channel reporting tells you what your real iMessage share is before you plan the next push.
- Appointment confirmations and reminders, for teams that run a booking funnel: a reminder that only reaches part of the list is a reminder that loses meetings. Fallback closes the gap on the contacts iMessage cannot reach.
- No-show recovery and post-call follow-up: bottom-of-funnel messages carry live deal value, so every contact should get one regardless of what phone they carry.
- Onboarding, review requests, and referral activation: after the sale, support and retention messages need to land with every customer on the account, Android included.
How do you set up fallback rules?
How do you set up fallback rules?
Fallback setup involves three decisions. GoHighLevel users get it natively. Others connect via REST API at https://api.bluereacher.com/v1/messages. Lines pace at 50 opted-in / 30 cold new contacts a day; replies never metered.
- Mobile-validated leads cost $0.03/contact from 700M+ database. Pricing: $249/mo or $1,949/yr with unlimited iMessages paced at 50 opted-in / 30 cold new contacts a day, no per-message fees. Activation ($449) waived on annual billing.
- Ladder depth, set per line or per campaign: iMessage only, iMessage plus RCS, or the full ladder down to SMS.
- Fallback window: how long the send waits for iMessage delivery to confirm before stepping down. Short windows favor time-sensitive sends like reminders, longer windows keep more of the volume on iMessage.
- Channel variants: send one message body and let the platform strip what SMS cannot carry, or write a short SMS variant that swaps attached media for a link.
Frequently asked questions
Does every contact get an iMessage?
No. iMessage reaches iPhone-set numbers only. Every other valid mobile number gets RCS or SMS from the same line, inside the same campaign, with channel recorded. Validating your list for mobile numbers removes landlines and bad records so the ladder only runs on reachable phones.
Is RCS end-to-end encrypted in 2026?
RCS encryption shipped in beta May 11, 2026 on UP 3.0 and the MLS protocol. Requires iOS 26.5, current Google Messages, and carriers on both ends running UP 3.0. Encrypted chats show a lock icon and encryption defaults on where supported. Carrier rollout of 3.0 is still in progress.
Do I need A2P registration to run Blue Reacher?
No. A2P registration is a carrier requirement for carrier routes. iMessage is not carrier SMS, so it does not apply. Keep a line on iMessage only and there is nothing to register. Enable lower rungs and white-glove activation walks you through carrier registration during onboarding.
What happens when someone replies from an Android phone?
Replies from Android phones land in the same thread because the message went out from your dedicated line number. The reply hits your CRM and webhook with {from, content, channel, external_id}. The channel field tells you whether it came back over RCS or SMS so automations can respond differently.
Do read receipts and typing indicators work on the fallback channels?
Read receipts and typing work on iMessage and RCS, not SMS. That difference shows in reporting: campaigns that fell back heavily to SMS show fewer read signals even when reply volume holds. Delivery status and replies are recorded on every message regardless of channel.
Can I send iMessage only and turn fallback off?
Yes. Fallback depth is a setting on the line and campaign, so you can run iMessage only, iMessage plus RCS, or the full ladder. A clean setup is iMessage only on outbound lines, which keeps the channel pure and leaves nothing to register, with lower rungs on for operational sends.
Does fallback cost extra per message?
Fallback is included in your plan. Pricing is $249/mo or $1,949/yr (~$162.50/mo), unlimited iMessages paced at 50 opted-in / 30 cold new contacts a day, no per-message fees. RCS and SMS fallback comes with the line, so your cost does not move with device mix.
How do I know which channel each message went out on?
Every message records its channel at send time, visible on the contact timeline and rolled up in campaign reports by channel. Inbound replies carry the channel field in the webhook payload, giving you a real read: what share of your list is iMessage-reachable, and how reply rates differ by channel.
Reach the whole list, not the iPhone half of it
The Android third of your list is paid-for pipeline too. Send iMessage first, fall back to RCS and SMS automatically, keep every reply in one thread. $249 per line per month, unlimited iMessages paced at 50 opted-in / 30 cold new conversations per line per day, white-glove activation waived on annual. Book your Blue Funnel Map and ask us to open it by text.