A failed-delivery WhatsApp message should say which order was affected, why delivery failed, what the customer needs to do, and the deadline for replying. Keep the action simple. Effective WhatsApp marketing for ecommerce treats a delivery exception as a service message, not an excuse to add a promotion.
A practical message is: “We could not deliver order {{1}} today because {{2}}. Please reply with 1 to retry on {{3}}, 2 to update the address, or 3 to speak with support. Reply by {{4}} to prevent the parcel from being returned.” Use only verified order details and never ask for payment card data in chat.
Quick answer: what must a failed-delivery message include?
- The store name and recognizable order reference
- A plain-language reason for the failed attempt
- The next available delivery, pickup or support options
- One clear response method, ideally quick-reply buttons
- An honest deadline before the carrier returns the parcel
- A safe support path for address, payment or identity questions
Do not write “delivery failed” and leave the customer to investigate. The message should complete the next step or collect the minimum information needed to complete it.
Template 1: general failed-delivery message
Hi {{1}}, we could not deliver your {{2}} order {{3}} today because {{4}}.
Choose the next step:
1. Retry delivery on {{5}}
2. Update delivery details
3. Speak with supportPlease reply by {{6}} so the parcel is not returned to us.
Use this only when the reason and options come from the carrier or fulfillment system. If the cause is unknown, say that the carrier recorded an unsuccessful attempt and avoid inventing a reason.
Template 2: customer was unavailable
Hi {{1}}, the courier attempted delivery of order {{2}} at {{3}}, but no one was available to receive it.
We can request another attempt on {{4}}. Reply YES to confirm, CHANGE to choose another available day, or HELP for support. Please respond by {{5}}.
Do not blame the customer. “No one was available” is neutral and describes the recorded outcome. Include the attempt time only when it is reliable.
Template 3: incomplete or incorrect address
Hi {{1}}, delivery of order {{2}} is paused because the courier could not confirm part of the address.
Please use this secure link to review the delivery details: {{3}}
For your security, do not send payment details or identity documents in this chat. Update the address by {{4}}, or reply SUPPORT for help.
Use a secure authenticated page for sensitive address changes, especially after dispatch. A WhatsApp reply can begin the process, but the store should verify identity before changing a high-value order’s destination.
Template 4: cash-on-delivery customer did not have payment
Hi {{1}}, the courier could not complete delivery of cash-on-delivery order {{2}} today.
The amount due is {{3}}. We can request another attempt on {{4}}. Reply RETRY to confirm or SUPPORT if you need to discuss the order. No payment is requested through this message.
State the exact amount already attached to the order, and do not add a payment link unless it is an approved option in your verified workflow. The customer should not have to guess whether the message is genuine.
Template 5: delivery was refused
Hi {{1}}, the courier marked order {{2}} as refused at delivery.
If this was a mistake or you still want the parcel, reply RETRY by {{3}}. If you intended to cancel, reply CANCEL. We will confirm the final status before taking further action.
A refusal scan can be wrong or made by someone else at the address. Confirm intent before canceling, refunding or scheduling another chargeable attempt.
Template 6: access problem at an apartment, office or gated address
Hi {{1}}, the courier could not access the delivery location for order {{2}}.
Please reply with the safest option:
ACCESS: add gate, reception or building instructions
CALL: ask the courier to call on arrival
PICKUP: view available collection optionsReply by {{3}} so we can prevent a return.
Do not request door codes in a broad shared inbox. Route sensitive access instructions through the carrier’s secure delivery-management page where possible.
Template 7: pickup-point alternative
Hi {{1}}, we were unable to deliver order {{2}}. It can be held at {{3}} until {{4}}.
Pickup address: {{5}}
Hours: {{6}}
Required at pickup: {{7}}Reply PICKUP to choose this option or RETRY for another available delivery attempt.
Include only a pickup point the carrier has actually confirmed. State the collection deadline and identification requirement accurately.
Template 8: weather or carrier disruption
Hi {{1}}, delivery of order {{2}} could not be completed because of {{3}} affecting the carrier network.
No action is required right now. The revised delivery estimate is {{4}}. We will message you again if that changes. Reply HELP if the order is time-sensitive.
When the customer cannot fix the problem, do not ask for a reply merely to increase engagement. Give the new expectation and an escalation route for urgent cases.
Template 9: final reminder before return to sender
Final delivery reminder for order {{1}}: we need your response by {{2}} to arrange another attempt or pickup. After that time, the carrier may return the parcel to us.
Reply RETRY, PICKUP or SUPPORT. We will confirm your choice before the deadline.
Use “may return” unless the carrier status guarantees the event. Avoid fake urgency and make the deadline reflect the actual operational cutoff.
Template 10: return to sender has started
Hi {{1}}, order {{2}} is now being returned to us after unsuccessful delivery attempts.
We cannot promise another delivery from the current parcel. Once the return is confirmed, we can explain the available resend or refund options under your order terms. Reply SUPPORT to open the case with the delivery history attached.
Do not promise an immediate refund before checking the order, payment method, condition of returned goods and applicable consumer rights. Give a specific update time after the return is scanned.
How should the message change by failure reason?
| Failure reason | Best customer action | Avoid |
|---|---|---|
| Customer unavailable | Confirm retry date | Blaming language |
| Address incomplete | Securely correct details | Collecting sensitive data in chat |
| Access restricted | Add instructions or choose pickup | Requesting public door codes |
| COD payment unavailable | Confirm amount and retry | Unverified payment requests |
| Carrier disruption | Wait for revised estimate | Unnecessary response demand |
| Parcel nearing return | Choose retry, pickup or support | Invented deadlines |
Should this be a WhatsApp utility template?
A delivery update tied to a specific existing order is normally operational rather than promotional. On the WhatsApp Business Platform, business-initiated messages can require an approved template depending on the conversation state and platform rules. Keep the wording specific to the transaction and remove coupons, cross-sells and unrelated marketing.
Meta’s official WhatsApp Business Platform collection shows that templates can contain body variables, quick replies and call-to-action buttons. See the Meta template API collection. Twilio’s documentation also recommends descriptive template names that make the utility purpose clear in the template approval workflow.
Rules, categories, pricing and delivery behavior can change. Check the current WhatsApp Business Platform requirements and your provider’s implementation before launching automation.
How do you make the message trustworthy?
- Use the verified business identity customers already recognize.
- Include a partial order reference, not unnecessary personal data.
- Match the carrier event and timestamp in the order system.
- Use a branded HTTPS domain for action links.
- Never request passwords, one-time codes or full card details.
- Provide a visible path to ecommerce customer service.
- Confirm every chosen action in a follow-up message.
WhatsApp’s published Business Messaging Policy requires businesses to follow applicable law, respect requests to stop contact and protect information. Consent and data-handling requirements should be built into the workflow, not added after complaints.
Which quick-reply buttons work best?
Use actions the system can fulfill: Retry delivery, Update details, Choose pickup and Talk to support. Limit the initial set to the two or three most likely paths. A button labeled “Fix delivery” is vague; “Retry Tuesday” is concrete.
After a button tap, confirm the result: “Retry requested for Tuesday. We will send confirmation when the carrier accepts it.” A button tap is not the same as a completed carrier booking.
How should the automation handle no response?
Send one reminder only when the parcel is genuinely approaching a carrier cutoff. Change the copy to show the deadline and consequence. Do not send identical messages every few hours. If WhatsApp remains undelivered or unread, use the customer’s permitted fallback channel, such as SMS or email, and record that channel switch.
Measure customer response rate, successful re-delivery rate, time to resolution, return-to-sender rate, opt-outs and support escalations by failure reason. The goal is recovered delivery, not message volume.
Failed-delivery automation checklist
- Trigger only from a verified carrier exception.
- Map each carrier code to plain customer language.
- Suppress marketing content and unrelated offers.
- Offer actions the fulfillment system can complete.
- Protect address and payment changes with verification.
- Include real deadlines and business hours.
- Escalate repeated failure or customer frustration.
- Stop reminders after resolution, cancellation or return.
FAQs
How soon should you send a failed-delivery WhatsApp message?
Send it after the carrier records a reliable exception and the next options are known. A fast but inaccurate message creates more support work.
Should the message include a tracking link?
Yes, when the link uses the verified carrier or a branded secure tracking page. Do not use shortened or unfamiliar domains that can look suspicious.
Can you ask the customer to update their address on WhatsApp?
You can start the request, but sensitive or high-risk address changes should use identity verification and a secure workflow. Do not collect unnecessary personal data in chat.
How many failed-delivery reminders should you send?
Usually one initial message and one deadline-based reminder are enough. Stop when the customer responds, the parcel status changes or the order enters return processing.
Should a failed-delivery message contain a discount?
No. Keep the message focused on resolving the existing order. A promotion can confuse template classification, reduce trust and distract from the required action.
Leave a Reply