Job · Order confirmation
Confirm the order before the courier touches it.
Every order gets a confirmation message on the channel the customer actually reads. A reply releases it. Silence holds it. Nothing ships on a maybe.
Illustrative demo with fictional data.
What it looks like
One template out, one reply back, one order flipped.
The same sequence runs on every order that matches your filter. The parts that change money are the parts you can read afterwards.
The template goes out
The order is placed and BlendDesk sends your approved confirmation template to the customer's WhatsApp number — utility category, because it is about an order the customer already placed.
The customer replies
Quick replies map to confirm and cancel. The reply lands in the same thread an agent would use, so anything unexpected becomes a conversation rather than a dead end.
The order flips
A confirmed order is written back to your store and released for pickup, with the customer's reply attached to the order record.
Silence holds the order
No reply after the reminders you configured? It stays held and appears in a list for a person to call. It does not ship, and it is never auto-cancelled.
The problem
An unconfirmed order is a shipping bill you pay twice.
Cash on delivery moves the risk onto you, and it lands as logistics cost long before it lands as a refund.
- Fake orders
- Cash on delivery lets anyone place an order against a phone number that may not be theirs. Without a confirmation step you discover it at the door.
- Wasted shipments
- A courier drives to an address, nobody answers, the parcel comes back. You pay both legs and the stock sits in transit for a week.
- Cancellation after shipping
- The customer changes their mind while the parcel is already moving. The cheapest moment to catch that is before the pickup, in a message.
- The courier does not call
- Confirmation gets delegated to a call centre that calls once, in working hours, from an unknown number. A WhatsApp message gets read.
- Confirmation by hand
- One person on a phone, order by order, reading the same three lines. It works at twenty orders a day and collapses at two hundred.
Public review of a different WhatsApp app on the Shopify App Store, Egypt, 11 February 2026.
“accurately sends whatsapp, email and sms order confirmations, unsuccessful rate decreased from 30% to 7%”
Public review of a different WhatsApp app on the Shopify App Store, Egypt, 11 February 2026.
Not a BlendDesk customer and not our number. We publish it because it is the clearest public description of what confirmation messaging is worth, written by a merchant rather than a vendor. Your own figure is the only one that matters, and you will see it in your analytics.
How it works
The mechanism, step by step.
Nothing here is a model decision. The language is Scout's; the facts and the state changes are the automation's.
- Trigger
- A new order in your store, or a webhook from whatever system holds orders. Run it on every order, or only the ones that match a filter — cash on delivery, first-time customer, above a value you set.
- Template
- A pre-approved utility template carrying the order number and items. You write it, Meta approves it, BlendDesk sends it. The category is declared, not guessed.
- Reply handling
- Buttons map to confirm and cancel. Free text goes to Scout, which answers inside the scenario you wrote — address change, item swap, delivery timing — and escalates anything that moves money.
- Write-back
- The result updates the order through a native integration or a custom HTTPS tool pointed at your own endpoint, and the call appears in the run trace with its response.
- Hold rules
- Reminder count, spacing, and what happens after the last one. The default is hold and assign to a person, never cancel on the customer's behalf.
- Audit
- Every send, reply and write-back is one run with a trace: what was sent, what came back, what changed, and when.
What it costs to send
Order confirmation is a utility template.
A confirmation is about a transaction the customer already made, so it routes as utility — the cheapest template category Meta sells. Getting that category right, or wrong, is the largest message-cost lever most businesses control.
- Order confirmation template (Egypt)
- $0.0036
- Utility category: order confirmations, shipping updates, anything about an existing transaction.
- The same message sent as marketing (Egypt)
- $0.0644
- What a wrongly categorised template costs: about eighteen times the utility rate for identical text.
- The customer's reply
- Service message
- A message from the customer opens a 24-hour window. Meta began charging for service messages on 1 October 2026, with the first 1,000 per business phone number per month free.
Source: Meta WhatsApp per-message rate card, Egypt, retrieved 2 November 2026; category, window and service-message rules from Meta developer documentation.
Meta bills these fees, not us, and we never mark them up. BlendDesk charges for seats and AI resolutions.
Control
The off switch is part of the job.
Confirmation touches orders, which means it touches money. Everything that does gets a gate.
- Nothing auto-cancels
- Scout can confirm and hold. Cancelling an order is a state change that waits for a person unless you explicitly decide otherwise.
- A human path, always
- Any thread can be taken over mid-flow with the full history. Meta's policy requires an escalation path out of automation; we treat it as a product requirement rather than a checkbox.
- Rehearse first
- Run the scenario in the playground against real past orders, see every reply it would have sent, and change it before it touches a customer.
- Read the run
- Template sent, reply received, order updated, by whom, at what time. One trace per order, kept for as long as your plan retains them.
Source: WhatsApp Business Messaging Policy, updated 23 September 2026.
What you need
Four things, and we help with three of them.
- A WhatsApp Business number connected to BlendDesk.
- One approved utility template — we draft it with you and submit it for approval.
- A way to read and update orders: a native integration, or a read-and-write HTTPS endpoint you control.
- A decision about what happens when nobody replies.
Questions buyers actually ask.
Does this only work for cash-on-delivery orders?
No. It runs on any order you want confirmed. Cash on delivery is where it pays for itself fastest, because an unconfirmed COD order can cost you two courier legs and a week of stock in transit.
What if the customer replies with something other than confirm or cancel?
The free-text reply opens a normal conversation. Scout answers inside the scenario you wrote — address changes, item swaps, delivery timing — and hands over to a person for anything that changes money.
Can it run on channels other than WhatsApp?
Yes, on any channel you have connected. WhatsApp is the default because it is where confirmation messages actually get read.
Will Meta charge me for each confirmation?
Yes, at the utility rate for the destination country. BlendDesk does not mark it up, and the calculator shows the rate for your market before you send anything.
What stops it from messaging the same customer repeatedly?
Reminder count and spacing are set per automation, and a customer who has confirmed drops out of the sequence immediately.
Do I need a developer?
Only if your order system has no native integration. In that case the requirement is one HTTPS endpoint that returns an order and accepts a confirmation result.
See it confirm a real order.
Book a demo and we will run your confirmation flow — your template, your hold rules, your write-back — against a test store.