WhatsApp order updates and COD confirmation that cut returns
A COD order that was never confirmed is a parcel that comes back. Linkubit confirms the order, asks a COD customer for a YES before it ships, sends the shipped and out-for-delivery updates, answers "where is my order?" from the record, and handles a failed attempt or a return without a ticket.
Linkubit confirms an order on WhatsApp the moment it is placed, asks a cash-on-delivery customer to confirm before it ships, sends shipping and delivery updates as utility templates, answers order questions from the order record, and handles a failed delivery or a return request in the same thread.
What it asks for
- Order number, or the phone number it was placed with
- COD: a YES before dispatch
- Delivery address confirmation and landmark
- Preferred delivery slot where the courier allows one
- For a return: reason, and photos where needed
- Refund method
None of this is hardcoded. It is a schema you edit, which is why a completely different business runs on the same system.
Updates that stay cheap
Utility templates, with no promotion inside
"Your order has shipped" is a utility message. "Your order has shipped — shop again for 10% off" is marketing, priced several times higher and rejected by review more often. The pack keeps the two apart; the assistant sends the right one.
- Every update is a template written to pass review
- A reply to any update reopens a free-form conversation
Pre-flight across 1,241 contacts
1,183 will send
consent and identity checks passed37 skipped — no marketing consent
service messages only21 suppressed — unsubscribed earlier
refused permanentlyQuestions answered from the order
"Where is my order?" is answered from the record, not by a person
The assistant reads the order and the courier status you gave it, answers with the tracking and the next step, and hands over only when the answer is not there — a lost parcel, a damaged item, a refund that has not landed.
- Handover carries the order and the thread
- A return request opens with reason and photos captured
Sales Agent
Internal note · good running volume, taking this one — Rohan
Rohan · took over
The rule that holds
A COD order does not ship until the customer says YES
The confirmation goes the moment the order is placed with a YES button; no YES within the time you set is a hold, not a dispatch. Order, shipping and delivery messages are utility templates about a transaction the customer started — no promotional line inside them, because that re-categorises the message and multiplies its price.
Anything else goes to a person
A topic you named, a value above a threshold, a customer who asks for a human, or a question the assistant cannot answer from what you gave it — the conversation is handed over before a reply is written, with the whole thread and every field captured so far.
From checkout to delivered, in one thread
What an order looks like when the confirmations, the updates and the questions are handled, and a person handles the exceptions.
Confirmed the moment it is placed
Order number, items, amount, delivery estimate. For COD, a YES button and a hold until it is pressed; a prepaid order confirms and moves on.
Shipped, with tracking
The courier, the tracking link and the expected date, sent as a utility template when the parcel leaves. A change of address before dispatch is accepted in the same thread.
Out for delivery, and a failed attempt
A failed attempt is a message asking for a better time or a landmark, not a parcel on its way back. The reply is written onto the order for the courier.
Delivered, then one question
A review request a few days after delivery — marketing, consented, with a STOP line — and nothing else unless the customer writes.
A return, handled without a ticket
Reason and photos captured, the return booked, the refund method confirmed, and the refund confirmation sent when it lands. A dispute goes to a person with all of it already in the thread.
The templates it sends
6 WhatsApp message templates from the industry packs that carry this use case, each written the way Meta's review reads it. Open one for its variables, a filled example and what gets it rejected.
| Template | Category | When it goes out |
|---|---|---|
| Order confirmed | Utility | Payment is captured. |
| Shipped | Utility | The courier has picked up. |
| COD confirmation | Utility | A COD order is placed, before it is packed. |
| Delivery attempted | Utility | The courier could not deliver. |
| Shipment departed | Utility | The vessel or flight has left. |
| Proof of delivery | Utility | Delivered, with the signed POD in hand. |
Each template opens on its own page with the variables, a filled example and what Meta’s review objects to. Utility and authentication templates cost ₹0.115 a message in India, marketing ₹0.8631 — the pricing guide has the rest.
Questions people ask
Does it connect to Shopify or WooCommerce?
Orders reach Linkubit as events from your store or as rows you upload, and the assistant reads them as the customer's record. The updates it sends are templates on your own WhatsApp number.
What if the COD customer never confirms?
The order holds for the time you set, gets one more nudge, and is then marked unconfirmed for a person to decide. That is the parcel that would have come back.
Can customers change the address or the slot in the chat?
Before dispatch, yes — the assistant writes the change onto the order and confirms it. After dispatch it tells them what the courier allows and passes the request on.
Why does it matter that these are utility templates?
Meta prices utility messages at a fraction of marketing messages, and rejects a utility template that contains a promotional line. Keeping the update and the offer in separate messages is what keeps the bill and the approval rate where they should be.
Read next
Ready to put your sales on autopilot?
Start freeNo coding required. No credit card required.