In short: most despatch admin is not despatch. It is the correspondence despatch generates – where is my order, it arrived damaged, nobody was in, the address was wrong. That load outweighs the picking and labelling in hours, and it gets handled last because it is not holding up a van.
Ask someone running a small operation how long despatch takes and they will time the picking, the packing and the labelling. That number is usually about right, and it is usually about a third of the real total.
The rest is the email, and it does not feel like despatch, so it does not get counted as despatch. It gets counted as “the inbox”, where it sits next to the new business enquiries.
The four message types delivery creates
Tracking chases. Where is my order. Comfortably the highest volume of the four and individually the quickest to answer, which is exactly why it eats the day: forty two-minute jobs scattered across eight hours cost far more than eighty minutes.
Failed delivery. Nobody was in, it was left somewhere odd, the card was not left, the safe place was not safe. Slower to resolve because it needs the courier, and it sits in a gap where neither you nor the carrier obviously owns it.
Damage and claims. The longest threads, the most back-and-forth, and the ones with a deadline attached, because most carriers have a claims window. Handled badly, these become refunds and reviews.
Address and access corrections. Short, urgent, and time-critical in a way the others are not. A wrong postcode caught before the van leaves is a two-minute fix; caught afterwards it becomes a failed delivery, then a tracking chase, then possibly a claim.
That last point is the shape of the whole problem. These categories feed each other, and the cheapest place to deal with any of them is upstream.
Why “where is my order” volume is a notification problem
The instinct is to treat tracking chases as a customer service load and to try to answer them faster.
The more useful reading is that each one is a customer who expected to know something and did not. Almost every WISMO message maps to a specific gap: no despatch confirmation, a tracking link that showed nothing for two days, a delivery date that passed without comment, or a delay nobody mentioned.
The volume responds to closing those gaps far more than it responds to answering faster. A despatch confirmation carrying a realistic date, and one proactive message when something slips, removes more enquiries than any improvement in reply speed.
Two practical points on the replies themselves. Answer with the status and a date rather than a tracking link, because a customer who is emailing has already looked at the link and sending them back to it produces a second message. And where the honest answer is that you do not know, say that with a date attached for when you will chase the carrier. “I’ve raised it with DPD and I’ll come back to you tomorrow” closes a thread; “it’s showing as in transit” does not.
Failed delivery: the chase nobody owns
This is the category that costs the most, because it has no natural owner.
The parcel is with the carrier, so it is not obviously yours. The customer bought from you, so it is not obviously the carrier’s. In a small operation that means it lands with whoever opened the email, gets a holding reply, and then depends on that person remembering to follow it up in two days.
Nobody tracks whether it resolved. The first anyone hears is a refund request, or a review, from a customer who has been waiting nine days and has emailed twice.
The fix is unglamorous: failed deliveries come off the inbox and onto a short list with an owner and a next-action date, exactly like an enquiry. Small list, usually a handful at a time, and it needs looking at once a day. What makes it work is that a list with a status has to be actively closed, and an email thread does not.
Damage and claims
Longest threads, most emotional customers, tightest deadlines. Most carriers have a window for reporting damage, and it is not generous.
Two things save time here. Ask for photographs in the first reply rather than the third, including the packaging and not just the item, because the claim will need them and asking later restarts the clock. And separate the customer’s outcome from the claim: resolve the customer quickly with a replacement or refund, then pursue the carrier on your own time. Making the customer wait for the claim to conclude turns a resolvable problem into a review.
Peak, when the enquiry load outruns the despatch load
The thing that catches people out is that the two do not scale together.
Double the orders and you double the picking. Double the orders in a period when the whole network is congested and you more than double the correspondence, because delays generate chases, and a chase generates a follow-up if it is not answered. The relationship compounds in a way the warehouse work does not.
Which is why the usual peak plan of putting more hands on packing solves the visible half and leaves the inbox to fill up behind it. The inbox is where the refunds get decided.
Where courier integrations stop
Worth being clear about this, because it is where most advice on the topic ends.
An integration that pulls orders, generates labels in bulk and pushes tracking events back is worth having, and it removes real manual work. If that is the question you came in with, it is answered properly on our workflow automation page, which covers which tools handle despatch and labelling and when a general automation tool is the wrong choice.
What no integration does is answer a customer who says the tracking claims delivered and there is no parcel. That message needs somebody to look at the photograph, form a view, and write a reply that a worried person will find reassuring. That is the larger half of delivery admin by time, and it is the half nobody sells you a tool for.
What a daily pass over a delivery inbox covers
The same shape as any inbox pass, with the categories set to this work.
Tracking chases get answered with a status and a date, in one block rather than as interruptions. Failed deliveries come off the inbox onto the tracked list with an owner. Damage goes to a standard first reply requesting the photographs the claim will need. Address corrections are pulled out and handled first, because they are the only category with a cutoff, and after the cutoff they become three other categories.
Anything needing a decision – a goodwill refund, an unusual claim, a customer who has had two failures in a row – is flagged with the history attached, so the person deciding is deciding rather than reconstructing.
For most operations that is thirty to forty minutes once a day, and the important part is that it is once a day rather than forty times.
That is the work in Inbox & Ops, and the general version of the problem is on admin backlog blocking the work.
The enquiry sitting behind all of this
Here is the reason a delivery inbox matters beyond the customer service of it.
In most small operations the delivery correspondence lands in the same place as new business. Wholesale enquiries, trade account requests, a retailer asking about stocking you. Those arrive into a queue containing forty tracking chases, and they look identical at a glance, because an inbox sorts by time and nothing else.
The tracking chase is from someone who has already paid you. The wholesale enquiry is not, and it is the one that goes elsewhere.
We will send one enquiry to your address and time how long it waits for a human answer – you write it, you approve it before it goes, and the result comes back about a week later. On a delivery-heavy inbox this is usually the number that changes minds.
LoadOff runs daily inbox work for UK operations where the correspondence outgrew the person handling it. Enquiries answered, delivery chases cleared, and anything needing a decision put in front of you with the history attached. Most clients are live within 48–72 hours. Get in touch.
Related reading: Where enquiries get buried · Workflow automation: what’s actually worth doing