For a decade the answer to 'what about Android customers' was a shrug and an SMS. RCS changed that. It brings read receipts, typing indicators, high-resolution media and longer messages to Android, and to iPhone-to-Android threads. If you last thought about this in 2023, your mental model is out of date.
What RCS actually gives you
SMS/MMS
- 160 characters per segment
- Compressed, low-quality media
- No delivery or read receipts
- No typing indicators
- Per-segment carrier cost
RCS
- Long messages without segmenting
- Full-resolution images and video
- Delivery and read receipts
- Typing indicators
- Verified sender branding for businesses
That last row is the one people miss. Business RCS supports a verified sender profile — your business name, your logo, and a verification badge in the thread. For a channel where the customer's first question is 'is this a scam', that is worth more than any of the rich-media features.
What RCS does not do
- It does not make the bubble blue. An RCS message from your business to an iPhone user still is not iMessage, and iPhone users read bubble colour as a signal whether or not that is fair.
- It is not universal. Coverage depends on carrier and device. Your fallback path to plain SMS does not go away.
- Business RCS has its own gate. Verified sender profiles require registration and approval, much like carrier registration for SMS.
- It does not simplify your stack. You now have three delivery paths to reason about instead of two.
Treat RCS as a third lane, not a replacement
The right architecture is unchanged: one send call, best-available channel. RCS slots in between iMessage and SMS as a better fallback than plain SMS. Several providers in our comparison now route all three automatically.
What this means for a small business
Practically: your Android customers now get a much better experience than they did, and you should stop writing your messages down to the lowest common denominator quite so hard. Full-resolution before-and-after photos work on both sides now. That is a genuine change for trades, salons and anyone whose work is visual.
Strategically: nothing changes. You still want a provider that routes automatically, you still want SMS fallback as the floor, and you still need consent regardless of which protocol carries the message. The rules follow the recipient, not the technology.
Do not build three sets of templates
The temptation is to write a rich version for iMessage, a rich version for RCS and a plain one for SMS. Three templates means three things to keep in sync and three ways to ship a typo. Write one message that degrades gracefully and let the channel add what it can.
Next step
Generate a tagged link for whatever you send next with the UTM builder, see what this looks like in your industry, or compare the services that can send it on the providers page.