A parcel aggregator got call-centre delivery rates without the call centre
First-attempt delivery across its GCC lanes went from 78% to 84% — within a point of what rivals achieve with a room full of people phoning customers, and with no one phoning anyone.
- First-attempt delivery rate
- +6 ptsFirst-attempt delivery rate78% to 84%, the aggregator's own measurement
- People added to get there
- ZeroPeople added to get thereNo calling team, no per-address human step
- What the human-agent alternative reaches
- 85-88%What the human-agent alternative reachesA competitor's rate, reported to us by the customer
- Where the address is fixed
- Pre-OMSWhere the address is fixedBefore the order record exists, not after a failed attempt
- Customer
- Parcel aggregator
- Markets
- GCC
The challenge
In most of the GCC, an address is a sentence, not a code.
There is no dependable postcode to key off. A shipper hands over a villa number, a building name that three buildings share, a landmark, a district spelled four different ways across four orders, and a phone number that may or may not be answered. It is enough for a human who knows the neighbourhood. It is not enough for a routing system, and it is often not enough for a driver who has never been down that street.
This aggregator was landing 78% of parcels on the first attempt. The missing fifth were not lost — they were re-attempted, held, called about, re-routed, and eventually delivered, each step costing a van slot, an agent's time, and a customer's patience. The address data was the root cause and everyone downstream was absorbing it: customer support fielding the calls, drivers making the judgement calls at the kerb, neither of them positioned to fix the record at source.
The market had already answered this. Competitors were hitting 85–88% first-attempt by hiring people to phone the recipient before dispatch and write down a better address. It works. It is also a permanent headcount line that scales with volume, and it was being sold as a premium service at a premium price.
So the question was not whether address quality could be fixed. It was whether it could be fixed without buying a call centre.
The solution
XB AddressIQ sits in front of the aggregator's OMS. Every inbound address is parsed, resolved and corrected before the order record is created — not flagged for someone to review, not queued for a human, not caught after a failed attempt.
That placement is the whole design. An address corrected after dispatch has already cost you the attempt. An address corrected inside a review queue has already cost you a person. Correcting it upstream of the OMS means every system that reads the order downstream — routing, driver app, tracking, support — reads the good version, and nobody had to be told.
Nothing changed about how the aggregator's shippers submit orders. No new format, no portal for merchants to learn, no integration work on their side.
The results
First-attempt delivery moved from 78% to 84% — six points, on the aggregator's own numbers, across its GCC lanes.
That lands a point under the 85–88% its competitors reach with people on phones — near enough to compete on service, and reached a completely different way. Their band is a team that grows as volume grows, and a premium charged to cover it. This aggregator's 84% is a fixed cost with no one added to the payroll: the same class of result arriving as a property of the pipeline rather than as a service someone performs.
Six points sounds modest until you count what a first attempt is worth. Every avoided re-attempt is a van slot returned to the schedule, a support call that never happens, and a recipient who does not have to be home twice. Those savings compound across every lane, every day, without anyone doing anything.
The strategic outcome the aggregator points to is competitive rather than operational: it can now quote against the premium-service operators without carrying their cost base.