Live pilot claims stay tied to QA evidence and current readiness gates.
Dispatch billing templates
Dispatch billing templates for faster load intake and cleaner invoice readiness
DispatchAi by Brace lets teams choose or create lane and billing defaults near the start of New Load so bill-to, rate, terms, contact, route, and document expectations are easier to carry forward.
Product workspacePlan and money proof
Billing defaults, payroll review, and report outputs stay visible before export.
- Plan clarity
- Preview-before-export
- Pay Drivers review
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.
Dispatch billing templates pathReview the plan, usage, and billing defaults before signing up.
PlanUsageDefaultsNo surprise add-ons
Includes up to 4 office users plus included driver access while native app, push, and store rollout remain in controlled QA.
Do not charge fleet drivers as full seats before certified ELD, physical-device app proof, and push proof exist.Use Fleet Pro when the customer needs more office users, heavier support, OCR review, or integration setup.
$350/month is too low when the office team doubles and support, training, and QA load grow.Keep driver access bundled during pilot and app beta, then consider low active-driver or document-usage overages after real app value is proven.
High driver volume should be quoted by active fleet usage, support burden, OCR volume, push, and integrations instead of a full per-driver seat.Without certified ELD or hardware, price around dispatch, documents, reports, and office value rather than charging drivers like telematics seats.
ELD, video, and telematics remain partner-enabled until provider evidence and customer credentials are connected.Pick defaults early
Lane and billing templates should be searchable by customer, bill-to, origin, destination, and load type before the dispatcher fills the rest of the load.
Manual fallback
A dispatcher should still be able to enter a manual bill-to and save customer billing later when no profile exists yet.
Review before sending
Templates speed intake, but invoice and financial outputs remain preview-first before leaving DispatchAi.
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.