Delivery and Logistics Phone Handling: Status, Claims, Drivers
How delivery and logistics companies can handle parcel status calls, failed deliveries, claims and driver lines without overloading the phone.
Delivery companies have a phone problem that grows with success. Every parcel is a potential call: someone wants to know where it is, when it will come, or what to do about the card through the door. When volumes rise, call volumes rise faster, and the ratio of calls to deliveries is a measure of how much information customers can get elsewhere.

This guide is for courier firms, freight forwarders, last-mile delivery operators and warehouses with customer-facing phones. It looks at the three groups who call, how to deal with status questions, how to handle damage and claims, and how to run a line that does not drown at peak times. For related context, read Phone Handling for E-commerce and Self-Service in the Contact Centre.
Who is on the line
Three types of caller
- ReceiversPeople waiting for a delivery, asking where it is, changing the time or address, or reporting a failed delivery.
- ShippersBusinesses or senders asking about pick-ups, pricing policy, labels, tracking and claims.
- Drivers and partnersCouriers who cannot find an address, cannot get access, or need to reach a dispatcher.
Drivers are the group most often overlooked. A driver stuck at a locked gate needs an answer in minutes; if they have to use the same queue as a customer asking about a delivery next week, deliveries are delayed and the customer's call is the result. Give drivers their own line or option.
Status questions: the biggest category
In most delivery businesses, status calls are the majority. "Where is my parcel?" is a question that tracking should answer, and when it does not, it is usually because the customer cannot find the tracking page, the tracking is out of date, or the answer is not helpful ("in transit"). Each is a clue to fix elsewhere.
Handling a status call
- IdentifyAsk for the tracking reference or other agreed identifier.
- Look upRead the current status from your records.
- ExplainSay what it means in plain words and when the next update is expected.
- ActOffer a reschedule, a safe place, a pick-up point or a redirect if your service allows it.
- RecordNote the request so the driver or hub sees it.
A voice agent connected to your tracking data can be designed to read out the latest status and take a change request. Without that connection it should not guess; it should take the reference and arrange for a person to call back. Voice AI Function Calling explains how an agent looks up live data, and Numbers and Names in Voice AI explains why long references are tricky to capture by voice.
Failed deliveries and rescheduling
A failed delivery attempt produces a predictable wave of calls. The customer wants to know what happened and what they can do. Make the rescheduling path short and precise. Say what can be changed (date, time window, neighbour, collection point) and what cannot.
Rescheduling by phone
| Without a plan | With a clear path | |
|---|---|---|
| Caller hears | Hold music, then a general agent | The options for their parcel |
| Driver sees | No change, or a note too late | The updated request before the next run |
| Outcome | Another failed attempt | A planned second attempt |
Connect what is promised on the phone to what the driver sees. A promise that does not reach the driver is the quickest way to a second failed delivery and a second angry call.
Damage, loss and claims
These are the most sensitive calls. A customer whose parcel is damaged or missing is upset, and what you say may matter later. Staff should follow a written claims procedure.
- Collect the reference, the sender, the receiver and a plain description of what happened.
- Tell the caller what evidence you need, such as photos, and where to send it.
- Explain the next steps and timelines without promising an outcome.
- Pass the case to the person who owns claims, with a written note of the call.
- Follow up at the time you said you would.
An automated agent can start a claim by collecting the facts, but it should not promise compensation or admit liability. See What an AI Receptionist Should Not Do.
A line for drivers and depots
Dispatchers and depot staff handle calls that customers should never see: access codes, gate problems, vehicles that have broken down. A separate number or menu option, perhaps with a short code, keeps those calls out of the customer queue. Route them to dispatch, give them priority and measure the time to answer separately.
Peaks, weather and disruption
Delivery call volume follows promotions, holidays and weather. When a hub is delayed or the roads are closed, thousands of customers have the same question. The best response is a short recorded message that explains what is happening, offers a callback and invites the customer to use tracking. Seasonal IVR Updates and Emergency Messages in Your IVR explain how to prepare messages.
Delivery phone readiness
- Receivers, shippers and drivers each have a clear route
- Status answers come from live tracking, not guesses
- Rescheduling changes reach the driver before the next run
- Claims are logged with a written note and a follow-up date
- A disruption message can be switched on within minutes
What to measure
Look at calls per hundred deliveries, not just total calls. A rising ratio means customers cannot find answers elsewhere. Track the proportion of status calls, repeat calls about the same reference, and how long claims take to resolve. Repeat Call Rate and First Call Resolution explain how to interpret those figures.
A worked example: a failed-delivery wave
Imagine a regional courier on a day when heavy rain delays several routes. By afternoon, hundreds of customers have a card through the door and call to ask what to do. The same question repeats, and the answers depend on the parcel.
A prepared company has a short message explaining the delay, a menu option for rescheduling, and a callback option for people who prefer to wait. Status answers come from the tracking records, and rescheduling changes appear on the driver's list for the next run. The queue still gets busy, but it is shorter and calmer. The example is hypothetical; it shows why connecting the phone to the same records the drivers use matters more than adding people to answer the same question repeatedly.
- Test the reschedule path end to end before the season starts.
- Keep a script for the three most common failure reasons.
- Check at midday whether the message still matches what is happening.
Doing it in Call
In Call, an IVR can send receivers, shippers and drivers to separate queues, with business hours and holiday closures deciding where each goes. Callback requests let customers keep their place during peaks, and voicemail per queue captures out-of-hours messages. An AI agent can be given your delivery information and told when to hand a call to a person, and call summaries show the reference and the request. Contacts and the shared inbox help keep claims on track. See Setting Up Call Queues and Call Summaries in Call.
Frequently asked questions
Can an AI agent tell customers where their parcel is?
It can if it is connected to your tracking data and designed to read only what is there. Otherwise it should take the reference and arrange a callback.
How do we separate drivers from customers?
Offer a dedicated number or menu option for drivers and depots, route it to dispatch and measure it separately.
What should the phone do after a failed delivery?
Offer clear options, such as a new date, a collection point or a safe place, and make sure the choice reaches the driver.
Who should handle damage claims?
A trained person following a written procedure. An automated agent can collect the facts but should not promise compensation.
How do we handle disruption peaks?
Use a short message explaining the situation, offer callbacks, point customers to tracking, and review the message every few hours.
Which metric tells us if the phone is working?
Calls per hundred deliveries, alongside repeat calls about the same parcel, show whether customers are getting answers without ringing.