WhatsApp template to notify order delays (food service)

We know that in a pizzeria (or any restaurant), the phone doesn't stop between 12:00 and 15:00, and amid so many orders, it can happen that one takes longer than expected. The customer gets impatient, sends a WhatsApp asking, and if you don't reply quickly, they go elsewhere. That's why having a template to notify about delays saves you: it shows you're aware, you care, and the order is on its way.

• {{1}}: the customer's name, for example "Maria".
• {{2}}: the order number or details, for example "#1234" or "the Neapolitan pizza with fainá".
• {{3}}: the estimated delay time, for example "15 minutes" or "half an hour".

1. 1Copy the message above and replace the variables {{1}}, {{2}}, and {{3}} with the order details.
2. 2Paste it into the WhatsApp Business conversation with the customer and send it.
3. 3If you use Wando, load this template in the template panel: the AI will use it automatically when it detects an order is delayed, and you only approve it with one click.

This type of message is transactional (delay notification) and falls into the "utility" category in Meta's WhatsApp API. That means it doesn't require customer opt-in to send, but it does require the template to be approved by Meta before use. Approval usually takes up to 48 hours, so load it in advance. With Wando, you load it once and the AI uses it when appropriate, always with your approval.

When is it appropriate to send this message (and when not)?

The right moment makes all the difference. Send it as soon as you know the order will take longer than promised, not when the customer has already asked. If you wait for them to write to you, you're too late: the customer is already upset and the template loses its effect.

Don't send it if the delay is just two minutes or if you're not sure it will actually happen. An unnecessary notice creates noise and distrust. Also, don't use it for orders that have already shipped: in that case, send a shipping confirmation message, not an apology.

The rule is simple: if the delay exceeds 10-15 minutes and affects the experience, notify. If it's shorter or uncertain, wait. The customer values being notified beforehand, not being asked for patience afterwards.

What to reply when the customer responds (3 sample messages)

The customer may respond in several ways. The three most likely are: asking how much longer, canceling the order, or complaining. Here's a sample message for each, ready to copy and adapt.

• If they ask how much longer: "Hello {{1}}, we confirm that your order {{2}} is on its way. We estimate it will arrive in {{3}}. We'll let you know as soon as it's with the delivery driver. Thanks for waiting!"
• If they want to cancel: "Hello {{1}}, we apologize for the delay and understand your decision. If you'd like, we can cancel your order {{2}} at no charge. We can also offer you a discount on your next purchase if you prefer to wait. What works best for you?"
• If they complain about the delay: "Hello {{1}}, you're absolutely right and we apologize. Order {{2}} is taking longer than expected due to {{3}}. We're doing everything we can to get it to you soon. We offer you a 10% discount on your next order as compensation. Does that sound good?"

How to know if the message worked?

The success of a delay notice is not measured in sales, but in retention. If the customer waits and doesn't cancel, the message has fulfilled its purpose. Look at three concrete signs:

First, the customer's response. If they reply with something like "thanks for letting me know" or "okay, I'll wait," that's a good sign. If they don't reply, that's also fine: they probably accepted the delay. If they cancel, the message didn't get through, but at least you avoided a later complaint.

Second, the order status. Did the customer pick up or receive the order without further complaints? That's success. Third, repetition: if the customer orders again, the template didn't scare them off. In Wando, you can see in statistics how many times each template was used and compare it with that day's cancellations.

Why Meta may reject this template (and how to fix it)

Meta reviews each template before approving it. The most common rejection reasons for this type of message are three.

First, requesting sensitive information. If you include variables like "card number" or "ID number," Meta will reject it. Second, promising something you can't fulfill, like "guaranteed delivery" or "never any delays." Third, using a promotional tone or adding links not related to the notice.

To fix it, review the text: make it purely informative, without exaggerated promises and without asking for personal data. Make sure the variables {{1}}, {{2}}, and {{3}} are well defined and that the message is clear. If it's rejected, Meta tells you the reason; adjust it and resubmit. Approval takes up to 48 hours.

Formal variant and casual variant: when to use each

The formal variant ("Dear {{1}}...") is for customers who don't have a close relationship with your brand, such as a corporate order or a first purchase. It also works if the customer is older or if the error was serious and you want to show professionalism.

The close variant ("Hi {{1}}!...") is for regular customers, delivery orders, or if your brand has a relaxed tone. It builds closeness and reduces tension faster.

The rule: if you don't know the customer, go with the formal one. If it's a customer who has already bought from you several times, use the close one. In Wando, you can load both variants and choose on the spot based on the conversation.

When to send this message (and when not to)

Timing makes all the difference. Send it as soon as you know the order will take longer than promised, not when the customer has already asked. If you wait for them to write to you, you're too late: the customer is already angry and the template loses its effect.

Don't send it if the delay is two minutes or if you're not sure it will actually happen. An unnecessary notice creates noise and distrust. Don't use it for orders that have already gone out either: in that case, send a shipping confirmation message, not an apology.

The rule is simple: if the delay exceeds 10-15 minutes and affects the experience, notify. If it's shorter or uncertain, wait. Customers value being notified in advance, not being asked for patience afterward.

What to reply when the customer responds (3 sample messages)

The customer may respond in several ways. The three most likely are: asking how much longer, canceling the order, or complaining. Here's a sample message for each, ready to copy and adapt.

• If they ask how much longer: "Hi {{1}}, we confirm that your order {{2}} is on its way. We estimate it will arrive in {{3}}. We'll let you know as soon as it's with the delivery. Thanks for waiting!"
• If they want to cancel: "Hi {{1}}, we're sorry for the delay and understand your decision. If you'd like, we can cancel your order {{2}} at no charge. We can also offer you a discount on your next purchase if you prefer to wait. What works best for you?"
• If they complain about the delay: "Hi {{1}}, you're absolutely right and we apologize. Order {{2}} is taking longer than expected due to {{3}}. We're doing everything we can to get it to you soon. We're offering you a 10% discount on your next order as compensation. Does that work?"

How do you know if the message worked?

The success of a delay notification isn't measured in sales, but in retention. If the customer waits and doesn't cancel, the message did its job. Here are three concrete signs:

First, the customer's response. If they reply something like "thanks for letting me know" or "okay, I'll wait," that's a good sign. If they don't reply, that's also fine: they probably accepted the delay. If they cancel, the message wasn't enough, but at least you avoided a later complaint.

Second, the order status. Did the customer pick up or receive the order without further complaints? That's success. Third, repeat purchases: if the customer orders again, the template didn't scare them off. In Wando, you can see in statistics how many times each template was used and compare that with cancellations for that day.

Why Meta might reject this template (and how to fix it)

Meta reviews every template before approving it. The most common rejection reasons for this type of message are three.

First, asking for sensitive information. If you include variables like "card number" or "ID number," Meta will reject it. Second, promising something you can't deliver, like "guaranteed delivery" or "never any delays." Third, using a promotional tone or adding links unrelated to the notification.

To correct it, review the text: make sure it is purely informational, without exaggerated promises and without requesting personal data. Make sure the variables {{1}}, {{2}} and {{3}} are well defined and that the message is clear. If it is rejected, Meta tells you the reason; adjust it and send it again. Approval takes up to 48 hours.

Formal variant and casual variant: when to use each

The formal variant ("Dear {{1}}...") is for customers who are not familiar with your brand, such as a corporate order or a first purchase. It also works if the customer is older or if the error was serious and you want to show seriousness.

The casual variant ("Hi {{1}}!...") is for regular customers, delivery orders, or if your brand has a relaxed tone. It builds closeness and reduces tension faster.

The rule: if you don't know the customer, go with the formal one. If it's a customer who has already bought from you several times, use the casual one. In Wando, you can load both variants and choose at the moment based on the conversation.