Skip to main content

Vive is now RoutMe. Same product, same team, new name. Read more

Delivery rescheduling chat

Delivery rescheduling chat lets a customer move a delivery in a conversation instead of a phone call. With RoutMe, the agent reads open windows from your routing or scheduling system, the flow writes the chosen window back and confirms only if that write succeeded, and a customer who rejects every option goes to dispatch.

Illustrative runWhatsApp
  1. Customer

    Nobody's home tomorrow. Can you come later in the week?

  2. Listed open windowsAgent

    slots.list → Thu 10am to 1pm · Fri 2pm to 6pm

  3. Agent

    I can do Thursday 10am to 1pm or Friday 2pm to 6pm. Which works?

  4. Customer

    Friday.

  5. Saved the new windowFlow

    delivery.update → Write succeeded · confirm

  6. Agent

    Done. Your delivery is now Friday between 2pm and 6pm, same address.

Sample data. In production every value comes from a live lookup in your own systems, and every step is logged.

How it works, concretely

Four questions decide whether this works: what the agent can see, which rules it cannot bend, where the customer is, and when your team steps in.

  1. 01

    What the agent reads

    The shipment and the open delivery windows for that address, from your routing system or delivery database, through read-only tools.

  2. 02

    What the flow decides

    Whether a window was accepted. The flow saves it first and confirms only after the save succeeds, so nobody is promised a slot that failed to write.

  3. 03

    Where it runs

    WhatsApp, started from a delivery exception, and website chat on the tracking page. Voice (IVR) is on the roadmap.

  4. 04

    When a person takes over

    A customer who turns down every window, or an address outside the route, goes to dispatch with the shipment attached.

Set it up

  1. 1

    Expose windows read-only

    A tool returns the open delivery windows for one shipment and address.

  2. 2

    Connect the write-back action

    The confirm action saves the new window in your system. The flow confirms to the customer only after it returns success.

  3. 3

    Trigger from the exception

    Start the conversation from a failed-attempt or delay event, or let customers start it with a message.

  4. 4

    Set the dispatch handoff

    Choose where unplaceable cases go, then test a full reschedule end to end.

What you need first

  • A routing or delivery system with an API for windows and updates
  • An approved WhatsApp template if you message customers first
  • A dispatch queue for cases the flow cannot place

Frequently asked questions

Can an AI agent reschedule a delivery by itself?

No. The agent offers windows it read and records the customer's choice. A flow action writes the change, so the confirm-only-after-saving rule applies every time.

Can I message customers on WhatsApp after a failed delivery?

On WhatsApp, yes, with an approved template and the customer's opt-in. Once they reply, the 24-hour customer service window opens and the conversation continues freely.

Try it on your own data

Connect one system, start from a template and test it before a customer sees it.