What Is Intelligent Dispatch? A Plain-English Definition

What is intelligent dispatch? It's automatic technician matching. For every job, it evaluates each tech's skills and certifications, availability and working hours, current workload, proximity and how close the job is to its SLA deadline, then assigns the best fit. It keeps rebalancing those assignments as the day changes, so a sick call or an emergency doesn't mean starting the board over.

That's the short answer to "what is intelligent dispatch." The rest of this post is for dispatchers who've heard the term in a sales call and want to know what it actually does, what it doesn't do, and how to tell a real one from a label.

Why the definition matters at 6:42 AM

It's 6:42 on a Tuesday. Your board has 38 jobs on it. One of your two techs certified on backflow testing texted that he's sick. Four of his jobs need that certification, two have commercial SLA deadlines before noon, and the other cert holder already has a full morning across town.

You've got maybe 20 minutes before the phones start. You open the board, look at who's free, remember who's good with which customer, check who's closest, and start moving cards. Every move you make affects three other jobs.

That's the work intelligent dispatch is built to take off your plate. Not the judgment. The arithmetic.

What intelligent dispatch is not

The most common mix-up: people assume it's a map tool that puts a tech's stops in the shortest driving order. That's a different problem. Stop sequencing takes a list of addresses one person already has and orders them. It doesn't care who should be going in the first place.

Intelligent dispatch decides who goes. It's a staffing decision made job by job. When the right tech is matched to each job, and proximity is one of the things being weighed, shorter drives tend to follow as a byproduct. But the goal is the right person on the right job before the deadline, not the shortest line on a map.

It also isn't a replacement for you. A good system handles the repetitive matching and leaves the calls that need context (the customer who only wants one particular tech, the job you know will run long) in your hands.

Manual, rule-based and black-box dispatch

There are roughly three ways a job gets assigned to a tech.

Manual dispatch

You look at the board and decide. This works fine at 8 jobs a day. It works poorly at 80, and it falls apart when the person who knows everyone's certifications and quirks is out. All the knowledge lives in one head, and nothing gets checked unless that head remembers to check it.

Rule-based intelligent dispatch

The system checks each job against clear criteria: does this tech hold the required skills, are they working right now, how loaded are they, how close are they, how urgent is this job. It picks the best match and can show you why. Because the rules are explicit, it works from day one. There's no training period and no need for months of history before it gets useful.

The trade-off is honest: a rule-based system only knows what it's been told. If a tech's skills or working hours are wrong in the system, the assignment will be wrong too. Clean data in, good matches out.

Black-box dispatch

Some systems learn patterns from your past assignments and make picks they can't fully explain. That can work once there's enough history, but you inherit the old habits along with the good ones, and when it puts the wrong tech on a job, nobody can tell you why. For a dispatcher who has to answer to a customer or a service manager, "the system decided" isn't an answer.

Explainable matters because you're still accountable. If you can see the reason behind each assignment, you can trust the good ones and fix the bad ones fast.

What is intelligent dispatch checking on each job

Every system words this differently, but a credible one weighs at least these, in plain terms:

• Skills and certifications. Can this tech legally and competently do the job? A lapsed certification should count as no certification. In FSM Navigator, certification tracking (Pro) keeps an expiry date on each tech's certifications, with reminders before they lapse.
• Availability and working hours. Is the tech on shift, and not off duty or on vacation?
• Current workload. How much is already on their plate today? Piling everything on your fastest tech burns them out and leaves nobody free for the 2 PM emergency.
• Proximity. How far are they from the job right now?
• SLA urgency. How close is this job to its deadline? A commercial customer with a four-hour response window is more urgent than a routine maintenance visit due Friday. If you're still tracking deadlines by hand, SLA tracking for field service teams is worth a read.

You shouldn't need to know a secret formula. A vendor who leads with scoring math is selling the math. What you care about is whether the match makes sense when you look at it.

What happens when the day changes

A schedule built at 7 AM is out of date by 9. This is where a fixed schedule and an intelligent one part ways. A static schedule is a plan you made once. A dynamic one keeps adjusting. Our comparison of dynamic vs. static scheduling goes deeper on that difference.

Here's how the common disruptions play out:

• Sick call. Jobs that haven't started yet move to the next best available technician who qualifies. If nobody is free, the job should wait for you instead of landing on someone who's already booked.
• Emergency comes in. The new job gets matched like any other, and its deadline counts toward who should take it.
• A job runs long. The tech's later work gets looked at again, and anything they can't reach in time can go to someone else.

The keyword in all three is "rebalancing." It's what separates intelligent dispatch from a one-time auto-fill that sets the morning and then leaves you to clean up the afternoon.

Where you stay in charge

Automation should never lock you out of your own board. You know things the system doesn't: the customer who had a bad experience with one tech, the apprentice who needs a ride-along, the job you've got a bad feeling about.

So the test is simple. Can you move any job to any tech by hand, at any time, without fighting the system? If the answer is yes, auto-assignment is doing the grunt work and you're doing the dispatching. If the answer is "sort of," keep looking.

How to check a vendor's intelligent dispatch claim

"Intelligent dispatch" is easy to put on a features page. These questions separate the real thing from a label:

1. Can it explain each assignment? Ask to see why a specific tech got a specific job. If the answer is a score you can't interpret, or nothing at all, that's a black box.
2. Does it handle certifications, including expired ones? A tech whose license lapsed last week shouldn't be matched to work that needs it.
3. What happens when nobody qualifies? Does it fall back to the closest match, hold the job for a dispatcher, or force it onto someone anyway?
4. Does it double-book? Ask specifically what happens on a sick day when every qualified tech is busy.
5. Does it keep adjusting through the day, or only fill the board once in the morning?
6. Can you override anything by hand? Every assignment, any time.
7. Does it need months of your data first? A rule-based system shouldn't.

How FSM Navigator handles it

FSM Navigator runs the business from first call to renewals: booking, quotes, dispatch, the job, payment and service agreements. Dispatch is one part of that, and here's how it works.

On every plan, Free included, you get a visual dispatch board and calendar, manual assignment and SLA tracking. Every job carries its customer, location, priority, SLA deadline and notes.

On Pro and Enterprise, intelligent dispatch adds automatic technician matching. Our dispatch engine evaluates skills and certifications, availability and working hours, current workload, proximity and SLA urgency, and keeps rebalancing assignments as the day changes. It's rule-based intelligent dispatch, so it works from day one with no training period and no black box.

A few specifics:

• Required skills (Pro). A job can require specific skills. Dispatch assigns a tech who holds every required skill with an approved, current certification, and otherwise the closest match. An expired or unapproved certification doesn't count.
• Why this tech (Pro). On any automatically assigned job, owners, dispatchers and managers can open a plain-language explanation of why that technician was chosen.
• Working hours (Pro). Techs have weekly working hours, and intelligent dispatch uses them. Off duty or Vacation status keeps a tech out of auto-assignment.
• Sick days (Pro). When a tech calls in sick, jobs that haven't started yet auto-reassign to the next best available technician, and a job with no free tech waits for your dispatcher instead of being double-booked.
• Parts-aware dispatch (Enterprise). It won't assign a technician whose van stock lacks the parts the job requires.
• You can always override. Dispatchers can reassign anything by hand at any time.

How well does it hold up under load? In a simulated week, 1,509 of 1,510 jobs were auto-assigned (99.9%) across 60 technicians. That's a benchmark, not a customer result, and the details are on our case studies page.

Intelligent dispatch glossary

Auto-assignment: The system picks a technician for a job without a dispatcher choosing by hand.

Rebalancing: Re-checking assignments when something changes (a sick call, a new emergency, a job running long) and moving work that no longer fits.

SLA deadline: The time by which a job must be responded to or completed under a service-level agreement with the customer.

Required skills: Skills or certifications a job demands. A tech without them, or with an expired certification, shouldn't be matched.

If you're still assigning every job by hand, it's worth putting a number on what that costs you each week. Read The Hidden Cost of Manual Dispatch.