On this page
What a WhatsApp notification system does
A notification system listens for events in the software you already run — an order placed, a parcel dispatched, an appointment booked, a login attempted — and sends the matching WhatsApp message to the right customer without anyone pressing a button. It is the least glamorous kind of WhatsApp automation and often the most useful, because these are messages customers actually want.
Because the business starts these conversations, every notification uses a pre-approved template, usually in Meta’s utility or authentication category. The customer must have opted in to receive WhatsApp updates from you — typically a checkbox at checkout, booking or sign-up, with the consent recorded.
Notifications businesses commonly automate
| Business | Typical notifications |
|---|---|
| D2C brand or online store | Order confirmation, payment received, dispatched with tracking link, delivered, return approved |
| Clinic or diagnostic lab | Appointment confirmation, reminder the day before, report ready, follow-up visit due |
| Coaching institute | Class schedule changes, fee due reminders, test results available |
| Restaurant | Order accepted, out for delivery, table booking confirmation |
| SaaS startup | One-time passwords, security alerts, subscription renewal notices |
| Manufacturer | Dealer order confirmation, dispatch details, invoice issued |
What we build
- Event triggers — webhooks or API calls from your store, booking system, ERP or application, or a scheduled job for reminders.
- A sending service with a queue, so bursts of events don’t overwhelm the API and nothing is lost if a call fails.
- Templates drafted in the right category and submitted for approval, with variables for order numbers, dates and links.
- Delivery tracking — sent, delivered, read and failed statuses stored against each message.
- Fallback rules — if a critical message fails on WhatsApp, it can go by SMS or email instead.
- Opt-out handling — customers who stop updates are excluded automatically.
- A simple log screen so support staff can answer “did the customer get it?” in seconds.
Designing for reliability, not just sending
Sending one message is easy. Sending the right message exactly once, at the right time, to thousands of customers is where the engineering matters. We deduplicate events so a customer doesn’t get three “order confirmed” messages when a store retries its webhook. We respect quiet hours for reminders. We retry temporary failures with backoff and alert your team when failures persist.
OTPs need extra care
One-time passwords use Meta’s authentication templates, which have their own formatting rules. Codes are generated and verified in your own system, expire quickly and are never logged in readable form. For critical logins we recommend keeping an SMS or email fallback, since no single channel is guaranteed to deliver every time.
How we deliver it
- List every event that should trigger a message and what the customer needs to know at that moment.
- Confirm where each event comes from and how we’ll receive it.
- Draft templates and submit them for approval.
- Build the sending service, queue, status tracking and fallback.
- Test end to end with real orders or bookings on a staging setup.
- Go live one notification type at a time and monitor delivery.
This sits on top of an official WhatsApp Business API setup. If your events come from custom software, our Webhook Development work often covers the other side of the connection.
What affects timeline and cost
- Number of notification types and templates.
- Whether your systems already emit webhooks or need changes to send events.
- Volume and timing — bursty traffic such as sale days needs more careful queueing.
- Fallback channels, since SMS in India requires its own sender and template registration, and email needs a properly authenticated domain.
Mistakes to avoid
- Slipping promotions into utility templates — Meta may re-categorise them and customers notice.
- Sending reminders at night because a scheduled job ran in the wrong time zone.
- Having no record of what was delivered when a customer says they never got it.
- Relying on WhatsApp alone for messages that must arrive, such as login codes.
Explore the rest of our WhatsApp automation services, read the WhatsApp automation guide, or tell us which events you want to automate.
Frequently asked questions
Can notifications work with Shopify, WooCommerce or our own store?
Yes. Most store platforms can send webhooks on order events, and custom software can call our sending service directly. We confirm what your platform supports during scoping.
Do customers need to opt in to receive order updates?
Yes. WhatsApp requires opt-in for business-initiated messages. A clear checkbox or consent line at checkout or booking is the usual way to collect it.
What if a customer doesn’t have WhatsApp?
The message fails with a status we can detect, and the fallback rule sends it by SMS or email instead, if you’ve set one up.
Can customers reply to a notification?
Yes. A reply opens the 24-hour customer service window, and the conversation can go to a chatbot or your support inbox like any other chat.
Should WhatsApp replace our order emails?
Usually it works best alongside them. WhatsApp is read quickly and suits short updates, while email is better for detailed invoices and records. Many businesses send both for important events and WhatsApp alone for small status changes. Our Transactional Email Setup service covers the email side.
Talk to us about notification systems
Order updates, appointment reminders and OTPs delivered reliably through WhatsApp.