What is RCS SMS fallback?

RCS SMS fallback is the process of delivering a message as SMS when the recipient cannot receive the RCS version. It helps businesses reach customers whose device, carrier, messaging app, network, or market does not support the required RCS capability.

Fallback is important because RCS availability varies by country, carrier, operating system, device, and customer configuration.

How does RCS fallback work?

Before sending or during message delivery, the business messaging platform may determine whether the recipient is eligible for RCS. If RCS is unavailable, the platform can send a plain-text SMS version instead.

A typical fallback workflow looks like this:

The business creates an RCS message.
The recipient’s capability is checked.
The RCS version is sent when supported.
The SMS version is sent when RCS is unavailable.
Delivery and fallback outcomes are recorded.
The business analyses both versions.

For example, a retailer can send a product carousel to RCS-capable customers. A customer without RCS may receive an SMS containing the product name, offer, and a shortened link.

Helo.ai’s Apple RCS messaging guide discusses how device and platform support affect the RCS experience and why fallback remains important.

Why does fallback matter?

Fallback reduces the risk that important communication will fail completely. It is particularly useful for:

Delivery notifications
Appointment reminders
Banking alerts
Payment reminders
Travel updates
Authentication messages
Emergency notifications
Time-sensitive service information

Fallback does not preserve the full RCS experience. Rich cards, carousels, branding, suggested replies, and interactive buttons may be converted into plain text or a link.

RCS fallback versus SMS-only messaging

An SMS-only campaign sends the same basic format to everyone. An RCS campaign with fallback attempts to provide a richer experience to eligible recipients while still offering a simpler version to others.

RCS with fallback	SMS-only campaign
Rich experience where available	Same plain format for everyone
Can include branding and buttons	Limited interactivity
Requires capability logic	Simpler implementation
May provide richer analytics	Usually fewer engagement signals
Needs two content versions	Requires one primary version

Designing a good fallback message

A fallback SMS should be understandable on its own. Do not write:

Your RCS card could not be displayed. Click here.

Instead, write:

Helo.ai: Your appointment is confirmed for 4:00 PM on 18 July. Manage your appointment: https://example.com/manage

The fallback should include:

Brand identification
Main information
A clear action
A short and trustworthy URL
Customer-support information where relevant

Limitations

Fallback depends on the partner, carrier, market, message type, customer consent, and current delivery rules. Businesses should also understand whether fallback creates a separate message charge and how delivery reporting distinguishes RCS from SMS.

A fallback mechanism is not a guarantee of delivery. The customer may still have no coverage, an inactive number, blocked messages, or an unreachable device.

Frequently asked questions

Does every RCS message automatically fall back to SMS?
Not always. Fallback behaviour depends on the RCS partner, campaign configuration, message type, carrier, and market.

Does SMS fallback include the logo and buttons?
Usually not. It generally becomes a plain-text message with a link or instruction.

Should businesses always enable fallback?
For important transactional communication, fallback may improve reach. For highly visual campaigns, businesses may choose to target only RCS-capable recipients.