Planner Agent
Miles
Explore
Delhivery is one of the largest tech-driven logistics companies, backed by FedEx and SoftBank. Know More →
Agentic Workforce/Chase
Chase
Logistics Coordinator Agent
Chase is the Logistics Coordinator Agent: he watches every shipment in motion to protect on-time delivery.
Chase
Live
Shipment · DAL → PHX
DallasETA on-timePhoenix
Live events
T+02:14Appointment booked · voice call
T+04:38Detention risk · proactive alert
T+05:02Driver called · route deviation
T+06:10Unscheduled halt · escalated
Detention ↓
20–40%
Visibility
100% · 24×7
ALWAYS LIVE - 24/7
What Chase Does
Owns the diagnosis, recovery, and rebooking on every shipment post indent, around the clock.
Skills
- Knows why a truck stopped, not just that it did
- Rebooks the delivery appointment the moment the ETA slips, by phone, portal, or email
- Tells your DC and your customer before the truck is late
- Escalates with full context, but only after trying the fix
Coverage by mode
Every mode fails differently in transit.Chase knows which questions to ask.
A truck that stopped, a dock that will not take the delivery and a container sitting under a hold are three different problems. Chase runs the right diagnosis and the right recovery for each.
Why the truck stopped, not just that it did
An alert tells you something happened. Chase investigates before it reaches you, and arrives with a cause, the evidence behind it and a recommended next step.
6
deterministic exception rules
7
investigation tools
24/7
on shift, every lane
Six deterministic exception rules
Route deviation, unplanned long stop, ETA breach, harsh-event clusters and geofence miss, each with warn and critical thresholds you tune per tenant. Detection is deterministic, so it fires the same way every time.
Root-cause investigation
Any warning or critical alert opens a multi-round investigation across seven tools: recent traces, traffic incidents, weather, local news, the carrier's ELD and hours-of-service log, prior incidents and geofence lookups. What lands on your desk is a probable cause with evidence, not a notification.
Take actions, gated by your autonomy tier
Each finding resolves to a concrete step: call the driver, dispatch roadside assistance, move the appointment or notify the customer. Below your tier it waits for approval. At or above it, Chase acts and logs what it did.
Live event streaming
Position, stops, geofence crossings, harsh events, alerts and the investigation itself stream per trip. A client that reconnects gets the history first, so nothing is missed between refreshes.
The dock appointment, negotiated and held
Multi-stop LTL lives or dies on receiving windows. Chase computes what is genuinely feasible, negotiates it on the channel the facility actually uses, and rebooks the moment it slips.
12
lifecycle states, every transition validated
13
tunable guardrails
2
live outreach channels
Deterministic slot resolution
Feasible windows are computed, never guessed: the MABD window, transit time, ready time, facility receiving hours in local time, blackout dates, a lead-time floor and spacing against other trucks at the same dock. The model only chooses among slots that are already valid.
Twelve-state appointment lifecycle
Pending through requested, negotiating, proposed, confirmed, at risk, recovering and rescheduled, with every transition validated before it is written. An appointment cannot quietly end up in a state nobody can explain.
Negotiation by email and SMS
Outreach goes by real email and real SMS, thread-tagged and idempotent, with counter-offers parsed and answered inside the negotiation rounds and quiet hours you allow.
Disruption recovery
An ETA breach on the road marks the appointment at risk and reopens slot resolution with a shifted window, whether the signal arrives from telemetry or an EDI 214 status update, with a facility-strictness buffer applied before anyone is disturbed.
Durable TMS writeback
Confirmations go back to your TMS through an outbox enqueued in the same transaction as the state change, retried across twelve backoff tiers, then dead-lettered rather than lost. Your TMS and the dock do not drift apart.
Watching the box, not just the vessel
Ocean exceptions are terminal-state questions. Was the container takeable, was it under a hold. Chase tracks those as they change, and is explicit about the days no source can answer.
2
visibility vendors, one interface
0
days claimed on missing evidence
Container-level tracking
Container availability transitions and holds, behind one vendor-neutral interface with adapters for multiple visibility providers. Switching vendors does not mean rewriting the logic that reads them.
Holds paired to their releases
A hold placement and its release arrive as unrelated events with nothing linking them. They are paired so the window is real, and a customs hold is recorded as a hold rather than an inspection unless the evidence actually says inspection.
Authority-ranked evidence
When two vendors disagree about when a box became available, the more authoritative source governs and the other is kept and disclosed rather than discarded. Ocean is the one place where two feeds can assert incompatible facts about the same container, and the losing value is exactly what a carrier will produce later.
A second opinion, bought deliberately
Every vendor bills per container tracked, so watching everything twice doubles the feed cost for a benefit that shows up on a small minority of boxes. A second source is pulled when the answer is worth paying for, inside a budget you set.
A day with no evidence is disclosed, not claimed
Whether the empty could be returned is a separate question from whether the container was available, and detention turns on it. Where no source can answer for a given day, that day is left out of the claim and named in it. A claim that states its own gaps holds up against a carrier better than one that overreaches.
