Profile
The plan shows what should happen. What actually happens is in the driver's head, and only comes out when someone calls.
The Delivery Status Assistant asks for a status update at agreed moments, processes the reply and passes any deviation to planning and customer service.
The aim is not to check up on the driver. It is to make sure planners and customer service know what is going on while there is still time to act.
What it does, step by step
- Load the routesFrom the plan: addresses, time slots and the assigned driver.
- Ask for a statusAt agreed moments, through the channel the driver already uses.
- Process the replyA delay, a hold-up at the unloading point or a successful delivery is recognised and recorded.
- Pass on deviationsPlanning and customer service are told, with the new expected time.
- Inform the customerOnly if you want it to, and with the message you have agreed.
Works with these systems
- Databases
- ERP
- APIs
Zendesk
HubSpot- Freshdesk
Is your system not listed? We can connect any system, even if there is no standard integration. View all integrations.
What runs automatically and what does not
You stay in control.
Not every decision should be made automatically. For each workflow, we set out:
- What can happen automatically.
- What is put forward for approval first.
- When a person is brought in.
- What information is stored.
- How actions are logged.
Is this a fit for your organisation?
A good fit if
- Transport companies and delivery services with their own drivers.
- Organisations where the planner currently phones round for updates.
- Situations with fixed delivery slots that customers rely on.
Less of a fit if
- Routes already fully covered by on-board computers and telematics: the data is already there.
- Very small fleets where the planner talks to everyone anyway.
What it can deliver
- Delays known before the customer calls.
- Less planner time spent phoning round for status.
- A consistent picture of what goes wrong on the road, instead of anecdotes.
Directions, not promises. As soon as there is evidence from a client project, it will appear here as a substantiated result.
Frequently asked questions
How does an AI employee stay in touch with drivers on the road?
Through the channel they already use, usually WhatsApp or an app on their phone. Short questions at agreed moments, not a form to fill in while driving.
Isn't this just monitoring the driver?
That depends on how you set it up, and it is a conversation to have with your drivers before you start. Our advice: ask about the status of the route, not the person, and use it to inform planning and customer service, not to hold someone to account afterwards.
Does this work with our transport management system?
Yes, through the API or a database integration. The routes come from your planning; what the assistant adds is the actual status on the road.
Can the customer be notified automatically about a delay?
Yes, and that is often the biggest gain. We do recommend agreeing the message in advance and setting a threshold: for a ten-minute delay you do not want to bother anyone, for two hours you do.
What happens if a driver does not reply?
After an agreed time, the planner gets a signal. No reply is information in itself, and usually on exactly the routes where something is wrong.
How to put this to work
- 1A short callTogether we look at your process and your systems, and whether this task is the best place to start.
- 2Set up on your rulesIntegrations with your own systems, and agreeing what may run automatically and what a person approves.
- 3Measure and adjustFirst alongside your team, only then on its own. We look at what it delivers and adjust.