Blue bubble or green: what actually changes for an agent
The difference between iMessage and SMS fallback is not cosmetic. It changes what your agent can do, what it costs and whether it works at all.
The colour of the bubble is treated as a social signal. For anyone building an agent it is a technical one, and the gap between the two states is much larger than most product pages admit.
What you get in blue
An iMessage thread gives an agent capabilities that have no SMS equivalent:
- Tapbacks. Reactions that can be sent and read. At least one agent in this directory treats an emoji reaction as an input, which is a genuinely native interaction pattern.
- Typing indicators and read receipts. Both readable and, through several providers, sendable. This is most of what makes an agent feel present rather than automated.
- High-quality media. Photos, video and voice notes without carrier degradation.
- Message effects and formatting.
- Apple Pay in the thread. And this one is worth stating plainly: in-thread Apple Pay is exclusive to Apple-to-Apple conversations. It is not available over RCS or any cross-platform path. If your agent's job ends in a payment, that is the difference between finishing in the thread and sending someone to a browser.
- Group threads, which several providers expose programmatically.
What you get in green
Text. Up to 160 characters per segment, no reactions, no typing indicator, no read receipt, no payment, and media that arrives as degraded MMS at extra cost.
You also inherit the entire US regulatory apparatus: brand and campaign registration under A2P 10DLC, carrier filtering, and per-message fees. See A2P 10DLC registration.
The three states people forget
Most product copy implies two states. There are three.
- Blue. Your agent and the recipient are both on Apple, everything works.
- Green with fallback. The recipient is on Android, your provider falls back to SMS, and the agent works with a fraction of its capabilities. Your feature set silently shrinks. If your onboarding depends on a tapback or your checkout depends on Apple Pay, it breaks here and the user has no idea why.
- Nothing. Your provider has no fallback, the recipient is on Android, and the message does not arrive.
State three is more common than it should be. Of the 33 agents catalogued here, 9 are iMessage-only with no SMS fallback recorded. For roughly half the US phone market and the great majority of phones elsewhere, those products do not work. Fourteen pair iMessage with SMS so a message still lands. One supports RCS.
What this means for design
Do not build a critical path through a blue-only feature. Apple Pay, tapback input and read receipts are enhancements. If the agent cannot complete its job without one, it cannot complete its job for a large share of users.
Check what fallback costs. It is not always included. At least one provider prices SMS and RCS fallback as a $15-a-month add-on, so the plan you costed may not include the thing that makes the product work on Android.
Say which you support. Almost nobody does. One of the clearest product pages in this directory states it directly, blue bubbles on iPhone and RCS or SMS on Android, and it is conspicuous precisely because it is rare. A person deciding whether to text your agent is entitled to know whether it will work on their phone.
Watch RCS, but do not plan on it. It restores cards, carousels and read receipts, and Apple now supports it. Adoption among shipping agents is one product out of thirty-three. It is the right long-term answer and it is not yet a plan you can build on.