The choice is mostly geography: SMS is near-universal in the US and needs no agreement from the recipient’s app; WhatsApp dominates much of Europe, Latin America and Asia and carries richer messages. The real differences are the approval regimes — carrier registration on one side, template approval on the other — and each shapes what you can build.
Follow the customer, not the feature list
Whichever your customers already use daily wins, and it is not close. A rich, well-designed WhatsApp experience is worthless to someone who does not have WhatsApp, and an SMS is ignorable in a market where nobody uses SMS for anything but verification codes.
If you serve multiple regions the answer is both, with one messaging layer behind them. If you serve one, this section is the entire decision.
Side by side
| SMS | ||
|---|---|---|
| Reach | Universal, no app needed | Only where adopted |
| Message richness | Text, plus MMS | Media, buttons, lists |
| Outbound constraint | Carrier registration | Template approval |
| Improvised outbound | Allowed once registered | Not allowed |
| Conversation window | Not a concept | Session rules apply |
| Cost per message | Per segment | Per conversation |
| Failure mode | Silent filtering | Explicit rejection |
That last row is the most important operational difference. WhatsApp usually tells you no. Carriers often just do not deliver.
The SMS failure that wastes days
Unregistered application traffic gets filtered, not rejected.
In the US, messages sent from an application to a person must be registered against a brand and a campaign. If you skip that or your registration is incomplete, carriers filter the traffic. Your provider reports a successful send. The message does not arrive. Nothing anywhere says why.
This produces days of debugging in the wrong place — people check their code, their numbers, their formatting, and the answer is a registration form. If business SMS is not arriving and your logs look clean, check registration status before anything else.
It is the same shape as email deliverability: the send succeeded, the delivery did not, and the two are different systems reporting separately.
The template constraint shapes your product
On WhatsApp, anything you send outside an open conversation window must use a pre-approved template. Approval takes time and templates can be rejected.
The consequence is architectural, not administrative: you cannot improvise outbound. Every proactive message your product might ever send has to be conceived, written, submitted, and approved in advance. An AI agent that composes a novel message and sends it cold does not fit the model at all.
Design around it by treating templates as a schema. Enumerate the proactive messages your product sends, submit them, and use variables for the parts that change. Anything genuinely conversational happens inside an open window, where you can write freely.
Get this wrong and you discover it late, when a feature is built and cannot ship.
Cost shapes differ
SMS charges per message segment, and a long message is several segments — including when a single emoji flips the whole message to a different encoding and halves the segment length. Watch that if you send anything near a boundary.
WhatsApp charges per conversation window rather than per message, so a back-and-forth exchange costs differently from a single notification. That usually favours genuinely conversational use and penalises one-way blasting, which is deliberate.
What I would build
- One messaging layer, channel adapters underneath. Your product should ask to send a message; the adapter decides how.
- Register early. Registration takes longer than you expect and blocks nothing else in the meantime.
- Enumerate your templates up front if WhatsApp is in scope. This is a design exercise, not paperwork.
- Treat delivery as separate from sending. Log both. A successful send is not a delivered message on either channel.
- Handle opt-outs properly and centrally. One suppression list across channels, honoured everywhere.
- Check the rules where you operate. Consent, quiet hours, and identification requirements vary by country and state, and they are not optional.
FAQ
SMS or WhatsApp?
Follow your customers. SMS is universal in the US; WhatsApp dominates much of Europe, Latin America and Asia and carries richer messages.
What is template approval?
Anything sent outside an open conversation window must use a pre-approved template. It means you cannot improvise outbound.
Why do my business SMS not arrive?
Usually unregistered A2P traffic, which carriers filter rather than reject — so the send reports success and nothing arrives.
Can I use one system for both?
Yes: one messaging layer, channel adapters. Keep the constraint sets separate.
Related: Resend vs Mailgun, AI voice agents for follow-up, and automation services.