Skip to content

Logistics & Distribution · Courier & Parcel

A parcel is only ever as trusted as the queue watching it

We build the instant booking, live tracking, and proof-of-delivery capture that keep a courier run honest: every job priced on the spot, every drop closed with a signature or a photo, every exception caught before support has to pick up the phone.

Every booking priced and confirmed on the spotEvery job closes with a signature, a photo, or a logged exceptionAn exception gets a new window before support has to call
booking queue · Thistledown Courier live
4 bookings in queue
BK-3041 · N. FerroSame-day · 09:00–11:00 · Awaiting captureOut for delivery
BK-3044 · H. AdeyemiNext-day · 13:00–15:00 · Signature capturedDelivered
BK-3047 · C. WhitlockEconomy · 08:00–12:00 · Photo capturedDelivered
BK-3052 · J. OseiSame-day · 15:00–17:00 · Exception: no access codeDelivery attempted

Proof of delivery · latest capture

signed+1 photo

BK-3052 flagged · redelivery offered 09:00–11:00 tomorrow · customer confirmed by SMS

Bookings, customers, and the capture shown here are illustrative. The queue logic behind them is what ships.

Where a parcel run breaks down

Five rules a booking breaks without a live queue

Each of these is cheap on one parcel and ruinous at volume. The second is the one operators underestimate: answering where-is-it is a whole team's day, far more than a line in the support budget, and it's the only one on the list a customer can be handed themselves.

Q.01

A booking taken by phone is a booking taken twice

Reading an address and a service level back over the phone invites the typo that sends a driver to the wrong door.

Q.02

‘Where is it’ is the call center's whole day

Without a live status a sender can check themselves, every parcel in transit becomes a phone call waiting to happen.

Q.03

A missed collection window costs the account

A same-day promise that slips past its window delays more than one parcel. It puts the next booking from that account at risk.

Q.04

No proof means every dispute starts from zero

‘It never arrived’ is expensive to argue without a timestamped signature or photo on file.

Q.05

An exception with no next step just sits

A failed attempt that waits for someone to notice it is a parcel quietly aging in the back of a van.

None of these are rare. They're the five places a booking most often loses trust before it loses time.

Collection windows

Every tier reads the same way, from booking to close

Same-day

Book by 11:00

Collected and delivered within the metro area same day.

Next-day

Book by 17:00

Collected today, delivered by end of day tomorrow.

Economy

Book anytime

Collected within 48 hours, delivered on a flexible 3–5 day window.

A dispatcher doesn't have to ask which tier a booking is on. The queue already knows, and prices it accordingly.

Proof of delivery

What closes a job in the queue

Instant booking & pricing

A sender picks a service level and gets a price and a collection window on the spot. No call, no quote to wait on.

Auto-pricingInstant confirmCollection windows24/7 booking
BK-3041Same-day · 09:00–11:00
BK-3044Next-day · 13:00–15:00
BK-3047Economy · 08:00–12:00

Live tracking for sender and recipient

A shareable link follows the parcel from collection scan to delivery, so the status a customer sees is the one the queue shows.

Collection scanIn-transit pingsDelivery windowShareable link

Proof-of-delivery capture

Every drop closes with a signature or a photo, timestamped and geo-tagged, filed straight against the booking.

SignaturePhotoGPS + timestampAuto-filed
Captured 14:071 photo

Exception handling & redelivery

A failed attempt raises a flag immediately, offers the next window, and texts the customer before anyone has to ask.

Access issuesRedelivery offersCustomer SMSDispute record

Every card above reads and writes to the same queue, so there's no second system for anyone to reconcile.

The exception

A failed attempt should never sit quietly until someone asks about it

The moment a drop fails, the booking is flagged, the recipient is messaged, and a new window is offered, all before the parcel leaves the courier van. What used to be a callback the next morning now closes itself in minutes.

  • Flags a failed attempt the moment it happens, hours before end of shift
  • Offers a real redelivery window in place of a generic ‘we'll try again’
  • Confirms the new window with the recipient over SMS
  • Leaves one clean record: booking, attempt, and resolution in the same place
Booking BK-3052 · Thistledown Courier
14:02Delivery attempted: access code not accepted at the gate
14:03Agent texted the recipient for an alternate code
14:05No response. A redelivery window was offered for tomorrow
14:06Recipient confirmed 09:00–11:00 by SMS reply
14:07Booking rescheduled and the courier notified, nothing retyped

The booking and the exchange shown here are illustrative; the logic behind them is what ships.

Watch a failed attempt turn into a rebooked window

The queue above is illustrative. Point the same booking, tracking, and exception logic at a real run from your own depot, and see how quickly a stalled parcel gets a new window and a notified customer.

What plugs into the queue

Every service level, every system you already run

Levels the queue tracks

Same-day
Next-day
Economy
Scheduled pickup

Already in your depot

Courier & dispatch network

Bookings assign to a courier by location, capacity, and service level without a dispatcher working the phone.

Address validation

Collection and delivery addresses get checked and geocoded at booking, before a driver is ever sent out.

SMS & push notifications

Collection confirmations, live updates, and redelivery offers go out from your own number.

Payments & COD reconciliation

Card, account, and cash-on-delivery jobs reconcile back to the booking automatically.

Getting a run onto the queue

Four stages from a phone-booked depot to a working queue

STEP 01

Map the parcel journey

We trace how a booking moves today (taken, priced, collected, tracked, and closed) and where trust currently leaks.

STEP 02

Connect booking and tracking

We wire instant booking and live tracking into the courier network and address systems you already run.

STEP 03

Launch the queue and POD capture

Booking, tracking, and proof-of-delivery go live first, tuned against real runs from your own depot.

STEP 04

Tune exception handling on real data

Redelivery offers and dispute records go live once we've seen how attempts actually fail on your routes.

We build on top of the courier network, address, and notification systems already running your depot. No rip-and-replace.

What changes in the queue

A depot that stops running on phone calls

Fewer ‘where is it’ calls

A shareable tracking link answers the question before support's phone rings.

Exceptions caught before they're a complaint

A failed attempt raises a flag the same hour it happens.

Redelivery booked without a phone call

A new window gets offered and confirmed by text, no callback required.

One clean proof record per job

Signature, photo, and timestamp file themselves against the booking automatically.

The bars above are a sample dashboard read, not a performance figure we're publishing. Real numbers live inside a client's own queue.

Questions

What a depot asks first

Yes. A sender chooses a service level online and gets a price and a real collection window immediately, with no callback to wait for.

A single shareable link follows the parcel from the collection scan to the delivery capture, so the sender and recipient see the same status the queue does.

The booking is flagged the moment the attempt fails, a redelivery window is offered, and the recipient is texted to confirm. No one has to notice it manually.

A signature or a photo, timestamped and geo-tagged, filed straight against the booking record. That's enough to close a dispute without a phone call.

No. It connects to the courier network, address validation, and notification systems you already run, so nothing gets double-entered.

Have a project?

Let's talk

Running a large platform, shaping a first MVP, or getting a product ready for a funding round? Tell us where you are. We'll shape the process around it, and stay with you after launch.