In the United States, SMS is the default messaging channel. Americans have grown up with carrier-based text messaging, and most people expect that a "message" means an SMS.
This assumption is wrong for roughly 75% of the planet.
In Brazil, India, Israel, Nigeria, Germany, Spain, Italy, Indonesia — and most of the world — WhatsApp is the default messaging channel. Not SMS, not iMessage, not Telegram. WhatsApp. 2 billion active users. 100+ billion messages per day.
When your AI agent can only communicate via SMS and voice, it cannot reach most of the world's population on their preferred channel.
Why WhatsApp is different from SMS
The intuition is that WhatsApp and SMS are interchangeable — they're both "messaging." In practice, they're very different:
Delivery reliability: SMS delivery across international borders is inconsistent. Messages get lost, delayed, or blocked by carrier routing issues. WhatsApp uses internet infrastructure — delivery is far more reliable.
No per-message carrier cost: SMS has per-message charges that compound at scale. WhatsApp delivery is free (WhatsApp Business API has session and template fees, but no per-message carrier cost for delivery).
Rich media: WhatsApp natively supports images, documents, audio messages, and location. SMS supports none of these without MMS, which has its own reliability issues.
Read receipts: WhatsApp shows delivery and read confirmation. SMS shows nothing after the carrier reports delivery.
Session context: WhatsApp threads maintain context natively in the UI. A conversation with an agent looks like a conversation, not a series of disconnected texts from an unknown number.
The access problem
The catch with WhatsApp is access. Meta controls the WhatsApp Business API, and their approval process is designed to ensure quality:
Getting through this process takes 2–4 weeks, and the requirements can be opaque. For an agent developer, this is the same regulatory wall problem that exists with A2P SMS registration.
The right solution is the same: pre-handle the registration at the infrastructure layer so developers don't face the wall.
What WhatsApp-capable agents look like in practice
An agent with WhatsApp capability can:
Send rich content: Instead of a plain-text SMS follow-up, the agent can send a WhatsApp message with formatted text, an attached document, or a link preview.
Handle images: A real estate agent can send property photos. A support agent can receive a screenshot of an error. An e-commerce agent can send product images.
Maintain conversational context: WhatsApp threads naturally maintain the conversation history in the recipient's UI, so the conversation with the agent feels continuous even when there are gaps of hours or days.
Reach global users on their channel: A sales agent reaching out to leads in Europe, Latin America, or Southeast Asia can communicate on the channel those users actually check.
The unified number principle
The most powerful aspect of WhatsApp for agents is that it can share a number with voice and SMS. The same phone number that makes outbound calls, receives inbound SMS, and handles WhatsApp — all from a single agent identity.
When an agent calls a lead and they don't answer, the agent can follow up via WhatsApp if the lead is in a WhatsApp-dominant market. The recipient sees the same number that called them. The conversation thread picks up with context from the missed call.
This is what "channel agnosticism" means in practice: the agent communicates on the right channel for the recipient's context, without managing separate identities or separate systems for each channel.
The international agent
As AI agents handle more global workflows — international sales, cross-border customer support, multi-market operations — the communication infrastructure has to match the geographic reality.
An agent that can only SMS is an agent that works in the US and Canada. An agent that also handles WhatsApp can work almost anywhere.
The 2 billion users aren't a future consideration. They're the majority of the market right now.