What a custom agent looks like inside a courier, medical delivery or last mile company — the ten roles in your language, and what each plugs into in a business running a courier platform alongside driver apps and customer portals.
last reviewed
Courier work is high volume, low value per transaction, and unforgiving about timing. The economics only work if dispatch, proof of delivery and billing all happen without much human touch — and in most companies at least one of the three still does. Add contract customers who each want their own reporting format and their own service level, and the office grows faster than the fleet.
The honest version of "does it integrate with my software." These are the systems this industry actually runs on, and what each one means for a build.
The systems of record for orders, dispatch, routing, proof of delivery and billing across on-demand and scheduled routes.
Where scans, signatures, photos and timestamps are captured, which is both the service proof and the billing trigger.
Contract customers placing orders through your portal or their own systems, in volume, with service levels attached.
Stop sequencing and driver assignment, the largest lever on cost per delivery.
Independent contractor or employee pay per stop, per mile or per hour, with the classification implications that follow.
Driver qualification, insurance and, for medical and pharmaceutical work, chain of custody and temperature requirements.
Per-stop, per-mile and accessorial billing across contracts with different rate structures.
Each of these is a real build, not a feature of a product you already pay for. Follow one through to see how it works in general.
Nothing you are owed gets dropped.
Whatever arrives, in whatever format, becomes a clean record.
Writes the recurring document from your own past work.
Knows what expires, renews or comes due — and says so first.
Answers from your own records, not from the internet.
The conversation becomes the record, without anyone typing it up.
Assembles the recurring report from systems that do not talk.
Matches two sets of records and queues only the exceptions.
Two systems that do not talk, now talking.
Applies your rules, escalates only what needs judgment.
If that is a job in your business, the next step is half an hour on a call. Bring whatever you know about the volume — how many a month, who owns it now, which systems it touches. That is enough to scope it properly and quote it flat before anything starts.
Everything in this library is built to order rather than bought off a shelf — and whatever I build, I host and maintain. The rest of the library is here.