Skip to content
E-commerce & orders

WhatsApp chatbot template: delivery rescheduling

A failed delivery costs you the trip, the redelivery and the support conversation. Asking the day before turns all three into one tap.

8 nodes Built for: Retail, logistics, field service
8 nodes · E-commerce & orders

The goal

Confirm or move the slot before the van is loaded.

The flow, node by node

Message copy
  1. Send template

    Confirm tomorrow’s slot

    Utility — logistics on a paid order. Send it the evening before, not the morning of.

    Your delivery is scheduled for tomorrow between 11am and 2pm. Does that still work?

  2. Buttons

    Works / move it / change address

    Three taps covering everything that actually happens.

  3. HTTP request

    Fetch available slots

    From your own system, so the flow only offers windows a van can actually cover.

  4. List menu

    Offer the alternatives

    Real windows with real dates. "We will call you" is not an alternative.

  5. Ask for location

    Address change → ask for a pin

    A dropped location pin beats a typed address every time, particularly outside planned neighbourhoods.

  6. Set attribute

    Write the new slot or address

    And push it back to the courier system in the same run.

  7. Send template

    Confirm the change

    Repeat the new window back. An unconfirmed change is the same as no change.

  8. Hand off to a human

    Anything outside the slots → a person

    Someone travelling next week needs a human, not a longer list.

Where this usually goes wrong

  • Offering slots you cannot cover. One broken promise costs more than the failed delivery would have.
  • Sending it the morning of. The van is already loaded, so the tap achieves nothing.