iMessage vs SMS vs WhatsApp vs RCS for AI agents

The channel decision is the first architectural choice in a messaging agent and the hardest to reverse. It sets your reach, your regulatory burden, your unit economics and what the agent can express.

Here is the comparison, then what the 33 agents in this directory actually chose.

The comparison

	iMessage	SMS	RCS	WhatsApp
Reach	Apple devices, US-heavy	Every phone	Android, and now iPhone	Dominant outside the US
Official API	None	Yes, via carriers	Yes	Yes, Meta Cloud API
Gatekeeper	Apple, indirectly	Carriers, via 10DLC	Carriers and Google	Meta
Registration	None available	Brand + campaign, mandatory	Agent vetting	Template approval
Cost shape	Flat monthly, ~$5–289	Per message	Per message	Per message
Can you message first?	Depends on provider	Yes, with consent	Yes, with consent	Only from approved templates
Rich features	Best in class	None	Cards, carousels	Buttons, lists
In-thread payment	Apple Pay, exclusive	No	No	Some markets

What each one is actually good for

iMessage has the best interaction surface of any channel: tapbacks, typing indicators, read receipts, high-quality media, and Apple Pay in the thread, which remains exclusive to Apple-to-Apple conversations and is not available over RCS. It also has no official general API, so everything here runs on a managed provider or a self-hosted Mac. Choose it when the experience is the product and your users are American iPhone owners.

SMS reaches every phone ever made and has no rich features at all. In the United States it also has the heaviest compliance burden: brand and campaign registration under A2P 10DLC, which carriers have enforced by blocking unregistered traffic since December 2024. Choose it as a floor and a fallback rather than as a destination.

RCS is what SMS should have become: cards, carousels, read receipts. Apple now supports it. It carries its own vetting through the same registry that handles 10DLC. Choose it if you need rich messaging on Android without the WhatsApp tax.

WhatsApp is the default messenger across most of the world and has a real, documented API. Its constraint is initiation: businesses cannot message freely out of the blue, only from pre-approved templates in defined categories, with free-form replies confined to a window after the user writes first. Meta moved to per-message billing in July 2025 and has said business agent pricing moves to a token-based model from August 2026. Choose it for reach outside the US, and design around the initiation rule rather than against it.

What the products actually chose

This is where a directory can say something a vendor cannot. Across the 33 agents catalogued here:

Channel	Agents
iMessage	28
SMS	16
Email	5
Voice	4
Telegram	4
WhatsApp	4
RCS	1

Three things stand out.

iMessage dominates despite being the hardest channel to access. Twenty-eight of thirty-three, in the channel with no official API, grey-market tooling and platform risk. Builders are accepting real fragility to get the blue bubble, which tells you what they think the bubble is worth.

Eleven of thirty-three are single-channel, and nine of those are iMessage-only with no SMS fallback recorded. For a recipient on Android, those nine products do not work. That is not a degraded experience, it is no experience, and very few of them say so up front.

RCS has one adopter. One. In a directory of thirty-three, in the year Apple added support for it. Whatever the roadmap decks say, the products shipping today have not moved, and anyone planning a strategy around RCS ubiquity should weigh that against the announcements.

The practical answer

If you are building for US consumers and the interaction quality is the point, iMessage with SMS fallback, the fourteen-product pattern in this directory, is the pragmatic default, and you accept the platform risk knowingly.

If you are building outside the US, WhatsApp, and design for the initiation window from day one.

If you are building notifications rather than a relationship, SMS, and budget the registration time before you budget anything else.