Freight Dispatch · Proposed AI workflow
Prioritize deliveries after a road closure
During the afternoon run, a road closure pushes two shipments past their delivery windows.
Try the Freight Dispatch demo →Application screenshots · Sample data
How Freight Dispatch works today
Select a shipment in the Freight Dispatch control tower to highlight its route. Simulate a road closure and compare the recalculated ETAs in the risk queue.
Simulation · Fictional records
Walk through the chat
Follow the scripted conversation and review the proposed action. Choices affect this walkthrough only.
Requester
Which delivery is projected to be latest?
Proposed agent workflow
-
Read
On a closure alert, compare active shipment routes and delivery windows in the control tower with the closure location. List DL-201 and DL-202 with projected overruns.
-
Check
For the highest overrun, compare the bypass and original route using current traffic estimates and vehicle restrictions. Return the 16:20 bypass estimate.
-
Draft
When dispatch selects the bypass estimate, check the customer contact on DL-201 and prepare a conditional delivery update for dispatcher approval.
-
Approve and queue
On dispatcher approval, recheck the traffic timestamp and shipment status. Queue the approved customer update in the dispatch outbox. Dispatch handles route authorization.
Result after approval
DL-201 customer update queued in the dispatch outbox.
Exception path
If the traffic feed stops refreshing, the assistant flags the stale 16:20 estimate. The customer update stays pending until the dispatcher verifies the bypass with the driver.
What to measure in a pilot
-
Notice preparation time
Measure from closure alert to approved customer draft.
-
ETA error
Compare each approved estimate with the delivery timestamp and report median absolute error.