What Workflow Is
Workflow is where your operation runs. Every load, every driver update, every broker email generates tasks — the AI handles the routine ones automatically and surfaces the ones that need a human decision.
Instead of juggling email, phone, ELD dashboards, and spreadsheets, you have one view: what's happening right now, what the AI has already handled, and what needs your attention.
How It Works
Workflow is organized into five department lanes that mirror the lifecycle of a load:
| Lane | What It Covers |
|---|---|
| Booking | Rate offers, negotiations, load acceptance, confirmations |
| At Pickup | Driver arrival, loading status, detention start, BOL |
| In Transit | Status updates, broker check calls, delay notifications |
| At Delivery | Arrival confirmation, POD collection, unloading issues |
| Post-Delivery | Invoice generation, payment follow-up, driver settlement |
Every task in the queue shows:
- What needs to happen and why
- What the AI recommends (with its reasoning)
- The financial impact if relevant
- Action buttons to approve, modify, or override
Automation Modes
You control how much the AI does vs. how much you do. Set a mode per department — you might want full auto on status updates but human approval on every rate negotiation.
| Mode | What It Does |
|---|---|
| Manual | AI shows you information, you take every action yourself |
| AI Suggest | AI drafts actions and recommendations, you approve before anything sends |
| AI Approve | AI acts automatically on routine tasks, asks you on high-stakes decisions |
| AI Auto | AI handles everything, you see results after the fact |
Start with AI Suggest across all departments. After a few weeks of approving or adjusting its recommendations, you'll have a feel for where it's reliable enough to promote to Auto.
What Needs to Be Set Up First
Workflow populates from live data. It needs:
- Email connected — broker communications flow through email; without it, the AI can't see offers or send responses
- ELD connected — driver locations and HOS data power the in-transit and dispatch decisions
- Fleet data — trucks and drivers must be in the system for assignment tasks to work
If any of these are missing, Workflow shows a setup prompt pointing to what's needed. A half-connected operation means half the task queue — get all three connected before expecting full coverage.
The Stats Bar
At the top of Workflow you'll see a live summary:
- Tasks today — total tasks generated in the last 24 hours
- AI handled — how many the AI resolved without you
- Pending your input — what's waiting on you right now
- Revenue in motion — dollar value of loads currently active
This is your daily pulse check. A high "AI handled" percentage means the operation is running smoothly. A growing "pending" count means something needs attention.
Overriding the AI
Every AI action can be overridden. When you disagree with a recommendation:
- Open the task
- Modify the AI's draft or select a different action
- Your override is recorded — the AI uses it to calibrate future decisions on similar tasks
The AI gets more accurate over time as it learns your preferences, your broker relationships, and what rates you actually accept on specific lanes.
What Makes Workflow Different
Most dispatch software is a record-keeping system — you do the work, it stores what happened. Workflow runs in the other direction: the AI does the work, you supervise. Your job shifts from executing tasks to reviewing outcomes and setting the rules the AI operates by.