Container clears. Driver already moving.
100+ terminals watched continuously. Holds caught the moment they post. Container clears: appointment triggers and the best move is queued for your dispatcher in the same motion. Driver matched by skill, urgency, and proximity. Move chained to double-dip. Empty return timed before per-diem starts.
How it works
Every terminal in your network, watched without a single login
Every terminal: monitored continuously. No dispatcher opens a browser.
Discharge, availability, and LFD pulled instantly
Discharged overnight? LFD posted after vessel berths? We capture it the moment the terminal posts it.
Holds surface the moment they land: customs, chassis, freight
Customs hold, chassis split, freight hold: any can appear after discharge while the LFD clock runs. We catch them immediately and flag the right contact.
Container clears: appointment triggers, best move recommended, dispatcher sends it
The moment terminal status changes: appointment booking triggers and the best move is built and queued for your dispatcher, matched by skill and urgency, chained to double-dip if viable, empty return sequenced. Your dispatcher reviews the recommendation and dispatches with one click — and it keeps learning from the calls your team actually makes.
Before Doublefast: your team checks terminals one by one, dispatching hours behind
Dispatcher logs into one terminal, then another, then another, copying LFDs into a spreadsheet, missing holds that landed overnight. By the time they finish, the data is stale. Demurrage starts, and the dispatch is already late.
After Doublefast: every clearance surfaces a ready-to-go recommendation, dispatcher decides in seconds
100+ US terminals monitored continuously. Holds surface the moment they land. Container clears: appointment books and the recommended move lands in your dispatcher’s queue at the same time. The system learns from how your team actually dispatches, so the recommendation gets sharper every week — the dispatcher still makes the call.
Built for the real world.
LFD not posted yet: steamship line sets it after berth, not on DO arrival. Customs hold drops at 11pm; caught immediately, dispatch paused, broker notified. Container at the terminal, nearest chassis two miles away, flagged before the recommended move reaches your dispatcher. Container clears overnight: appointment booked, best driver identified, move ready for your dispatcher to review and send when the morning shift starts.
* Estimates based on live deployment data. Read the case study →
Customs hold
A customs hold lands at discharge; terminal blocks pickup, LFD clock keeps running. We detect it immediately, draft a notification to the customs broker, and queue the appointment to fire the moment it clears.
Container still on vessel
DO arrives before discharge. LFD won't post until after the vessel berths. We monitor discharge status and capture the LFD the moment the terminal sets it.
Chassis split
Container available at the terminal, chassis pool tapped out, so the driver deadheads to a nearby yard. We detect the split, adjust the move sequence, and bill the extra chassis time exactly.
Appointment cancelled day-of
Terminal cancels a confirmed slot with no notice, common across terminal booking portals. We detect it within seconds and re-snipe immediately.
LFD change after vessel berths
Steamship line adjusts free time; terminal portal and steamship line website show different dates. We pull both, take the tighter date, and re-sort the dispatch queue.
Accessorial mismatch
Redelivery logged on paper, not in the app. Fuel surcharge at 15% when the contract says 12%. We reconcile every accessorial against the delivery confirmation before the invoice goes out.