Tell customers about delays
before they ask.
Shipment ETA automation watches your tracking and telematics data, works out when a delivery will actually arrive and messages the customer when the time changes enough to matter. Routine updates go out automatically. Bad news, such as a missed day or damaged goods, is drafted for a person to approve first.
What does proactive ETA messaging do?
Most “where is my delivery?” calls are about one thing: the customer does not know the delivery is late until it is late. Proactive updates send the information first. The customer hears about the delay at 10am, not at 4pm when the goods have not arrived.
This is different from order status updates, where the customer asks and the agent answers. Here, the system decides when to speak. That needs rules, because too many messages are as bad as too few.
Is shipment ETA updates a job for an agent?
Tick what is true of your shipment eta updates work.
Tick the statements that apply and the suggestion appears here: an AI agent, ordinary automation, or a person with software support.
Which data does it need?
| Source | What it gives | Common problem |
|---|---|---|
| TMS or route plan | Planned stops, sequence and booked windows | Changes on the day are not always saved |
| Telematics (GPS) | Vehicle position and speed every few minutes | Shows the vehicle, not which drop is next |
| Driver app | Arrived, delivered, failed, with times | Drivers update late or in batches |
| Routing service | Drive time from current position to the next stops | Needs a sensible time per stop added |
| Subcontractor tracking | Status events from a pallet network or carrier | Often hours behind; formats vary |
A simple ETA is the current position, plus drive time to the customer, plus the remaining stops before it multiplied by your average time per stop. This is often good enough. The bigger risk is stale data. If the last driver update is two hours old, the system must say so, or hold the message.
Driver location is personal data. Use it to calculate an ETA, but do not send customers a live map of a driver’s position unless drivers have been told and it is needed. A time window is usually enough.
When should the system send a message?
Write the rules down before the build. A starting set, to adjust for your customers:
| Event | Trigger | Sent by |
|---|---|---|
| Out for delivery | Vehicle leaves the depot with the order on board | Automatic |
| Window narrowed | ETA is stable and within the booked window, about 1 hour before | Automatic |
| Running late | ETA moves outside the booked window by more than 30 minutes | Automatic, with a new time |
| Missed today | Delivery will not happen on the booked day | Drafted; a person approves |
| Failed or damaged | Driver records a failure, refusal or damage | Drafted; a person approves |
| Back on time | A late ETA recovers to inside the window | Automatic, once only |
- Send at most one change message per hour per delivery. Do not report each small change in the ETA.
- Do not message after a set time in the evening. Hold the update until the morning, unless the delivery is that night.
- Stop all messages for a delivery once it is marked delivered or a person takes over.
- Let business customers choose: every update, delays only, or a daily summary.
How much time could shipment ETA updates give back?
Put your own numbers in.
The starting values are an illustrative example, not a benchmark or a neu figure. Use your own volume, the time each one takes today and the share you expect the system to handle without a person.
Time saved is only part of the case: response times, missed work and errors matter too. The ROI guide covers how to set a baseline, and the cost guide what the build and running costs include.
Why should a person approve bad news?
A missed delivery day can stop a building site or empty a shop shelf. The message needs a new date you can actually meet, sometimes an apology and sometimes a phone call instead. An automated system does not know that this customer was promised a priority slot last week.
The system drafts the message with the facts: order, original window, reason code, the next available slot. A planner checks it, edits if needed and sends it. This usually takes under a minute, and it keeps the decision with someone who knows the customer. The human-in-the-loop guide covers how to set these approval points.
Which channel should carry the updates?
| Channel | Good for | Watch out for |
|---|---|---|
| Consumers and site contacts who reply with questions | Messages outside the 24-hour service window must use an approved template; each delivered template message is charged | |
| SMS | One-way updates to any mobile, with no app needed | No rich content; replies are harder to handle |
| Business customers, and updates with documents attached | Read late; not suited to “arriving in 20 minutes” |
Meta charges WhatsApp Business Platform messages per delivered template message. From 1 October 2026, utility templates sent inside the customer service window are also charged, where they had been free since July 2025. Check current rates for Ireland in our WhatsApp pricing guide before you choose a channel per message type.
When a customer replies (“can you leave it with the neighbour?”), the reply must reach a person or an agent that can act on it. A one-way update that cannot handle replies creates new work.
How do you know it is working?
Track a few numbers from the first week. They show whether the updates help customers or only add messages.
| Measure | What it tells you |
|---|---|
| Deliveries inside the window you sent | Whether your ETA is good enough to send at all |
| Inbound “where is it?” calls per 100 deliveries | Whether customers stop calling, the main aim |
| Messages per delivery | Whether the rules are too noisy; most deliveries should need one or two |
| Replies needing a person | The new work the updates create |
| Time to approve bad-news drafts | Whether the approval step is fast enough to be useful |
| Opt-outs | Whether customers find the messages useful |
Review late deliveries that got no warning each week. Each one points to a gap: a missing status, a stale driver update or a rule that did not fire.
Where should you start?
First, check your data. For two weeks, compare the time the driver app says each drop was delivered with the ETA you would have sent an hour before. If the error is large, fix the data and the stop-time estimate before you message anyone. Then start with one message type, usually “running late”, for one depot. Add the others once customers and planners trust it. The WhatsApp agents page covers two-way conversations once updates are running.
Common questions
Do we need telematics for this?
Not always. A driver app that records arrived and delivered times, plus the route plan, gives enough for a reasonable ETA on multi-drop routes. GPS improves accuracy on long legs and shows when a vehicle is stuck. For subcontracted deliveries, you depend on the carrier’s tracking events, which are often less frequent.
How accurate does the ETA need to be?
Accurate enough that the customer can plan around it. For most deliveries, a one or two hour window that holds is better than a precise time that keeps moving. Measure how often the delivery lands inside the window you sent, and widen the window if it does not hold.
Can customers reply to change the delivery?
They can, if the channel supports replies and someone acts on them. An agent can handle simple requests such as a safe place or a contact number, within rules you set. Requests that change the route, such as a new day, should go to a planner who can see the vehicle plan.
Will this reduce calls to the office?
It should reduce “where is it?” calls, because customers hear first. It can increase other contacts at the start, such as replies to messages. Measure inbound calls and messages per delivery for a month before and after, and check that the reduction is real rather than moved to another channel.
Sources
We last checked these sources on 19 November 2026. Rules, fees and prices change. Check the source before you act.
Bring us the task.
Tell us what happens today, which tools are involved and where it goes wrong. On a free 30-minute review, we’ll work out whether an agent, an automation or neither is the right fix, and what a sensible first release would be.
Start a project.

Book a call or send us a message. We read everything.
tash@neu.ie
Working with teams in Ireland and worldwide.
Free 30-minute AI review.