Live pilot claims stay tied to QA evidence and current readiness gates.
Intermodal drayage
Intermodal drayage dispatch built around booking, container, chassis, and terminal timing
DispatchAi by Brace keeps intermodal load intake focused on booking numbers, container and chassis details, terminals, cutoff pressure, appointments, drop/return timing, documents, and repeat lanes.

Loadboard work should explain rate, risk, assignment fit, and execution proof.
- Rate context
- Verified carrier
- Partner signals
Company-scoped routes, users, reports, and documents stay separated.
Financial and report outputs are reviewed in app before files leave.
ELD, video telematics, accounting, and push claims stay setup-scoped.
Legal, privacy, security, subprocessors, DPA, and acceptable-use pages are public.
Container-first intake
Intermodal dispatchers need booking, container, chassis, pier/ramp, customer, and timing details near the top of the load record.
Repeat lane memory
Lane and billing templates help teams avoid retyping customer/origin/destination patterns while preserving manual review.
Documents near the action
BOL, POD, delivery proof, accessorials, and reupload status stay tied to the load so billing can see what is ready.
Questions
What is live now?
Fleet dispatch, driver upload, OCR review, billing readiness, payroll review, messages, and QA-proven stress workflows are the current MVP focus.
What comes later?
Live Gmail/SES ingestion, QuickBooks/Xero, telematics, production push notifications, and native scanner polish remain later-scope integrations.