Look at the chair. The person in it answers the status call, covers the no-show, reassigns the no-heat emergency and settles a parts question, all before lunch, and does it across six systems.
The dispatcher makes more decisions per hour than anyone else in a field service business and is usually the worst-served by its software. They're also the supervisor, the customer service rep and the first line of tech support, so a tool that costs them a minute costs it a hundred times a day. Knowledge workers switch between 11+ apps a day and lose 4+ hours a week to system switching (McKinsey), and the dispatcher's version of that is worse.
Here's the same day on one board, from the 6:30 queue to the 4:30 schedule, in which the dispatcher makes decisions instead of retyping them.
The timeline
6:30 AM: the queue is already built
On one board: Overnight portal submissions are in the queue as work orders. This week's planned maintenance is there too, generated from the agreements that cover it, ready to assign.
In six tools: The submissions are voicemails to transcribe, and the maintenance is a spreadsheet of contracts that someone has to check against the calendar. The first hour goes to building the list the software should have built.
8:00 AM: the trucks roll out
On one board: Technicians clock in on their phones. Vehicles are checked out with mileage and fuel recorded, and a truck marked out of service can't be checked out.
In six tools: The clock-in is a text or a call, the vehicle log is a clipboard, and someone discovers at 9:15 that the van with the bad brakes went out.
11:00 AM: the no-heat call
On one board: A commercial no-heat call comes in. The board recommends a technician based on workload and experience with similar work. The jobs that will be affected are flagged for reassignment, and ETA updates go out to those customers.
In six tools: The dispatcher scans a map in one system, checks a schedule in another, phones two technicians, then phones the customers whose appointments moved. The decision was quick. The logistics around it took the rest of the hour.
2:00 PM: the licensed job
On one board: A licensed job needs covering, and the nearest technician is no longer certified for it. The board won't let them be assigned. Nobody had to remember the expiry date. The full argument is in why an expired certification should block dispatch automatically.
In six tools: The nearest technician goes, because the board has no idea. The credential lives in a different system, and its expiry was an email that went to someone else.
4:30 PM: the exceptions
On one board: Completed work orders are already in invoicing at price book rates. Tomorrow's schedule is published. Only the exceptions that need a human are left.
In six tools: The dispatcher leaves at six, after checking that completed jobs have what invoicing needs and rebuilding tomorrow's schedule by hand.
What the board has to show
What should a dispatch board show? Enough to make a decision without opening another system. In practice that means five things.
A live map. Every technician's location, job status and remaining capacity are visible in real time, so assignment decisions rest on current information and not last hour's.
A dispatch board. Unassigned jobs sit in a queue and are assigned by drag-and-drop or with AI assistance.
Calendar views. Daily, weekly, team and regional. SLA tracking with escalation alerts warns before deadlines slip, not after.
Customer communication. ETA and on-the-way notifications trigger from technician status changes, so the dispatcher isn't the messenger.
Best-fit assignment. The suite recommends a technician based on open workload and experience with similar work, weighing proximity, skills, certification and priority in real time, and sequences the day's stops to cut drive time. The dispatcher decides. The recommendation explains itself.
And one more requirement that's easy to miss: requirement-aware assignment. Work types carry the certifications they require, and the board says so at assignment. It's a single paragraph here and a full article in its own right, linked above.
The operations manager's view: the shape of the business, not today's fires
If the dispatcher's day is about the next hour, the operations manager's is about the quarter. They need the shape of the business, and that has to come from the same records the dispatcher works from.
What reports should a field service operations manager track? A useful starting set:
- Open versus completed work by technician, team and service type
- Revenue from completed jobs and payments received
- Estimate pipeline by technician, service type and region
- Days-to-invoice and days-to-payment by customer
- Work order volume and completion time by service type
- Estimate win rate by technician and service type
Dashboards are configurable and role-based, and exports to Excel, Power BI and Tableau keep the data portable. Because the numbers come from the same platform the work runs on, month-end close gets faster and executive reporting gets more accurate. Nobody has to reconcile the operations report with the finance one, because they read from the same place.
It also opens up natural-language questions. "Which service lines had the longest days-to-invoice last quarter?" is a request an operations manager can ask and get an answer to, with the underlying data. Where AI actually changes a field service operation covers this and the rest of what AI does around dispatch.
If any of those measures looks bad, the causes often trace back to the six information gaps, and the estimate pipeline in particular comes from one price book.
Scaling the operation
As the operation grows, a few things have to hold up.
- Configurable workflows for different service lines: installation, repair, maintenance and emergency dispatch don't run the same way.
- Multi-location and multi-team support, with regional autonomy and shared data.
- Role-based access, so technicians see their jobs, supervisors see their teams and executives see the business.
- Connected onboarding, from recruiting through first dispatch.
For the last of these, see staffing a seasonal, licensed field workforce. For the way the whole sequence hangs together from request to payment, see from request to paid, and for adding a new crew to a live board, your first 90 days.
One board, one data model
The dispatcher's board can do all of this because it reads the same record that HR, the technician and accounting write to. A credential recorded in one place, a status changed in the field, a price updated by the office: each is one fact, written once and seen everywhere.
MangoApps Field Service Suite is built that way, as part of a platform that also handles communications, learning and HR. That's the difference between a board that displays the schedule and a board that knows the business.
What the dispatcher stops doing
It helps to name the tasks that disappear, because they're the ones nobody logs.
They stop retyping a voicemail into a work order. They stop opening a second system to see who's free, and a third to see who's qualified. They stop phoning customers to tell them a technician is running late, because the notification goes out when the status changes. They stop reconciling completed jobs against invoices at the end of the day. And they stop being the only person who knows why the schedule looks the way it does, because the board shows it.
None of those is a decision. Each is a piece of transcription that a person does because two systems don't share a fact. When they go, what's left is the judgment the dispatcher was hired for: who to send, what to move, what can wait.
Five things to ask on a dispatch demo
Ask to see each of these live, with your own service lines if possible.
- An emergency job entering the queue, and how the board proposes an assignment and shows its reasoning.
- A job being reassigned, and what happens to the customer's ETA and to the technician's next stop.
- A technician whose certification has lapsed, and an attempt to assign them to a job that needs it.
- A vehicle marked out of service, and an attempt to check it out.
- Yesterday's completed jobs, already in invoicing, and the exceptions that need a person.
If a vendor can do all five without leaving the board, the dispatcher's day probably looks like the one above. If it takes a second system for any of them, count it as one of your six tools.
What the afternoon of status calls is worth
The dispatcher is the user whose time compounds most across the company. Every minute they don't spend retyping or answering a status call is a minute spent on the decision that's actually theirs. Software that gives them back the afternoon is worth more than any single feature on the technician side.
If you're building a case for it, the evaluation guide has twelve questions to put to any vendor.
The dispatcher's day, the operations manager's reports and a role-by-role view of the same platform are in the Field Service Management guide. You can also see the Field Service Suite itself.
Frequently asked questions
What is a dispatch board in field service?
A dispatch board is the screen a dispatcher uses to see open jobs, technician locations and availability, and to assign work. A good one shows a live map, a queue of unassigned jobs, calendar views by day, week, team and region, and SLA warnings, and it triggers customer notifications as technician status changes. It's most useful when it reads the same record as accounting, HR and the technician's app.
How does AI-assisted dispatch choose a technician?
The suite recommends a technician based on open workload and experience with similar work, weighing proximity, skills, certification and priority in real time, and explains its reasoning so the dispatcher can decide. Requirement-aware assignment adds a check on credentials: a technician whose certification has lapsed shouldn't be assignable to work that requires it.
What KPIs should a field service operations manager track?
Start with open versus completed work by technician, team and service type; revenue from completed jobs and payments received; estimate pipeline and win rate by technician and service type; days-to-invoice and days-to-payment by customer; and work order volume and completion time by service type.
Can dispatch software prevent assigning an uncertified technician?
It can when work types carry the certifications they require and the technician's credentials live on the record the board reads. A technician whose credential has lapsed can't be assigned, and the board says why at the moment of assignment. Ask a vendor to expire a certification in a demo and then try to assign that technician. In MangoApps, work types carry the certifications they require, and a technician whose credential has lapsed cannot be assigned. The board says so at assignment.
Can I export field service reports to Power BI or Tableau?
Yes. Dashboards are configurable and role-based, and reports export to Excel, Power BI and Tableau, so the data stays portable and can be combined with the rest of your reporting.
The MangoApps Team
We're the product, research, and strategy team behind MangoApps — the unified frontline workforce management platform and employee communication and engagement suite trusted by organizations in healthcare, manufacturing, retail, hospitality, and the public sector to connect every employee — deskless or desk-based — to the people, tools, and information they need.
We write about enterprise AI for the workplace, internal communications, AI-powered intranets, workforce management, and the operating patterns behind highly engaged frontline teams. Our perspective is grounded in a decade of building for frontline-heavy industries and shipping AI agents, employee apps, and integrated HR workflows that real employees actually use.
For short-form takes, product news, and field notes from customer rollouts, follow Frontline Wire — our ongoing stream on AI, frontline work, and the modern digital workplace — or learn more about MangoApps.
