AI agents for logistics and delivery
For logistics and delivery teams, RoutMe lets an AI agent answer tracking questions from the shipment record, offer real reschedule windows and capture delivery instructions, on WhatsApp or website chat. The flow saves each change before confirming it, and customers who reject every window go to dispatch.

The customer journey, stage by stage
At each stage: what the customer asks, what the agent reads, what the flow decides and where the conversation happens. Sample questions are illustrative.
- Customer asks
- “When will my parcel be collected?”
- Agent reads
- The pickup booking for the shipment.
- Flow decides
- Updates you start use approved WhatsApp templates.
- Channel
- WhatsApp.
- Customer asks
- “Where is my parcel?”
- Agent reads
- The latest scan and delivery attempts.
- Flow decides
- No match on the tracking number asks again, then hands off.
- Channel
- Website chat on the tracking page, or WhatsApp.
- Customer asks
- “Nobody's home tomorrow. Can you come Friday?”
- Agent reads
- Open windows for the address.
- Flow decides
- The new window is saved before it is confirmed.
- Channel
- WhatsApp, from the exception notice.
- Customer asks
- “Can you leave it with the building desk?”
- Agent reads
- The delivery record and its notes.
- Flow decides
- A flow action saves the instruction for the driver.
- Channel
- Same thread.
- Customer asks
- “The box arrived damaged.”
- Agent reads
- The proof of delivery and shipment details.
- Flow decides
- Damage claims always go to a person.
- Channel
- Same thread, with a person.
Go live in 5 steps
The same five steps on every build. Most of the work is deciding what the agent may read and where a person takes over.
- 1
Connect your systems
Connect the shipment and routing systems as read-only tools, and give the flow a write action for new windows and notes.
- 2
Draw the flow with an agent node
Start from a template or a blank canvas. Fixed steps hold the rules that must never vary, and one agent node takes the open-ended turn.
- 3
Set what the agent may read
Attach only the tools that node needs and add your policies as knowledge sources. Read-only is the usual start, and writes run as flow actions you guard.
- 4
Test in the dashboard
Ask real questions before customers do, and read every tool call and branch in the run log. There is no separate test mode, so tests use your live connections.
- 5
Switch on the channel
Paste the chat widget snippet on your site, connect a WhatsApp Business number through Embedded Signup, or both. The same flow runs on each.
Related guides
- How to reduce WISMO ticketsCut where-is-my-order tickets with proactive status updates, easy tracking and a read-only assistant that answers from live order data.
- WhatsApp message templates and approvalWhatsApp templates are pre-approved messages for reaching customers outside the 24-hour window. See the categories, how review works and why they fail.
- AI chatbot for banking and fintech: what to allowHow to scope AI chat in banking and fintech: approved informational answers, strict verification, no advice, auditable lookups and fast handoff.
Frequently asked questions
Can a delivery chatbot reschedule a failed delivery?
Yes. The agent offers windows read from your routing system, and a flow action saves the chosen one before the customer is told it is confirmed.
Can we message customers on WhatsApp when a delivery fails?
Yes, with an approved template and the customer's opt-in. Once they reply, the 24-hour customer service window opens.
Does the AI agent talk to drivers?
No. It talks to customers. Instructions it collects are saved to your system by a flow action, where your drivers already see them.
Try it on your own data
Connect one system, draw the flow and test it in the dashboard first.