A message that actually gets opened:
SMS and WhatsApp, not another unread email
Order confirmations, appointment reminders and delivery alerts get opened on SMS and WhatsApp at rates email cannot match, but only when the sending is done on an official API with approved templates, not a workaround that gets a number banned. We build the integration the compliant way, with delivery tracking and a real fallback path.
What it is
SMS and WhatsApp notifications are event-triggered messages, an order confirmation, an appointment reminder, a delivery update, a one-time password, sent through official messaging APIs rather than email, because open rates on a phone’s native messaging app run far higher than email for exactly this kind of time-sensitive, short message. The infrastructure covers the API integration, approved message templates, delivery tracking and the opt-out handling that keeps the sending compliant and the sending account in good standing.
When you need it (and when you do not)
You need this when a notification’s timing matters, a customer needs to know their order shipped today, not whenever they next check email, or when your audience’s market genuinely prefers WhatsApp or SMS over email, which is common across much of Asia, Latin America and parts of Europe. Appointment-based businesses, delivery and logistics, e-commerce order updates and anything needing a one-time password for verification are the clearest fits.
You do not need this if your notifications are not time-sensitive and your audience reliably reads email, in which case the email infrastructure page is the better starting point, or if your volume is low enough that a manual message genuinely works for now.
How we build it
WhatsApp integration runs on the official WhatsApp Business Cloud API, never an unofficial workaround, because unofficial methods get numbers banned without warning and take your notification pipeline down with them. Message templates go through WhatsApp’s approval process before use, categorized correctly (utility, marketing, authentication) since the category affects both approval odds and cost per message. SMS integration runs through Twilio for most markets or a local provider where regional delivery rates are meaningfully better, which varies by country and is worth checking before committing to one provider.
The backend, Python/FastAPI or Node/TypeScript, listens for the events that should trigger a message, an order status change, a booking confirmation, a delivery milestone, and sends through whichever channel the customer has indicated a preference for, or your default channel for that market. Delivery status (sent, delivered, read, failed) gets tracked and written back into your order or booking system, and a failed delivery on one channel can trigger an automatic fallback to the other when the message is time-sensitive enough to warrant it.
Opt-outs are honored immediately and permanently, logged per phone number, which both respects the customer and keeps your account’s compliance standing intact with the messaging providers.
What to watch
WhatsApp’s template approval and category rules change periodically, and a template that was fine six months ago can need resubmission; we keep templates compliant and tell you if a change affects your existing setup. Account bans from unofficial WhatsApp integrations are permanent and immediate, which is the single biggest reason to use the official API even though it is more restrictive than a workaround.
SMS costs vary enormously by destination country, and a notification system that sends internationally without per-country cost awareness can get expensive fast; we flag this during setup rather than after the first surprising invoice.
Price and timeline
| Option | Price | What it covers | Timeline |
|---|---|---|---|
| Single channel | from $1,500 | WhatsApp or SMS, event triggers, delivery tracking, opt-out handling | 1 to 2 weeks |
| Multi-channel with fallback | from $2,800 | Both channels, automatic fallback, multiple template categories | 2 to 3 weeks |
Running cost is usually $0.005 to $0.08 per message depending on channel and destination country, separate from the integration fee.
Related
Pairs with email infrastructure and deliverability for a complete multi-channel notification stack, and with the setup and integrations service for the broader messaging account setup. See the development service page for custom builds on top of this. For a production system sending across seven channels including WhatsApp-adjacent messengers from one brain, see the seven-channel AI sales agent case study, and for a Telegram-based notification and alert system, the staffing agency recruitment bot case study.
Need order and appointment updates that actually get read? Get in touch and we will set up the right channel mix for your market.
FAQ
How much does WhatsApp or SMS notification setup cost?
From $1,500 for WhatsApp Business API integration with a handful of approved templates and event-triggered sending. Adding SMS as a fallback channel, or multiple template categories (orders, reminders, OTP, support), typically runs $2,500 to $4,500.
Can we message customers who have not messaged us first?
On WhatsApp, only with pre-approved template messages for specific categories like order updates, reminders or OTP, which is exactly what this build sets up. Free-form messages outside an open customer conversation are restricted by WhatsApp's own policy, and we build within those rules rather than around them.
What happens if a WhatsApp message fails to deliver?
The system tracks delivery status (sent, delivered, read, failed) and can automatically fall back to SMS for time-sensitive messages like OTP or delivery alerts, so a failed WhatsApp send does not silently disappear.
Do we need a verified WhatsApp Business Account?
Yes, and getting one verified and template-approved is part of the setup. We handle the application and template submission process with you, since templates need approval before they can be used for notifications.
Is this different from the WhatsApp features in an AI sales agent?
This is the notification layer, triggered by events in your system (order placed, appointment booked) rather than a conversation. It can run standalone or alongside an AI sales or support agent that handles the conversational side on the same channel.