Detention Gets Lost Between the Dock and the Invoice
The truck waits, the driver waits and the operations team watches it happen. Billing hears about it days later and rebuilds the story from texts and calls. The customer questions the timestamps, the fee gets short-paid or disputed, and the driver’s detention pay waits on the same paperwork.
One Event Record From Arrival to Payment
DockTime AI captures arrival and departure from telematics-backed timestamps and checks them against the contractual free window. When the window is breached, it notifies the right people, assembles the supporting data and generates the detention invoice. The driver’s detention pay comes from the same record, so nobody keys the event twice.
Detention is a revenue workflow, and it starts the moment the truck reaches the dock.
How It Works
Objective Timestamps
Captures arrival and departure from telematics data rather than driver calls.
Free-Time Monitoring
Compares dwell against each facility’s contractual window and alerts when it runs out.
Invoice With Proof
Generates the detention invoice with the supporting record attached.
Driver Pay
Triggers driver detention pay from the same event record.
Proof the Customer Can Check
A detention invoice gets paid when the customer can verify it. DockTime AI attaches objective timestamps and the related documents from Documents AI to each charge, and it reports detention by shipper, facility, lane and driver, so you can see which customers cost you time while there is still a chance to reprice.
Why We Built It This Way
Built in the Right Order
EKA built the infrastructure first and the optimizers second, so nothing gets ripped out when the next agent ships.
One Record, Three Seats
The same infrastructure serves carriers, brokers and shippers, because the load crosses all three and the handoff is where freight breaks.
Earned, Not Read About
The team spent decades operating freight across trucking, brokerage, freight payment, risk and insurance, which is why the agents handle the 40% of edge cases that break other AI.
Live in 2 to 8 Weeks
EKA goes live in 2 to 8 weeks against a legacy implementation of three to six months, and new agents ship on 8-week cycles.
You Do Not Have to Replace Your TMS
EKA is headless and API-first. Starting in Q1 2027, DockTime AI will deliver its work into the system you already run. EKA goes live in 2 to 8 weeks, on the records you already have.
Talk to Us About the APIOne Agent, Three Seats
Carriers and private fleets
The hours your trucks sit become revenue and driver pay rather than a write-off.
Brokers and 3PLs
You bill the shipper and pay the carrier from one verified record, so detention stops eating the margin on the load.
Shippers
Detention charges arrive with timestamps you can check, so disputes get shorter and the facilities causing delays become visible.
See DockTime AI on Your Own Freight
Live in 2 to 8 weeks, on the order, route and carrier records you already have. Bring a real load and we will show you the agent working on it.
Schedule a 20-Minute DemoFAQs
How does DockTime AI prove detention time?+
It uses telematics-backed arrival and departure timestamps checked against the contractual free window, and attaches them to the detention record.
Can it pay drivers automatically?+
Yes. Driver detention pay is triggered from the same event record that produces the customer invoice.
Can we see which facilities cause the most detention?+
Yes. DockTime AI reports detention by shipper, facility, lane, driver and time period.