How Sri Lankan Businesses Can Cut "Where Is My Order" Messages with WhatsApp Automation
Most "where is my order" messages are not about slow delivery. They come from the silent gaps between order placed and order delivered. Here is which update to send at each stage, by industry, and a simple way to measure whether it is working.

Customers rarely message "where is my order?" because delivery is slow. They message because nothing has told them anything since they paid or placed a COD order. This guide shows which WhatsApp update to send at each stage for five kinds of Sri Lankan business, how to count "where is my order" (WISMO) messages yourself before and after, and what the templates can say.
Quick answer: Find the stage where customers ask most (usually between order placed and dispatch, and on delivery day), then send one short, factual WhatsApp update at that stage, triggered automatically by your order or booking system. Count WISMO chats per 100 orders for two weeks before and four weeks after, so you know whether it worked. Keep every update strictly about the order so Meta prices it as a utility message, not marketing.
Where WISMO messages actually come from
In the order flows we build for clients, the questions cluster around a few predictable moments: right after a bank transfer or card payment ("did you get it?"), the day or two before dispatch ("has it been sent?"), and delivery day ("is the rider coming today?"). Questions after delivery are usually about returns or COD change, not location. If you know which moment produces most of your messages, you only need one or two well-timed updates, not a message for every internal status.
That is why measuring comes first. Sending five updates per order costs more and annoys customers; sending the one update that answers the question before it is asked is what reduces the load.
Step 1: Measure your WISMO rate before changing anything
You do not need software for this. If your team answers customers on the WhatsApp Business app, use its labels (you can create up to 20, according to WhatsApp Help: How to use labels).
- Create three labels: WISMO - before dispatch, WISMO - delivery day and WISMO - other (payment received?, wrong address, and so on).
- For two normal weeks (avoid Avurudu, Vesak or a big sale week), staff apply the label the first time a customer asks about order status. One label per order, not per message, so a customer asking three times still counts once.
- At the end of each week, note the number of chats under each label and the number of orders you shipped that week.
- Calculate WISMO per 100 orders = (labelled chats / orders) x 100, for each label. This is your baseline.
- Also note the stage with the highest count. That is where your first automatic update goes.
| Week | Orders | Before dispatch | Delivery day | Other | WISMO per 100 orders |
|---|---|---|---|---|---|
| Baseline week 1 | |||||
| Baseline week 2 | |||||
| After week 1-4 |
Copy this table into a sheet. Keep the counting rules identical after you switch on updates, otherwise you are comparing different things. Phone calls asking the same question should be counted too if they are a large share of your enquiries.
Step 2: Pick the messages for each stage, by industry
Each row below is a moment your system already knows about. The trigger column is what has to happen in your store, courier sheet, POS or booking tool for the message to go out.
Retail and e-commerce
| Stage | Message | Trigger in your system |
|---|---|---|
| Order placed / payment confirmed | Order number, items, total, payment method (COD or paid) | Checkout completed or bank transfer marked as received |
| Dispatched | Courier name, tracking number, expected delivery window | Order status set to Shipped |
| Delivery day (optional) | Rider is out today; have the COD amount ready | Courier marks out for delivery, if your courier gives you that event |
| Delivered | Delivered confirmation, how to report a problem | Status set to Delivered |
Courier and logistics
| Stage | Message | Trigger in your system |
|---|---|---|
| Shipment created | Sender name, tracking number, expected delivery date | Waybill created |
| Out for delivery | Delivery today, COD amount, rider contact number if you share it | Package assigned to a rider route |
| Delivery attempt failed | Reason, how to reschedule, how long the parcel is held | Rider records failed attempt |
| Delivered / COD collected | Delivered time; for the merchant, COD collected | Proof of delivery recorded |
For couriers, the failed-attempt message matters most: it turns an angry call into a rescheduled delivery.
Pharmacy
| Stage | Message | Trigger in your system |
|---|---|---|
| Prescription or order received | We received your order; we will confirm availability | Order or prescription photo logged |
| Ready for pickup / out for delivery | Order number and collection hours, or delivery today | Pharmacist marks order ready |
| Refill due (only if the customer asked for it) | Your monthly order can be prepared; reply to confirm | Refill date set at the customer's request |
Keep medicine names and conditions out of the message and use an order number instead. Health information is sensitive personal data, and Sri Lanka's Personal Data Protection Act No. 9 of 2022 sets rules for how you collect and use it. A lock-screen preview should never reveal what someone is being treated for.
Salons and spas
| Stage | Message | Trigger in your system |
|---|---|---|
| Booking confirmed | Service, stylist, date, time, branch | Booking created |
| Reminder | Time and branch; reply to reschedule | Your booking system or automation tool, at the time you choose |
| Visit completed | Receipt and amount paid | Bill closed at the counter |
Tuition classes and institutes
| Stage | Message | Trigger in your system |
|---|---|---|
| Registration confirmed | Student name, class, day and time, hall | Registration saved |
| Fee received | Receipt with month and amount | Payment recorded |
| Class changed or cancelled | New date, time or hall | Teacher or admin edits the timetable |
| Monthly fee due | Amount and due date | Billing run in your system |
For booking and fee reminders, timing matters as much as wording. We cover reminder timelines and no-shows separately in our guide to WhatsApp appointment and payment reminders.
Step 3: Write templates that stay in the utility category
A business can only start a WhatsApp conversation with a template Meta has approved, and Meta prices templates by category. Utility templates must be specific to the customer's order or request and must not contain promotional or persuasive content; a template that mixes an order update with a promotion is classed as marketing (Meta: template category guidelines). At Meta's Sri Lanka rates, a utility message costs roughly Rs 0.66 against about Rs 24 for marketing (approx., Oct 2026, see Meta: WhatsApp pricing).
Examples you can adapt ({{1}}, {{2}} are the variables your system fills in):
- Order confirmed: "Hi {{1}}, we have received your order {{2}} for Rs {{3}} (payment: {{4}}). We will message you again when it is dispatched."
- Dispatched: "Your order {{1}} was handed to {{2}} today. Tracking number: {{3}}. Expected delivery: {{4}}."
- Delivery attempt failed: "We tried to deliver parcel {{1}} today but could not reach you. Reply to this message to choose a new delivery day. We will hold the parcel until {{2}}."
- Sinhala dispatch example: "ආයුබෝවන් {{1}}, ඔබේ ඇණවුම {{2}} අද කුරියර් කළා. Tracking අංකය: {{3}}."
- Avoid: "Your order is on its way! Use code SAVE10 on your next order." The discount line turns it into a marketing template.
Step 4: Switch on the updates and connect your system
These messages go out on the official WhatsApp Business Platform, through a notification provider or Meta's Cloud API. Your store, POS, courier sheet or booking tool calls the provider's API (or a Zapier, Make or n8n HTTP step) when an order changes, and the provider sends the matching template in English, Sinhala or Tamil and reports whether it was sent, delivered and read. The provider does not decide when an order changes; that event has to come from your system. The step-by-step integration is covered in how WhatsApp order notifications work.
Example cost (illustration): a shop shipping 300 orders a month and sending three updates per order sends 900 notifications. Meta's utility fee is roughly Rs 594 (900 x Rs 0.66), billed by Meta to the shop's own WhatsApp Business Account. At 800 orders and three updates (2,400 notifications) it is roughly Rs 1,584. The provider's own monthly fee comes on top, so compare plans against your real volume.
Step 5: Read the results after four weeks
- WISMO per 100 orders went down at the stage you covered: keep it, and consider the next-busiest stage.
- No change: check delivered and read status. If messages are delivered but not read, test a shorter first line; if many fail, check the phone numbers your checkout collects (missing 94 country code is a common cause).
- Questions moved to a new stage: customers now know it was dispatched but ask on delivery day. That is the next message to add, if your courier gives you the event.
- More replies to the update itself: normal at first. If your notification tool has no inbox, replies arrive in the WhatsApp chat on your number, so make sure someone is watching the WhatsApp Business app.
Do not judge on one week. Delivery delays, a holiday or a courier problem can swamp the numbers. Four weeks with the same counting rules gives you a fair comparison.
Frequently Asked Questions
How many updates per order is too many?
For most shops, two or three: confirmation, dispatch with tracking, and optionally delivered or out for delivery. Add a message only when your WISMO count shows customers are asking at that stage.
My courier does not give me an "out for delivery" event. What can I send?
Send the dispatch message with the courier's tracking number and expected delivery window. Customers can check the courier's tracking page themselves, which removes most delivery-day questions without a live event.
Do customers have to agree to receive order updates on WhatsApp?
Yes. Meta requires opt-in that names your business and makes clear the customer is agreeing to messages (Meta: getting opt-in). A checkbox at checkout such as "Send my order updates on WhatsApp" works well.
Can I keep using the WhatsApp Business app on the same number?
Yes. Meta allows a number that is already on the WhatsApp Business app to be connected to the Platform, and you can keep chatting with customers in the app. A number on personal WhatsApp has to move to the Business app first.
We have no online store, just a spreadsheet of orders. Can this still work?
Yes, through an automation tool. Zapier, Make or n8n can watch the sheet and call your notification provider's API when a status column changes to Shipped. Stores on Shopify or WooCommerce can use the same route if no ready-made plugin fits.
Send the update before the customer has to ask.
We can connect your store or booking system to WhatsApp order updates as a custom software project. For the questions that still come in, Ceytrex Agent answers in English, Sinhala and Tamil and hands chats to your staff when needed.
Sources
- Meta: WhatsApp Business Platform pricing - per-message pricing, template categories and rate cards
- Meta: template category guidelines - what counts as utility versus marketing
- Meta: getting opt-in for WhatsApp - opt-in requirements
- WhatsApp Help: How to use labels - labels in the WhatsApp Business app
- Data Protection Authority of Sri Lanka - Personal Data Protection Act No. 9 of 2022



