How to Dispatch Work Orders With AI

It's 4:40 on a Friday. A chiller fault comes in from your busiest site. Someone now has to work out who is certified on that unit, who is closest, which vendor actually turns up on a Friday evening, and whether the SLA clock has already started.

In most FM teams, that someone is a coordinator with a spreadsheet, a phone and a lot of memory. Dispatch works because they know the patch. It breaks when they are on leave, when volume spikes, or when the fault is reported at 11pm on WhatsApp.

An AI dispatch agent does that same thinking on every job. It reads the SLA, skills, location and history, assigns the right technician or vendor, confirms they are on the way and escalates a no-show before the SLA slips. This guide covers how to set one up, the rules you control and what stays with a person.

Key Takeaways

• AI work order dispatch assigns, confirms, escalates and closes. A rule that picks a name and stops is auto-assignment, not dispatch.
• The agent needs four inputs: an SLA matrix, skills and certifications, service zones and vendor history.
• You set the auto-assign thresholds and decide which exceptions need a person's approval.
• Run the agent alongside your coordinators for the first week and score every assignment against their call.

What AI Work Order Dispatch Is

AI work order dispatch is an autonomous agent that decides who attends a work order and then follows the job until someone is on site. It reads the request, matches it against the SLA, the skills the job needs, who covers that location and how each technician or vendor has performed before. Then it makes the assignment and manages the confirmation.

That second half is the difference. CMMS auto-assignment picks a name and stops. A dispatch agent keeps working the job: it waits for acceptance, chases silence, reassigns when needed and records every step.

The Inputs a Dispatch Agent Needs

An agent dispatches only as well as the data it reads. Four inputs do most of the work.

Live workload is the fifth input, so the nearest qualified technician does not get a fourth job while a colleague sits free.

The Rules You Set

The agent assigns on its own inside limits you define. The rules that matter most:

• Auto-assign threshold. Routine priorities assign without review. P1 and safety-critical jobs can require a person to confirm first.
• Cost gate. Any job likely to exceed a not-to-exceed amount goes to an approver before a vendor is engaged.
• Exception owners. Name who approves after-hours callouts, unfamiliar assets and vendors outside the preferred list.
• Escalation timers. Set how long the agent waits for acceptance before it moves to the next option.

Rules are set per site or client contract, so an FM service provider can run different SLAs per account.

The Dispatch Loop: Assign, Confirm, Escalate, Close

1. Assign. The agent ranks qualified options by SLA fit, proximity, workload and past performance, assigns the best match and notifies them on the channel they already use.
2. Confirm. It waits for acceptance and an ETA. Silence inside the escalation window counts as a decline.
3. Escalate. If the first choice declines or goes quiet, the agent moves to the next qualified option. If the SLA is at risk, it alerts the duty manager with the full history attached.
4. Close. When the technician checks in and completes the job, the agent confirms attendance against the work order, updates the requester and logs the outcome for the next assignment.

Every action carries a timestamp and a reason, so the answer to why a vendor got the job is already on the record.

What Stays With a Person

• Approving jobs above the cost gate or outside contract scope.
• Safety-critical work that needs a permit to work.
• Vendor disputes and decisions to remove a vendor from the preferred list.
• Any assignment the agent flags as low confidence.

The agent handles the routine volume. Your coordinators handle the judgement calls, with the context already gathered.

Before and After: Manual vs Agent-Run Dispatch

The gain is consistency across thousands of jobs. Every work order gets the same SLA check, skills match and follow-up, at 2pm on a Tuesday or 11pm on a Sunday.

How to Check Accuracy in Week One

Start in shadow mode: the agent proposes an assignment for every work order while coordinators dispatch as usual, and the two are compared daily. Three measures decide when to go live:

• Assignment accuracy. The share of jobs where the agent picked what an experienced coordinator picked, or where the coordinator agrees the agent's choice was better.
• Reassignment rate. How often a job has to move to a second technician or vendor.
• Time to confirmed attendance. Minutes from work order creation to an accepted assignment with an ETA, against your current baseline.

Go live priority by priority once accuracy holds, starting with routine jobs. Keep reporting the same three numbers weekly after go-live, alongside your wider work order analytics.

How Facilio Runs Dispatch

Facilio is the agentic platform for facilities management. Its dispatch agent is live at enterprise FM customers today, and sits between two others: the intake agent, which turns a call, email or WhatsApp message into a work order, and the vendor coordination agent, which handles quotes, attendance and service reports after assignment.

The agent works on the Atom Platform's FM data model, where assets, vendors, contracts, SLAs and permits already sit in one structure. It runs inside a harness with human checkpoints and a full trace of every action, and it is measured against evals before go-live and every week after. It runs on Facilio's CMMS or on the system you already use, including Maximo, Corrigo and Planon, as an agent layer on top of your existing CAFM or CMMS.

FM Ops Engineers sit with your team to map the SLA matrix, connect the data, set the rules and run the shadow week. After go-live they tune the agent against its accuracy numbers. Your team gets the outcome. Ours runs the agent.

FAQs