ASTERION · DELIVERIQ
Module 17 — Last-Mile Delivery Intelligence

Last-Mile Delivery Intelligence

A driver co-pilot and courier intelligence that work around the app your drivers already use: routes that respect timed services, customers contacted before arrival, and no failed delivery without evidence.

Download the product overview (PDF)
THE LAST-MILE BLIND SPOT

The courier's app scans the parcel. Nothing helps the driver deliver it.

Couriers run on a corporate driver app that handles scanning and proof of delivery, and they rarely want it changed. None of those apps plans a route, so drivers pay for their own optimiser and switch between three apps at every stop. A generic optimiser can't see which parcels are on a timed service, so those are the ones that arrive late. And a failed delivery coded "customer not available" is hard to argue with when there's nothing to say whether anyone actually tried.

Timed services miss their windows

The route is built by a tool that doesn't know which parcels carry a cut-off, and those are the deliveries with penalties attached.

A fail with no evidence is just a claim

Without a contact attempt, a location and a timestamp, a false fail and a genuine one look identical, and so does a disputed non-receipt.

Mis-sorted parcels leave the branch

A parcel that belongs on another route is found halfway through the day, after the driver has already driven past the place it should have gone.

3
Apps a driver juggles per stop
The courier's app for the scan, a paid optimiser for the route, and WhatsApp for the customer. Co-Pilot becomes the one screen between them.
WHAT IT DOES

What DeliverIQ does

01

Routes that know the service

The day's waybills are sequenced into a route that honours the courier's timed services and their cut-offs. The driver can reorder anything, and their own order is kept as a version of the plan like any other.

02

Outliers caught at the branch

Parcels that don't belong on the route are flagged before the driver leaves the yard, not discovered halfway through the day.

03

The customer knows before the knock

The customer is contacted on WhatsApp ahead of arrival, in their language where the courier holds it, and the reply is shown and read back to the driver. Voice is an opt-in escalation, off by default.

04

Evidence, or the fail doesn't count

A stop can only be coded failed with a contact record, a GPS fix near the address, a reason and a timestamp. The bundle is written once and can't be edited. A refused fail is kept as an attempt, never discarded.

05

Offline-first Co-Pilot

The driver app keeps working without signal and hands each stop to Waze or Google Maps for turn-by-turn. It's the ordered stop list, never a replacement for the navigation app or the corporate one.

06

Branch and HQ intelligence

Built from the courier's own daily dispatch report, so a branch can see its fails and why, address quality per client account, driver quality and a wall dashboard before any driver installs anything.

GOVERNANCE & STANDARDS

The frameworks this is built against

POPIA

Customer contact data handled lawfully

Append-Only Evidence

Stop events and fails can't be edited

Read-Only Coexistence

Never writes to the courier's systems

White-Label

The courier's brand on every surface

ISO/IEC 27001

Information Security Management

Per-Tenant RLS

Isolation enforced at the database

PART OF THE PLATFORM

Read-only around the courier's systems

DeliverIQ is useful with no integration at all and gets better with each read-only feed the courier can give: the daily dispatch report, a scan in the yard, and eventually an API. It never writes to the corporate app. Every screen, message and export carries the courier's own name, logo and colours, switched per tenant from settings without a code change.

DeliverIQ SiteComm

Pre-arrival WhatsApp contact, reschedules and customer replies run through the platform's conversational layer, so the exchange is stored against the stop as evidence.

DeliverIQ NexusCore

Fail patterns, late timed services and address problems join the operating picture, where they can be correlated with everything else the business runs.

WHO USES DELIVERIQ

Who uses it

Drivers

One ordered list instead of three apps, customers who expect them, and a fair record when a delivery genuinely can't be made. The driver decides the route; the only thing they don't decide is whether a fail counts without evidence.

Dispatchers

Manifest import, route review, a reschedule inbox, address history and driver enrolment by QR code.

Branch managers

Fails and their reasons by driver and by client account, outliers caught before departure, and a wall dashboard for the depot.

Operations and client teams at HQ

Address quality per client account and evidence-backed answers to disputed deliveries, across every branch.

GET STARTED

Start with one day of your own dispatch data

Branch intelligence runs on the daily dispatch report you already produce, so you can see fails, late timed services and address quality across your branches before a single driver installs the app. Co-Pilot then pilots with one branch.

The driver decides the route. The evidence decides the fail.

Dispatch report in

One day's extract, read-only, turned into a branch picture of fails, reasons and address quality.

One branch pilot

Drivers enrolled by QR, routes sequenced, customers contacted ahead of arrival.

Your brand on it

Your name, logo and colours on every screen and message from the first day.