At a regional delivery company handling furniture and appliance deliveries, the office phone rings most of the day with versions of the same question. Where's my delivery? Is it still coming today? Can the driver call when he's close? Each call means the dispatcher looks up the job, calls or messages the driver to ask where he is, and calls the customer back. Meanwhile, a recipient who wasn't told the window precisely enough goes out for an hour, the driver arrives to an empty house, and the job turns into a redelivery tomorrow.
The information these customers want already exists. The driver's app knows which stop he's on, the route plan knows what's next, and the vehicle's telematics know where it is. What's missing is a habit of telling the customer before they ask, and building that habit starts with operations.
This article covers what to get right in your status data and messaging rules, then what an automated update system does through the day with a typical driver app, transport management system and text messaging.
What status calls really cost
Status calls interrupt the people running the day. A dispatcher answering "where is it" questions isn't replanning around a breakdown or a late collection. Drivers who get called for their location are distracted, and if they answer while driving, it's a safety problem.
Failed deliveries are the more expensive consequence. A recipient who didn't know the window, wasn't home, or didn't leave access instructions turns one delivery into two, with the fuel, driver time and vehicle capacity that implies. For two-person deliveries of large items, a failed attempt is especially costly.
For business customers who use you to deliver to their own customers, the lack of updates reflects on them as well. Shippers notice which carriers keep their customers informed, and it comes up when contracts are reviewed.
Fix the data and the rules first
Make driver statuses reliable
Automated updates are only as good as the events behind them. Check that drivers consistently record the key statuses in their app: loaded, departed depot, arrived at stop, delivered, failed with a reason. If a third of deliveries are marked complete at the end of the day in a batch, any message triggered by those statuses will be wrong. Fixing this usually means making the app quicker to use and explaining to drivers what the statuses are now used for.
Decide how you'll estimate arrival
Arrival estimates can come from the planned route, live vehicle location, or both. Decide how precise you want to be and when. Many operators give a broad window the day before, narrow it on the morning of delivery, and only give a specific estimate once the driver is a stop or two away.
Get the right contact details
For deliveries on behalf of shippers, you need the recipient's mobile number and email, and permission to use them for delivery updates. Agree with each shipper what they'll provide and how messages should be branded, since some will want updates to appear in their name.
Write the event rules and messages
List the events that trigger a message, who receives each one (recipient, shipper or both), and the wording. Keep it to the moments that matter: the day before, the morning of, shortly before arrival, on delivery, and on failure or delay.
Agree a failed-delivery process
Decide what happens when nobody's home: how long the driver waits, whether a neighbor or safe place is allowed, and how redelivery is booked. The messages should explain this in plain terms.
What the automated version does
- The day before, the recipient gets a message with the delivery date and window, plus a link to confirm they'll be in, add access instructions such as a gate code or safe place, or rearrange if the day no longer works.
- On the morning, once routes are finalized, they get a narrower window based on their position in the route.
- As the driver approaches, when the driver is a set number of stops or minutes away, the recipient gets a message saying roughly when to expect them, with a tracking link that shows the vehicle's approach for that final stretch only.
- When delays happen, the system watches estimated arrival times against the promised windows. If traffic or an earlier job pushes a delivery outside its window, the recipient gets a revised time before the window passes, and the shipper sees it too.
- On delivery, the recipient and shipper get confirmation with the proof of delivery photo and the name of whoever signed.
- On failure, the recipient gets the reason and a link to rebook, and the shipper is notified with the same information.
- Replies are handled. When recipients reply with instructions ("please use the side entrance" or "my neighbor at number 12 can take it"), the system reads the message, attaches the instruction to the job in the driver's app, and confirms back. Anything it can't handle goes to the dispatcher.
- Calls get answers too. For customers who still phone, an automated receptionist can look up the job by phone number or reference and give the current status, leaving dispatchers for the calls that need them.
The AI parts are the reading and writing. Interpreting free-text replies, matching them to the right job and turning them into clear driver instructions saves a lot of back-and-forth. The event triggers and timing stay rule-based, so customers get consistent messages.
Our proactive client updates system handles this for delivery and service businesses, and the logistics and transport page shows how it fits with dispatch, invoicing and compliance tracking.
A worked example
Take the furniture and appliance delivery company from the opening, running eight two-person crews. Say a week of logging status calls shows that a large share come from recipients asking for a time on the day. The company first tightens driver statuses, making the arrival and delivered taps quick in the app, and then switches on the message sequence. The evening before, a recipient gets a four-hour window and adds a note that her building's service elevator needs booking, and the note appears on the crew's run sheet. On the morning, the window narrows to two hours. When the crew is two stops away, she gets a message with a tracking link. An earlier delivery runs long, so her estimated time slips past the window, and she gets a revised time twenty minutes before the window would have been missed. The dispatcher spends the morning dealing with a vehicle problem instead of answering the phone.
What to watch out for
- Overpromising on precision. An exact time that turns out wrong annoys people more than an honest window. Narrow the window as the day progresses, and send a revised time the moment a delay is likely.
- Too many messages. Five or six messages for a single delivery is about the limit. More than that and recipients start ignoring the one that matters.
- Location privacy. Share the vehicle's live position only for the final approach to a stop, and never the driver's personal details beyond a first name.
- Driver safety. Instructions from recipients should appear in the driver's app when the vehicle is stopped, so nobody is reading messages at the wheel.
- Use of recipient data. Contact details provided for delivery should be used for delivery updates only, under whatever data protection rules apply where you operate. Agree this with shippers in writing.
- Shipper branding and preferences. Some shippers want messages in their name and style, some want none sent at all. Make it a per-shipper setting.
How to tell whether it's working
Count status calls for a week before launch and again a month after, and compare. Track failed deliveries and their reasons, since nobody-home and no-access failures are the ones updates should reduce. Measure how often deliveries land inside the promised window, and how often a revised time was sent before a window was missed. Watch replies from recipients too: the share handled automatically and the share that needed a dispatcher. Shipper feedback is worth asking for directly, since visibility is often part of how they judge carriers.
Where to start this week
For one week, have the office tally every status call: who called, what they wanted, and how long it took to answer. Alongside that, pull a sample of last week's jobs and check how many had complete, correctly timed driver statuses. Those two numbers tell you how big the problem is and whether your data can support automated updates yet.
Then write the five messages described above in your own voice and agree the event rules with your dispatchers. Once driver statuses are reliable, connecting them to text and email is a fairly contained piece of work, and the phone starts ringing for problems instead of questions you could have answered in advance.
If you'd like a quick read on where customer updates sit among the other jobs worth automating in your operation, run the free PATH report on your website. To talk through your own setup, book a call.