WhatsApp template for ecommerce: delayed order notice

When an order is delayed, the customer gets nervous and starts asking questions. If you don't notify them first, you lose trust and they flood your inbox with messages. With this template, you can notify them clearly, empathetically, and professionally, without having to write everything from scratch every time.

• {{1}}: customer's name (e.g., Laura)
• {{2}}: order number (e.g., #1024)
• {{3}}: reason for the delay (e.g., transportation issues)
• {{4}}: new estimated delivery date (e.g., August 15)

1. 1Copy the message and replace the variables with the actual order details.
2. 2In WhatsApp Business, go to 'Message Templates' (or 'Quick Replies') and save it to use when needed.
3. 3If you use Wando, upload the template in the panel: the AI will automatically suggest it when a customer asks about their order, and you approve it with one click.

When to send this message (and when not to)

Send it as soon as you know there is a delay, not when the customer has already asked. An early notice turns a problem into a gesture of transparency; a late notice seems like an excuse.

Use it if the delay is real and you have a new estimated date. If you don't have a date, don't send it: better a short message saying you're checking and will get back with updates within 24 hours.

Don't use it for delays of a few hours, for orders already on their way (that just creates noise), or for orders the customer already knows are late due to their own fault (for example, incorrectly entered data).

Also don't send it if the customer has already canceled or if the order is in the return stage: in that case, the message is confusing.

• Yes: confirmed delay, new estimated date, customer not notified.
• No: no date, minor delay, canceled order or in return.

Likely customer responses and how to answer them

Three responses repeat almost always. Prepare them to respond quickly and without improvising.

1. "So when will it arrive then?" — The customer seeks certainty. Reaffirm the date and offer proactive tracking:

Sample message: "Hi {{1}}, the new date is {{2}}. If there are any changes, we'll let you know as soon as we find out. Do you want us to send you the tracking number?"

2. "No, that doesn't work for me. I want to cancel." — Don't argue. Confirm the cancellation and explain the next step:

Sample message: "Hi {{1}}, we completely understand. We've canceled your order {{2}} and the refund will be processed within 3 to 5 business days. Should we send you the receipt here?"

3. "And why was it delayed?" — Explain the reason without getting into technical details and move on to the solution:

Sample message: "Hi {{1}}, it was due to {{2}}. It's already resolved and your order is on its way. It will arrive on {{3}}. Do you want us to notify you when the delivery driver leaves?"

• Variables: {{1}} name, {{2}} order detail or date, {{3}} reason or date as applicable.

How to know if the message worked

The message worked if the customer doesn't bombard you with questions and doesn't complain. Measure it with three concrete signals:

1. Response rate: if the customer replies "thank you" or "ok", that's it. If they don't reply, it still worked: it prevented them from asking.

2. Follow-up inquiries: if no one asks "where is my order?" within the next 48 hours, the notice did its job.

3. Cancellations: if the cancellation rate doesn't rise after the notice, the message maintained trust. If it rises, review the tone or clarity of the date.

With Wando, you can see in statistics how many messages were sent with this template and how many responses were received. That gives you an exact number, not a feeling.

• It works: no follow-up questions, positive responses, stable cancellations.
• It doesn't work: more inquiries, complaints, or cancellations than usual.

Why Meta may reject the template and how to fix it

Meta reviews WhatsApp API templates before approving them. The most common rejections for this type of notice:

1. Missing date variable: if you don't include {{4}} with the new date, Meta considers the message vague. Always include an estimated date.

2. Promotional language: phrases like "Take advantage!" or "Special offer" make Meta classify it as marketing, and that's not what you want for a transactional notice.

3. Malformed variables: if you use unnumbered variables ({{1}}, {{2}}), Meta doesn't know what gets replaced and rejects it. Follow the format.

4. Incorrect category: a delay notice goes in utility, not marketing. If you put it in the wrong category, it gets rejected.

To fix it: check the rejection reason in the Meta panel, adjust the text, and resubmit. Approval can take up to 48 hours. With Wando, you load the template in the panel and the AI suggests it when appropriate, always with your approval.

• Corrections: add a date, remove promotional language, use numbered variables, choose the utility category.

When to use the formal variant and when to use the casual one

There is no single rule, but there are two criteria that help: the type of customer and the context of the delay.

Use the formal variant when the customer is a business, when the order is high-value, or when the delay is long and the customer has already shown impatience. The formal tone conveys seriousness and reduces tension.

Use the close variant when the customer is an individual, the order is low-value, or the delay is short. The close tone maintains trust and humanizes the brand.

If in doubt, start with the formal one and offer a close closing: "We are at your disposal". The close one can sound disrespectful if the customer is angry.

With Wando, you can save both variants and the AI suggests which one to use based on the conversation history with each customer.

• Formal: corporate customers, expensive orders, long delays.
• Close: individuals, small orders, short delays.