A message that actually gets opened:
SMS and WhatsApp, not another unread email
Customers open SMS and WhatsApp messages far more often than email. That only works 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
An SMS or WhatsApp notification is a message triggered by an event in your system. An order confirmed, an appointment coming up, a delivery on its way, a one-time password. We send all of these through official messaging APIs, not email. People open a text on their phone far more reliably than an email, and for a short, time-sensitive message that difference matters. The build covers the API integration, approved message templates, delivery tracking, and the opt-out handling that keeps your sending account in good standing.
When you need it, and when you do not
You need this when timing matters: a customer should hear their order shipped today, not whenever they next check email. The same goes for markets where WhatsApp or SMS simply beats 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 that needs a one-time password for verification are the clearest fits.
You can skip this if your notifications are not time-sensitive and your audience reads email reliably. The email infrastructure page is the better starting point there. It is also fine to wait if your volume is still low enough that a manual message works for now.
How we build it
WhatsApp runs on the official WhatsApp Business Cloud API, never an unofficial workaround. Unofficial methods get numbers banned without warning, and take your whole notification pipeline down with them. Message templates go through WhatsApp’s approval process before use. We categorize them correctly as utility, marketing or authentication, since the category affects both approval odds and cost per message. SMS runs through Twilio for most markets, or a local provider where regional delivery rates are meaningfully better. That varies by country, and we check it before committing to one provider.
Your 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. It sends through whichever channel the customer prefers, or your default channel for that market. Delivery status, sent, delivered, read or failed, gets written back into your order or booking system. If a time-sensitive message fails on one channel, it can fall back to the other automatically.
Opt-outs are honored immediately and logged per phone number. That protects the customer, and it keeps your account’s standing intact with the messaging providers.
What to watch
WhatsApp’s template approval and category rules shift from time to time. A template that was fine six months ago can need resubmission. We keep templates compliant and tell you if a change affects your setup. Account bans from unofficial WhatsApp integrations are permanent and immediate. That alone is the biggest reason to use the official API, even though it is more restrictive than a workaround.
SMS costs vary enormously by destination country. A system that sends internationally without that awareness can get expensive fast. We flag per-country costs during setup, not 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, and that is 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. For a Telegram-based notification and alert system, see 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 costs more. So does covering several template categories such as orders, reminders, OTP and support. Together that 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 set categories like order updates, reminders or OTP. That is exactly what this build sets up. Free-form messages outside an open customer conversation are restricted by WhatsApp's own policy. We build within those rules, not around them.
What happens if a WhatsApp message fails to deliver?
The system tracks delivery status: sent, delivered, read, failed. For time-sensitive messages like OTP or delivery alerts, it can fall back to SMS automatically. A failed WhatsApp send does not just 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 the template submissions with you, since templates need approval before they can go out.
Is this different from the WhatsApp features in an AI sales agent?
Yes. This is the notification layer, triggered by events in your system like an order placed or an appointment booked, not by a conversation. It can run on its own, or alongside an AI sales or support agent that handles the conversational side on the same channel.