Key Takeaways
A partner in São Paulo stops emailing your support team. Instead, they message their account manager's personal WhatsApp, because that's how every business they work with talks to them. Meanwhile, your operations lead asks whether you can text customers during the next outage. Both requests land on your desk in the same week.
They sound like the same question, “should we support messaging?”, but they aren't. WhatsApp and SMS have different rules, different costs and different customers. Pick the wrong one, and you'll run a channel nobody uses, or break a rule you didn't know existed.
WhatsApp vs SMS customer support at a glance
| WhatsApp | SMS |
|---|
| Best for | Two-way support where customers already use WhatsApp | Short alerts, reminders and status updates |
| Reach | Strong outside the US; 30% of US adults | Every mobile phone |
| Main rule | Free-form replies only within 24 hours of the customer's last message | US senders must register, and consent depends on message type |
| Cost model | Paid per delivered template; other messages free | Paid per message segment, plus registration fees |
| Length | Long messages, files and images | 160 characters per segment, or 70 with an emoji |
| Weak for | Tickets that stay open for days; shared account channels | Anything detailed; login codes for sensitive accounts |
Where your customers are decides the channel
WhatsApp has more than 3 billion monthly users, but they aren't spread evenly. In Pew's 2025 survey, only 30% of US adults said they use it. GWI data compiled by DataReportal puts monthly use at 54% of online adults worldwide. We found no reliable data on B2B WhatsApp use by region, so be wary of vendor figures that claim one.
So the rule of thumb is simple. If most of your customers are in the US, SMS is the notification layer and email, chat and in-app help carry support. If you serve customers or partners in markets where WhatsApp is the default way to message anyone, it belongs in your support mix. The same goes for field teams and small-business owners who live on their phones.
How WhatsApp customer support works: the 24-hour window
Everything about WhatsApp support follows from one rule. Each message from a customer opens or resets a 24-hour customer service window. Inside it, you can reply with anything. Outside it, Meta's policy says you may only send approved message templates.
That rule collides with how B2B tickets actually run. You ask for logs, the customer's admin takes two days to find them, and engineering needs another day. By the time you have an answer, the window has closed. Now your reply has to be a pre-approved template, not a free-form message.
Design templates for re-opening conversations
Templates come in three categories: marketing, utility and authentication. A utility template follows up on a customer's request, so a short “We have an update on your request, reply to continue” message fits. Keep it clean. Meta treats a template that mixes a service update with promotional content as marketing, and it re-categorizes templates itself.
Know what you pay for
WhatsApp moved to per-message pricing on July 1, 2025. You pay only when a template is delivered. Non-template messages are free, and utility templates sent inside an open window are free too. So reactive support costs little per message. Proactive outage notices and follow-ups after the window are what you pay for, plus whatever your messaging provider or help desk charges. Some vendor pages still describe per-conversation pricing, which is out of date.
Automate inside the window, with a way out
You can use automation during the window. But WhatsApp's policy also requires “prompt, clear, and direct escalation paths” to a person or another channel. Customer service bots are allowed. Meta's rules from January 15, 2026 bar general-purpose AI assistants, where the AI is the product itself, not AI that serves your own customers.
Plan for the limits
A new business account can message 250 unique users outside the window in a rolling 24 hours. The limit rises through tiers as quality and verification improve. Customers must opt in before you contact them first. And WhatsApp is no substitute for a shared Slack channel. The Groups API allows a maximum of 8 participants per group.
Check what encryption covers
The Cloud API is now the only API route. On it, Meta acts as a data processor and decrypts messages on its servers for the business, keeping them for up to 30 days. That's normal for a hosted service, but it means “end-to-end encrypted” stops at Meta, not at your agent. Tell your security team before a customer asks.
How SMS customer support works: registration and consent
SMS reaches every phone, which is its strength. In the US, it also comes with more paperwork than most support leaders expect. This is a summary, not legal advice, and the rules are moving.
Register before you send
To text from a standard US number, you register your brand and each campaign. A campaign covers how customers opt in, opt out and get help. Unregistered traffic has been fully blocked since September 1, 2023. As of August 2025, a provider listed a $4.50 brand fee and $15 campaign vetting, plus monthly campaign fees. Toll-free numbers need their own verification, and unverified toll-free numbers have been blocked since November 2023.
Match consent to the message
The CTIA guidelines separate three types. If the customer texts first, “no additional permission is expected” for your reply. Informational messages, like outage alerts, need consent for that purpose. Promotional messages need written consent. Add a sales pitch to an outage alert, and it may count as promotional.
Honor opt-outs however they arrive
Customers can revoke consent by any reasonable method, a rule in force since April 11, 2025. Honor STOP and plain-language requests like “please stop texting me”, and send one confirmation, then nothing. A rule applying one opt-out to every message type has been delayed to January 31, 2027. The FCC also has a draft order on its September 30, 2026 agenda that would change it again. Check the outcome before you finalize your process.
Write for 160 characters
A standard SMS segment holds 160 characters, or 70 if it includes an emoji or a non-Latin character. Longer messages are split and billed per segment. That's room for a status update and a link, not a troubleshooting guide.
When neither WhatsApp nor SMS fits
Two jobs belong somewhere else. First, complex issues with several people from the customer involved. They need a shared thread, attachments and a record, so email, a portal or a shared Slack or Teams channel works better.
Second, login codes for sensitive accounts. NIST now classes SMS and voice codes as “restricted” authentication, and CISA advises highly targeted people not to use SMS as a second factor. SMS messages aren't end-to-end encrypted. Offer an authenticator app for admin consoles, and keep SMS as a fallback at most.
WhatsApp and SMS statistics to stop citing
Messaging vendors repeat a handful of numbers that don't hold up:
- “SMS has a 98% open rate.” We found no primary study, and SMS has no way to measure opens.
- “90% of texts are read within three minutes.” Same problem: no traceable source.
- “WhatsApp has 2 billion users.” Out of date. Meta reported more than 3 billion in 2025.
- “WhatsApp charges per conversation.” Wrong since July 2025. It charges per delivered template.
- Regional B2B adoption figures for Latin America or India. We couldn't trace any to a primary source.
How to run WhatsApp and SMS customer support without losing the thread
Give each channel a job
Decide what each channel is for before you launch it. For example: SMS for outage alerts and appointment reminders, WhatsApp for two-way support in named markets, email and chat for everything else. Put it on your support page.
Keep every message on the account record
A WhatsApp thread on a rep's phone is lost the day they leave. Route both channels into the same inbox as email and chat, attached to the customer's account, so the next person sees the history.
Write answers short enough to send
Both channels punish long answers. Keep short versions of your most common answers in the knowledge base, each linking to the full article. Then agents and AI agents send the same thing. If you serve several languages, see multilingual AI support.
Set response targets around the window
For WhatsApp, aim to resolve or update within 24 hours of the customer's last message. Keep a utility template ready for the cases that run longer.
MatrixFlows brings WhatsApp and SMS into the same inbox as email, live chat, Instagram, Slack and Microsoft Teams, attached to the record your team defines. Agents and the AI agent answer from one knowledge base, and a handoff to a person carries the full conversation. For the wider view, read our guide to customer support channels and what omnichannel customer service means. Or see how teams handle global customer support with a small team.
Start a free MatrixFlows workspace and connect your messaging channels to one record. Unlimited users, no credit card required.
.svg)
.svg)
.svg)
