One platform, door to door.
Every tool a courier needs between the order landing and the signature on the doorstep, built to work together instead of bolted on.
Balanced routes in one click.
Pick a day and a depot. QuickDispatch spreads the booked jobs across your vans, respecting every time window and what each van can carry.
- Capacity-awareCubic metres, weight and piece count per van. Two-person drops go to two-person crews.
- Time windows keptBooked slots are hard limits, not suggestions.
- Multi-depotPlan several depots on one screen (Growth and above).
| Van 01 · Jamal & Ben · 24 stops | |
| Van 02 · Priya · 22 stops | |
| Van 03 · Tom & Kai · 26 stops |
It plans. It re-plans. It explains.
The agent works on top of the optimiser. It builds the day, watches it live, and when a van breaks down or a customer rebooks it proposes a fix you can accept in one tap.
- Plans overnightRoutes are ready before the first driver arrives.
- Live re-planningBreakdowns, failed drops and late rebookings handled in seconds.
- You stay in chargeEvery change is a suggestion with a reason. Nothing moves until you accept.
Customers reply. Slots book.
Send booking requests by SMS and email in bulk. Replies like "yes", "not Monday" or "thurs after 12" are understood and booked automatically. Anything unclear goes to a short inbox for your team.
- Keyword replies on every planYES, 1, 2 and date links work on Starter.
- Free-text understanding from GrowthReal sentences, typos and all.
- Reminders and chasersNo reply in 24 hours? We nudge them, then flag it to you.
| "yes please" | Booked Tue 14 Oct |
| "can u do thurs after 12" | Booked Thu 16, 12–4 |
| "im away until the 20th" | Booked Mon 20 Oct |
| "is it the grey one?" | Needs you |
3 of 4 handled without anyone picking up the phone.
Every outstanding job, on one map.
See what's awaiting a reply, what's booked, what's on a van and what's delivered, coloured by status. Draw around an area to book or route it in bulk.
Everything the driver needs. Nothing they don't.
iOS and Android. Load the van by scanning, follow the stops in order, capture photos and signatures, and log a failed drop with a reason in two taps.
- Scan to loadEvery piece checked onto the right van.
- Proof of deliveryPhoto, signature and GPS stamp on every drop.
- A little bit of gameStreaks and badges for clean days and five-star drops.
| 1 · LS6 2AB · 2 pcs | Done |
| 2 · LS6 4QT · 1 pc | Done |
| 3 · LS4 2HB · 3 pcs | Next · 12 min |
| 4 · LS5 3AA · 2 pcs | 13:10–14:10 |
| 5 · LS13 1EP · 1 pc | 13:30–14:30 |
A link that answers "where is it?"
On delivery day each customer gets a text with their tracking link: the van on a map, how many stops away it is and a narrowing arrival window. They can leave a safe-place note too. On Enterprise it runs on your own domain.
Your clients, self-served.
Every retailer you deliver for gets a login. They see each consignment's status, piece by piece, with the booked slot, tracking and proof of delivery. Export to CSV or pull it by API.
Open the portal demo →| OAK-48213 | 3/3 |
| HSF-2950 | 2/3 |
| HSF-2941 | 0/2 |
Two APIs. Clear docs.
The Customer API lets your shippers create consignments and read status (Growth and above). The Admin API gives you orders, bookings, routes, runs, drivers and tracking (full access on Pro). Webhooks fire on every status change.
- REST + JSON, OpenAPI 3Interactive docs, sandbox keys, idempotency keys.
- Webhooksconsignment.scanned, consignment.booked, run.started, consignment.delivered and more.
# Create a consignment (Customer API) curl -X POST https://api.quickdispatch.co.uk/v1/consignments \ -H "Authorization: Bearer $QD_KEY" \ -H "Idempotency-Key: 5f1c-44a2" \ -d '{ "reference": "OAK-48213", "recipient": { "name": "Sarah Khan", "phone": "+447700900123", "postcode": "LS6 2AB" }, "items": [ { "sku": "DIVAN-4FT6-GREY", "pieces": 3 } ], "booking": { "channels": ["sms", "email"] } }' # 201 Created { "id": "con_8Kq2", "status": "awaiting_scan", "tracking_url": "https://track.quickdispatch.co.uk/8Kq2" }