Platform
Chatbot Builder Bulk Messaging Team Inbox Mini CRM API & Webhooks AI Integration WhatsApp Flows
Industries
E-commerce & D2C Real Estate Education Healthcare Finance & BFSI Logistics Hospitality Retail
Integrations 📚 Learn 🗂 Codex Compare Pricing About Contact Start Free Trial →

WhatsApp Failed Delivery Rescheduling — Rescue 58% of NDR Shipments

Every NDR that silently becomes an RTO costs you ₹150–300 in reverse logistics. Most can be saved with one well-timed WhatsApp message sent within 60 minutes of the failed attempt. The math is simple — the execution just needs automation.

Rescue My NDRs → Talk to an Expert
58%
NDR rescue rate with WhatsApp vs 22% by phone
60 min
Critical window — message must fire within 1 hour
₹200
Average RTO cost saved per rescued shipment
Zero
Manual effort needed per NDR with automation

4 NDR causes — and the WhatsApp response for each

NDR reason% of NDRsWhatsApp responseRescue rate
Customer not available at address42%Rescheduling message with time slot options65%
Wrong or incomplete address28%Address correction flow via WhatsApp Flows72%
Customer refused delivery (COD)18%Prepaid conversion offer + reschedule38%
Access issue (gated community, locked)12%Pickup point alternative or specific instructions55%

The window closes fast: NDR rescue rate is 60%+ within the first hour. It falls to 35% at 6 hours and under 20% at 24 hours. This is why automation is essential — no human team can respond to every NDR within 60 minutes at scale.

Complete NDR rescheduling automation flow

NDR rescue flow
T
Courier raises NDR event
Webhook from Shiprocket / Delhivery / Ecom Express
A
WhatsApp rescheduling message (within 60 min)
"We tried to deliver but couldn't reach you"
?
Customer response?
A
Retry today → pass instruction to courier
A
Tomorrow → courier reschedule instruction
A
Change address → collect new address via chat
?
No response after 6 hours?
A
Second nudge (more urgent)
"Your order will be returned in 24 hours if unreachable"
!
3rd attempt failed → RTO initiated — notification sent

The NDR rescue timeline

Within 60 min of NDR
First rescheduling message
The golden window. Customer remembers the missed delivery, is likely still near their phone, and has the highest intent to resolve. 58–65% rescue rate in this window.
+6 hrs (if no response)
Urgent follow-up
More direct tone: "Your order will be returned if we can't reach you." Reschedule rate drops to 30–35% at this point but is still worth sending.
Before 3rd attempt
Final warning message
"This is our last delivery attempt. After this, your order will be returned." Creates urgency. Some customers who ignored the first two messages act on this.
On RTO initiation
RTO notification
Tell the customer their order is being returned. Include refund timeline for prepaid. For COD — nothing to refund but confirm the order is cancelled. Transparency reduces support calls.
Never after 10 PM
No late-night NDR messages
If an NDR fires at 9 PM, queue the WhatsApp message for 8 AM the next morning. A 10 PM "your delivery failed" message at night is jarring and unnecessary.
COD: offer prepaid at NDR
Prepaid conversion window
A COD customer who refused delivery is a prime prepaid conversion target. Include a "switch to online payment and we'll redeliver tomorrow" option. 18% of COD refusals convert to prepaid this way.

NDR rescue results from logistics partners on WA.Expert

MetricManual / call centreWhatsApp automatedChange
NDR rescue rate (overall)22%58%+164%
NDR rescue rate (within 1 hr)62–65%Best window
RTO rate (net)Baseline−35%−35%
Address correction success rate45% (phone)72% (WhatsApp flow)+60%
COD-to-prepaid conversion at NDR0%18%New revenue
Monthly savings on reverse logistics₹25K–₹2L/monthDepends on volume

5 NDR rescheduling mistakes to avoid

Sending NDR message after 6+ hours
Manual NDR management means teams review reports at the end of the day — firing rescheduling messages 6–12 hours after the failed attempt. By then, the rescue window is mostly closed.
Fix: Automate via courier webhook. WA.Expert fires the message within 60 minutes of any NDR event — 24/7, no manual intervention.
No option to change address
28% of NDRs are caused by wrong addresses. Offering only "retry today" or "tomorrow" as options doesn't solve the problem for these customers — their order will fail again.
Fix: Always include "change delivery address" as a fourth option. Collect the new address via WhatsApp Flows and route to ops for update.
Initiating RTO without customer notification
Customer finds out their order was returned when it never arrived and they check tracking a week later. This is the worst customer experience in ecommerce.
Fix: Always send an RTO initiation message explaining why, when it'll be returned to the seller, and how the refund will be processed.
Not passing instructions to the courier
Customer reschedules via WhatsApp. Nothing happens on the delivery side because the courier wasn't told. Customer waits all day, order doesn't come. Trust destroyed.
Fix: WA.Expert pushes rescheduling instructions directly to courier APIs (Shiprocket, Delhivery, Ecom Express) the moment the customer responds.

WhatsApp NDR rescheduling — common questions

What is NDR in logistics?
NDR (Non-Delivery Report) is raised by the courier when a delivery attempt fails. The most common reasons: customer not available (42%), wrong address (28%), customer refused delivery (18%), and access issues like locked gates (12%). WhatsApp rescheduling directly addresses the first three.
How quickly should I send a WhatsApp message after an NDR?
Within 60 minutes of the NDR being raised. NDR recovery rate is 58–65% within the first hour. This drops to 35% at 6 hours and under 20% at 24 hours. Speed is everything in NDR recovery — automation is the only way to achieve this at scale.
What rescheduling options should I offer?
Offer 4 options as quick-reply buttons: retry today after a specific time, reschedule to tomorrow, change delivery address, and nearest pickup point. The more options you offer, the higher the rescue rate. Make all options available as single-tap buttons — not typed responses.
Can the customer change their delivery address via WhatsApp?
Yes — when a customer selects change delivery address, WA.Expert collects the new address via a WhatsApp Flows form and routes it to your operations team or directly to the courier API for update. This is critical for the 28% of NDRs caused by wrong addresses.
How many rescheduling attempts before auto-RTO?
Standard practice: 3 delivery attempts total. After the first NDR — WhatsApp rescheduling. After the second NDR — more urgent WhatsApp + call attempt. After the third NDR — final warning message, then RTO. Going beyond 3 attempts increases logistics cost beyond the value of rescue.
Does this work for COD orders?
Yes, and it's even more important for COD. The WhatsApp NDR message should acknowledge the missed payment and offer to reschedule at a specific time when the customer confirms availability. You can also use this as a prepaid conversion opportunity — 18% of COD refusals convert to prepaid when offered the option in the NDR message.
How do I pass rescheduling preferences to the courier?
WA.Expert integrates with courier APIs (Shiprocket, Delhivery, Ecom Express) to pass instructions directly. For couriers without API rescheduling, WA.Expert creates a task in your operations inbox with all details for your team to action manually.

More logistics WhatsApp automation guides

Ready to rescue 58% of your NDR shipments?

Connect your courier webhook and automate NDR rescheduling in under 2 hours. Save ₹200 per rescued shipment.

Start Free Trial → Talk to an Expert