WhatsApp order-status messages: what customers need to know

Build the reply from the latest trusted order or shipment record. A payment event, warehouse task and carrier scan describe different things. Do not turn one into another just to make the message sound complete.

Use this reply checklist:

• The order reference the customer recognises.
• The confirmed stage and which item or shipment it concerns.
• The tracking link, if a shipment has one.
• An estimate only when your source provides it.
• The next action when something needs attention.

Match the reply to the question. Someone asking about a missing parcel does not need a repeat of the original order confirmation. Check whether the order has separate shipments before saying that everything has shipped.

These are fictional examples, not messages from a customer account. Replace the details with verified information.

Preparing: “Order DEMO-204 is being packed. A tracking link is not available yet. Would you like the team to check a delivery question?”

Dispatched: “The first parcel from order DEMO-204 has shipped. You can check its progress using the tracking link. The remaining item is still being prepared.”

Delayed: “The carrier shows a delay for order DEMO-204. It has not supplied a revised delivery date. I can pass this to support for a check.”

These replies do not promise that a shipment will arrive tomorrow. They make the evidence and the next option visible. If a source includes an estimated date, describe it as an estimate and avoid silently converting it into a guarantee.

Use the store’s authorised process to match the request to an order before sharing its details. An order reference alone should not become a shortcut around customer verification. Someone may paste a reference from a forwarded message.

Ask only for information needed by the approved lookup process. Do not paste addresses, payment details or another customer’s order history into a WhatsApp reply. If there are several matching orders, let the customer identify the relevant purchase without exposing unnecessary information.

A failed lookup needs a clear fallback: “I could not match that reference. A teammate can help check it.” It does not mean the purchase never happened.

Route disputes and changes to the team that can act on them. A carrier status marked delivered with a customer reporting non-receipt needs investigation. A request to change an address needs an authorised decision. Neither is resolved by repeating the tracking link.

Include the reference, latest observed status, customer’s question and checks already attempted in the handoff. The handoff decision guide covers situations where another automated answer is unlikely to help.

Keep the customer’s words distinct from system facts. “Customer reports parcel missing; carrier marks delivered” is a usable summary. “Parcel lost” is a conclusion the team may not yet be able to support.

Plan proactive updates around permission and the appropriate approved template. On the Business Platform, replies outside the customer-service window require templates. WhatsApp’s policy sets those boundaries.

The template guide helps explain approval. Treat these examples as writing aids, not pre-approved templates. Keep a service update focused on the order instead of adding an unrelated promotion.

Also distinguish the status of the order from the status of the message. A message being accepted for sending does not show that the customer received or read it. The glossary explains queued and delivered messages.

Test representative fictional orders: one preparing, one split across parcels, one delayed and one the lookup cannot find. Check whether the wording changes when information is missing. Make sure a stale record cannot produce an unsupported arrival promise.

The D2C workflow page is the next step for planning store and support ownership. If your store uses Shopify, review the Shopify integration before deciding which data can support a reply. Keep an exception route in the design from the beginning.

Download the blank checklist to adapt the fields for your team. Use fictional records when testing it.