The problem
What was breaking.
Every carrier portal has its own dashboard. Operators tab-switch instead of running.
Dwell times spike for hours before anyone notices — by which point the SLA is already breached.
Exception handling is reactive: a manager finds out from a customer call.
What we did
The moves.
- ⌬Apogee gateway aggregates carrier APIs (5 partners, mixed REST and SOAP).
- ◎Probes watch dwell time per yard, per carrier, per shift. Threshold-aware.
- ▷Autopilot reroutes within tier AUTO when blast ≤ 5 shipments and risk ≤ READ.
- ≡Unified audit feed: who rerouted what, when, with what trace. Auditors get the receipts.
Results · first 90 days
The numbers.
SLA BREACHES
−62%
first quarter
DWELL TIME
−18min
median
EXCEPTIONS
94%
caught before customer call
“We stopped finding out from customers. APO finds out from the data, surfaces it to the dispatcher, and proposes the next move. We just say yes or no.”
Tomás R.
Dispatch Lead
Have a lifecycle in Logistics / Supply chain?
Bring it. We'll wire APO in read-only against it for 30 days.