Delivery reschedule automation that beats phone tag with customers

Updated 2026-09-19 · 4 min read · By the Convo360 team

The cost of a failed delivery attempt

Every failed delivery, nobody home, wrong address, customer refused COD amount, usually means a phone call from an agent, often unanswered, followed by a guess at when to reattempt. For a courier operation running out of Nagpur or Indore with thousands of daily deliveries, this manual follow-up is expensive and slow.

A WhatsApp message reaches the customer far more reliably than a phone call, and it lets them respond on their own time.

The knock-on cost is worth naming too: a failed attempt that sits unresolved for a day or two often becomes a second failed attempt, since nobody actually confirmed the new date with the customer. They just guessed one internally and tried again. Each repeat failure adds a full delivery run's cost with nothing to show for it.

Triggering on the failed attempt

When your delivery app or logistics system marks an attempt as failed, an inbound webhook passes the order ID and reason straight into a Convo360 flow. Within moments, the customer gets a WhatsApp message explaining what happened and offering next steps, no agent needs to notice the failure first.

The webhook payload should carry the failure reason as a structured field, not just a free-text note from the delivery agent: "not home", "wrong address", "customer refused" and "area inaccessible" each need a different flow branch. A Condition block on this field decides whether the customer sees reschedule buttons, an address-correction question, or a different message entirely for a refused COD parcel.

Reschedule buttons and address correction

The flow offers 2-3 upcoming delivery slots as Buttons, so the customer taps rather than types. If the failure reason was an incorrect address, an Ask a Question block collects the corrected address and stores it with Set Variable before the reschedule confirmation.

• Button 1: Tomorrow, 10 AM-1 PM
• Button 2: Tomorrow, 4 PM-7 PM
• Button 3: I'll call to arrange

The opening message matters as much as the buttons: lead with what happened, not an apology-heavy paragraph. "We attempted delivery of your order at 2:15 PM today but couldn't reach you. When should we try again?" is clearer than a generic "sorry for the inconvenience" that buries the actual question.

COD confirmation for high-value parcels

For cash-on-delivery orders above a set value, adding a confirmation step before the next attempt reduces refusals at the door. A simple "Confirm you'll pay ₹1,450 cash on delivery for your order tomorrow. Reply Yes or Cancel" with Yes/Cancel buttons, sent a day before the reattempt, catches order mismatches early rather than at the doorstep.

A useful edge case to plan for: if the customer replies Cancel, route this straight to a human agent rather than simply marking the order cancelled, since sometimes a Cancel reply actually means "wrong amount" or "I already returned this", and only a person can tell the difference safely.

Building it on Convo360

1. Set up an inbound webhook trigger that your logistics system calls on a failed-delivery event, passing order ID, customer number and reason.
2. Add a Buttons block with reschedule slot options.
3. Branch with Condition: if the customer selects a slot, confirm and update your system via an HTTP/API request block; if they choose "correct address", collect it with Ask a Question.
4. For COD orders, add a separate flow triggered a day before reattempt with a Yes/Cancel Buttons block.
5. Log every reschedule to your CRM or Sheet via the Google Sheets or Save CRM lead block.

Reference: webhooks docs, Flow Builder docs.

Set a timeout on the whole sequence too. If the customer hasn't responded to the reschedule buttons within, say, 24 hours, a Wait / Delay block can trigger one follow-up nudge before the case is handed to a human dispatcher rather than left open indefinitely with a delivery slot silently unbooked.

Repeated failures and what to measure

A single delivery address that fails three or more times in a row is a different problem than a one-off missed attempt: usually a genuinely wrong address, a customer who no longer wants the order, or a serviceability gap. Add a Condition block that flags any address past its second failure for manual review instead of letting the flow keep offering the same three buttons indefinitely.

Two numbers are worth tracking in Analytics: what share of failed-delivery messages get a reschedule response within 24 hours, and how the second-attempt success rate compares for addresses that went through the automated reschedule flow versus ones that didn't. A gap between the two tells you whether the automation is actually preventing repeat failures or just adding a message on top of the same manual process.

What it costs

Webhook-triggered flows and buttons are available from the Starter plan (₹999/month, ex-GST). If you also want an AI voice call to confirm reschedules for customers who don't respond on WhatsApp, that needs the Pro plan (₹2,999/month, ex-GST) and a connected telephony account such as Exotel or Plivo, billed to you directly at their published per-minute rate with no markup added by Convo360.

Example conversation

Frequently asked questions

Related reading

Available across India — see WhatsApp & AI calling automation by state and city.