PRACTICAL GUIDE
Order updates on WhatsApp: what to send at each stage
An order can pass through several internal statuses without the customer needing to hear about all of them. Choose the moments when an update answers a real question or explains what to do next.
By WatsBridge · Published 30 October 2026
Begin with the question, then find the event
List the follow-up questions your team receives. “Did the order go through?” calls for a different answer from “Can I collect it?” Match each useful answer to the system event that can establish it.
Write those pairs down before configuring notifications. If no dependable event exists, keep that step with a person until the source is ready.
Confirm what was received
A new-order message should identify the order and explain any outstanding action. Do not say that payment has cleared merely because a customer reached the end of checkout.
Keep the reference clear and avoid exposing unnecessary purchase information in the notification. Make the next step accessible to the intended customer.
Make collection information usable
A collection message needs an actual readiness decision, a location and accurate opening hours. A customer arriving too early creates another service problem.
Order [reference] is ready to collect at [location]. We are open [hours]. Please bring your order reference. Reply here if you need to discuss collection.
This is an illustrative draft, not a Meta-approved template. Configure only values that your supported workflow can resolve reliably.
Keep dispatch separate from arrival
If a supported source establishes dispatch, say that the parcel has been dispatched. Link to an appropriate tracking destination when available. An internal WooCommerce completion status alone does not demonstrate that the carrier has collected or delivered a parcel.
If you cannot establish a delivery estimate, explain where the customer can obtain current information rather than inventing a date.
Prepare for the exception
A delay, failed payment or cancellation may need a different message and a person who can answer questions. Decide who reviews the event and which parts of the process are safe to automate.
Check what happens when an event is repeated or a required value is absent. Test the full route in the relevant setup, including the reply, before enabling it for customers.
Keep the message attached to its purpose
Use the appropriate template and permission for the communication. Meta’s utility message guidance covers transaction-related uses; adding a promotion changes the purpose that needs assessment.
In WatsBridge, the order communication workflow starts with the supported events and data in your store. Confirm integrations and current availability during setup. The goal is a dependable update that removes a repeated question, with a person available when the situation needs one.
Sources and further reading
External sources checked on 30 October 2026. Platform availability and rules can change.
Published by WatsBridge. How we prepare our articles · Suggest a correction
