Dispatch Board for Field Service Companies: Who Takes the Urgent Job, and Why
A dispatch board puts every crew and every job in one place, and when an urgent job arrives it proposes which crew takes it, what moves and why, in plain words with the score shown. The dispatcher accepts it or drags the job to another crew and the plan is worked out again. Each customer whose window changes gets a text. We built a working demonstration on sample data, on an invented map.
The problem, in the owner's words
The owner's sentence is: "My dispatcher juggles a whiteboard, three group texts and a calendar, and jobs still get double booked." The schedule is real but it lives in three places, and the person who holds it together is the person who cannot be sick.
An urgent job is the test. A burst pipe means someone decides in two minutes which crew is closest, which one can do plumbing at all, and which customer gets pushed back. Doing that from memory is how a window gets missed.
The job this replaces, and what it costs
The role is a dispatcher or an operations manager. We cite no pay figure: our role data covers AI, systems and marketing roles, and we have not read a sourced figure for dispatchers.
What the demonstration shows is the decision, with the working visible, so the owner can overrule it in a click.
How the demonstration works, step by step
The dispatch board below is a demonstration system running on invented sample data. No client uses this dispatch board, and nothing in it is a result anyone achieved. Here is the dispatch board recording, and below it the same path in order.
- Every crew and job is on one board with a map. The sample day has 4 crews and 18 jobs and the sample clock reads 10:40 AM. The map is labelled a sample grid, not a real town.
- Each crew row shows its skills. Crew 3 is a plumber who does water heaters and well pumps.
- An urgent job arrives: a burst pipe with water in the basement. The board proposes that Crew 3 takes it, arriving 11:07 AM, promised by 12:10 PM.
- The reason is written out: Crew 3 does plumbing and is 3 blocks away, about 12 minutes; Crew 2 is closer, at 1 block, but does not do plumbing. The score is shown, lower being better: Crew 3 scores 52, Crew 1 scores 98.
- It also shows what moves. A water heater install goes to Crew 4 in the same window, and another customer moves to 1:00 PM to 3:00 PM. 3 customers will get a text.
- The dispatcher can drag the job to a different crew. When it goes to Crew 1 the plan is worked out again: arriving 11:28 AM, score 98, 4 customers affected. Dragging it back and accepting sends 3 texts.
- The affected customer's text reads: "Your new arrival window is 1:00 PM to 3:00 PM." The crew's phone view updates with the next job, the address and the drive.
What the sample data shows
At the end of the sample day the page counts 19 of 19 jobs done and 19 windows kept, 18 as first promised and 1 moved to a new window and kept, with 0 missed. Drive time is 6 hours 40 minutes, which is 100 blocks at 4 minutes a block.
The page itself says the rest of the day is simulated from the plan, and nothing is sent to a real number. So those counts show how the day is scored, not how a real crew performs. The script that walks the path passed 53 checks.
Hire it, rent it or own it
The job a dispatch board does can be done by a person, by rented software or by a system you own. This table sets hiring, renting and owning a dispatch board side by side, using only what is on this page.
| Hire the role | Rent software | Own a system built for you | |
|---|---|---|---|
| What it costs | Pay and benefits for a dispatcher; we cite no figure | A monthly fee for as long as you use it | One fixed fee, from $10,000, quoted after the audit |
| Urgent job | Decided from memory, fast | Often suggests the nearest crew only | Skills, distance and what moves are all scored, with the reason in words |
| Telling customers | Calls and texts one by one | Template notifications | Each customer whose time moves gets the new window by text |
| When the dispatcher is out | The schedule is hard to read | Readable in the vendor's screen | One board anyone can read, with the reason beside every move |
What building it for your company involves
To build this for your company we would load your real crews, their skills and your service area. The scoring weights would be yours to change, and the dispatcher would always have the drag override.
The customised dispatch board starts with the $499 AI-Ready Audit, with your money back if it is not worth it. Then comes a dispatch board prototype built on your real data, ready in 7 to 10 days and free of any build fee. Pricing for a production dispatch board starts at $10,000 as a single fixed fee, and the code and accounts are yours when we hand over. Care for the dispatch board, if you want it, is $997 a month.
Questions people ask
Can the dispatcher overrule it?
Yes. In the demonstration dragging the job to another crew re-plans the day and shows the new score and the number of customers affected. The dispatcher always decides.
How does it choose a crew?
By a score that adds distance, whether the crew has the skill, and the disruption to other jobs. The working is shown beside the score so you can see why.
Does it text customers by itself?
In the demonstration it sends the sample texts when the dispatcher accepts, to no real number. In your version you choose whether the dispatcher approves them first.
Is a field service company dispatching with this today?
No. The crews, customers, addresses and the map are invented, and the rest of the day is simulated from the plan. It shows how an urgent job is scored and moved.
What would a dispatch board for our crews cost?
A custom system starts at $10,000 as one fixed fee, set after the $499 audit counts your crews and skills. A prototype planning a day you have already worked comes first, within 7 to 10 days.
Keep reading
See other working demonstrations beside the dispatch board in the prototype library, the hiring data on The AI Hiring Report 2026, and AI consulting for home services. Or order the $499 AI-Ready Audit.