AI Dispatch Copilot
AI Dispatch for Small Trucking. Answers Calls 24/7, Drives Driver Check-ins, Screens Loads.
AI Dispatch Copilot is an operations assistant for small trucking carriers and owner-operators. It answers broker calls 24/7, drives driver check-ins by voice or SMS, screens incoming load offers for profitability and feasibility, and collects paperwork — all while keeping a human dispatcher in control. The AI never autonomously accepts freight, negotiates binding rates, or makes compliance claims. Carriers stop missing calls, automate the paperwork hunt, and make faster dispatch decisions without growing the back-office team.
System Capabilities
24/7 AI Call Answering
Inbound broker calls land on your Twilio number, get answered by an AI dispatch assistant, get recorded, and get transcribed by OpenAI Whisper. The AI extracts caller type (broker / driver / shipper), MC #, lane, equipment, rate, pickup and delivery times, and risk flags into a structured load opportunity. A human dispatcher reviews and decides — the AI never books.
Driver Check-ins by SMS or Voice
Send a check-in by SMS — the driver replies with status, location, ETA, and needs; the AI parses the reply. Or call the driver outbound: the AI asks one question at a time (location → status → ETA → needs), waits for each spoken answer, and writes structured data back. Drivers love voice because they don't have to type while driving.
Profit Scoring on Every Load
Per-tenant defaults (fuel price per gallon, truck MPG, driver pay method, target rate per mile) feed a deterministic profit calculator. Each opportunity gets a STRONG / ACCEPTABLE / WEAK / REJECT recommendation, plus operational warnings ('Required speed exceeds 50 mph — timing may be infeasible'). The AI flags risk; the dispatcher decides.
Document Capture by Text
Drivers text a photo of the POD, BOL, lumper receipt, or rate confirmation. The image lands in your tenant-scoped S3 bucket via a presigned upload, gets OCR'd via GPT-4o vision, and the AI extracts shipper, consignee, load reference, weight, and signed status into structured fields. POD acceptance flows back to the load timeline.
Human Approval Required by Design
The AI is not a freight broker. It never tells callers a load is accepted, never negotiates final binding rates, and never claims FMCSA / HOS / DOT compliance certainty. Every load commitment requires a dispatcher's explicit decision click. The compliance posture is baked into the prompts, the data model, and the UI.
Versioned Prompts + Audit-Grade Logs
Every AI inference (call summary, load screening, check-in parse, document extraction, daily report) writes an AiInteraction row with the prompt name, version, model, input, output, confidence score, and token usage. You can reproduce, audit, or A/B compare any AI run weeks later. Prompts are versioned files in the repo, not buried in code.
Tenant-Isolated Multi-Carrier
Built multi-tenant from day one. One install can host many carriers. Every operational table carries a tenantId. Database queries, S3 keys, and Twilio webhook routing all enforce isolation independently — one carrier cannot see another carrier's calls, drivers, loads, or documents under any code path.
Daily Dispatch Report
Every morning the system generates an AI-written summary of yesterday's loads created, decisions made, check-ins missed, documents still pending, calls still unresolved, top risks, and suggested next actions. It lands in the dashboard and (optional) the dispatcher's email. Read it over coffee, act on it before 8 AM.
Deployment Process
Connect Your Phone Number
Bring your existing dispatch phone number (port to Twilio, or buy a new one). Point Voice + SMS webhooks at AI Dispatch and set the number in your tenant settings. Inbound calls now route through the AI; SMS check-ins start flowing the same day.
Add Your Drivers and Trucks
Enter driver names plus mobile phones, plus your truck and trailer inventory. Set tenant operational defaults — fuel price, MPG, target rate per mile, late-checkin threshold. AI Dispatch is now ready to talk to your fleet.
Review the AI's Work
Every broker call becomes a structured load opportunity for review. Every driver check-in becomes a parsed status update. Every document upload becomes an OCR'd record. You approve, reject, or ask for more info — the AI never books or commits without a human.
Operational Cost
Connects to Your Existing Stack
AI Dispatch Copilot plugs into the platforms you already run.
Common Questions
Is this a freight broker?
No. AI Dispatch Copilot is carrier-side. The AI never accepts loads, never negotiates binding final rates, and never commits you to anything. Every load commitment requires a dispatcher's explicit approval click. The guardrail is enforced in the prompts, in the data model (DispatchDecision rows), and in the UI.
How does the AI actually answer my phone?
Your dispatch number's Voice webhook points at our TwiML endpoint. When a call lands the AI greets the caller, records the message, and Twilio's basic transcription is captured immediately; a background worker then re-transcribes via OpenAI Whisper for higher accuracy. The AI runs a versioned call-intake prompt over the transcript and creates a structured load opportunity (broker, lane, equipment, rate, risk flags). A human dispatcher reviews on the call detail page.
Can the AI talk back to drivers, or just text them?
Both. SMS check-ins send a structured prompt and the AI parses the driver's reply. Outbound voice check-ins use Twilio Programmable Voice with one question per turn — location → status → ETA → needs — the AI waits for each spoken answer and writes structured data back. Drivers prefer voice because they don't type while driving.
What if Twilio's transcript is wrong?
We re-transcribe every recording with OpenAI Whisper after the call ends, and the Whisper output replaces Twilio's basic transcript. AI summaries are always based on Whisper, not Twilio's transcription. Significantly higher accuracy on driver and broker speech, regional accents, and trucking terminology.
Does it integrate with my TMS?
Not natively today. AI Dispatch Copilot owns the call, SMS, check-in, profit, and document layer. Load and driver data are accessible via REST API for export to a TMS. Native McLeod, Truckstop, and DAT integrations are on the roadmap. Tell us what TMS you use.
What about 10DLC and STIR/SHAKEN?
We require A2P 10DLC registration for SMS — the platform walks you through the Twilio Console flow at onboarding (Sole Proprietor for owner-operators, Standard Brand for LLCs). For voice spam-labeling we recommend Twilio Verified Caller Display / Trusted Call Solutions when call volume justifies the per-call fee. Both are per-carrier setups.
Is my data shared with other carriers on the platform?
No. Tenant isolation is enforced at the database query, S3-key, and webhook-routing levels independently. Every operational row carries a tenantId; every Prisma query filters by it; every S3 key is prefixed with the tenant ID; inbound Twilio webhooks route by the dialed phone number (which is owned by exactly one tenant). Unit-tested.
See AI Dispatch Copilot Running Live
We will show you AI Dispatch Copilot processing real data in a live demo. No slides. No pitch deck. Just the system running.
See It Run