plan the work
Every job, every technician, one board.
One shared view of the day across teams, locations and regions: instead of scattered tickets and texts.
what it does
What Dispatch Board does
The board is where the operation is actually run. It shows who is working, what they are on, what is running late and what nobody has picked up yet.
Because every module writes to the same work order, what you see on the board is the current state, not a report that was accurate this morning.
Colour carries meaning rather than decoration: assigned, in progress, and needs a human decision are visually distinct at a glance from across the room.
- Create, assign and track every job from one place
- Status visible across teams, locations and regions
- Unassigned and at-risk work surfaced rather than buried
- Reflects the same record the technician is working from
how it works
Four steps, and none of them are magic.
-
gather
Every job lands on one board
Planned work, emergency callouts, follow-up visits and subcontracted jobs, across teams, locations and regions: instead of a board per depot and a spreadsheet in between.
-
show
State is visible without asking
Assigned, travelling, on site, waiting on parts, needs a decision. The board answers the question a coordinator would otherwise phone someone to find out.
-
adjust
Change is a drag, not a conversation
Move a job to another technician or another day and everything downstream updates: the technician's app, the customer's appointment, the schedule around it.
-
escalate
The board surfaces what needs a person
Jobs at risk of breaching a contract response time, unassigned work approaching its window, and anything a technician has flagged from site.
data and integration
What it reads, what it writes, what it sits beside.
Nothing here is a separate database. Dispatch Board works off the same work order, customer and asset records as everything else, which is the whole reason the modules are worth running together.
reads
Work orders, schedule assignments, technician status from the mobile app, contract response clocks.
writes
Reassignments back into the schedule; status changes to customers and to Invoice & Payments when work closes.
alongside
AI Scheduling & Dispatch, which proposes the plan the board then governs.
questions we actually get
Before you ask us on the call.
Yes, and filter down to one. Coordinators usually work in their own region and escalate across; managers watch the whole picture.
Yes. Visibility and edit rights are set per team, location or region.
The app queues their updates and syncs when the connection returns. The board shows the last known state and when it was received, rather than implying it is live.
Nothing you are likely to hit. Boards running several thousand jobs a week across regions are normal; the constraint is usually how much a human can read at once, which is why filters matter.
elsewhere in the platform
Other capabilities
further reading