What is Field Service Dispatch?

Field service dispatch is the assignment of service jobs to technicians and time slots — balancing skills, capacity, location and service commitments — and re-balancing as the day inevitably changes.

Why dispatch matters

In field service, the dispatcher is the constraint on the whole operation. Every job has to be matched to someone qualified, equipped and near enough to arrive within the promised window, and the plan degrades from the moment it is made: jobs overrun, parts turn out to be wrong, emergencies arrive, technicians call in sick.

The commercial stakes are direct. Utilisation — the share of a technician's paid day spent on billable work — is the primary lever on service profitability, and it is set almost entirely by dispatch quality. First-time fix rates depend on sending someone with the right skills and the right parts, and a second visit costs roughly what the first one did while earning nothing.

How dispatch works

A dispatch decision resolves several constraints at once:

Skills. Does this technician hold the certification or competence the job requires?
Capacity. How much work is already on them today, and does this fit?
Location. How far is the job from where they will be when it starts — not from where they are now?
Commitment. What was promised to the customer, and when does it breach?
Parts. Is what the job needs on the van, or does it require a depot stop?

These conflict routinely. The nearest technician may lack the skill; the most qualified may be committed elsewhere. Dispatch is therefore a sequence of trade-offs made under time pressure, which is why it benefits from being shown visually — on a map, a timeline and a board — rather than as a list.

An example

At 11:20 a technician reports that a two-hour job will take four. Two jobs behind it are now at risk, one with a commitment expiring at 16:00. The options are to move the at-risk job to a colleague finishing nearby at 14:00, to push the lower-priority job to tomorrow, or to let the commitment breach. All three are defensible; the failure mode is not noticing until 16:05.

Common variations

Manual dispatch. A dispatcher assigns work by hand, using local knowledge a model does not have. Effective at small scale, and the first thing to break as volume grows.
Assisted dispatch. The system proposes assignments and fills gaps; a human accepts or overrides. The common middle ground.
Automated dispatch. Jobs are routed by rules — skills, capacity, presence — without manual intervention, typically for high-volume standardised work.
Self-scheduling. The customer picks a slot from genuinely available capacity, which moves the constraint into the booking flow.

Limitations worth stating

Automated dispatch is only as good as the data behind it, and service data is notoriously imperfect: skills matrices go stale, job durations are estimated optimistically, and van stock is rarely accurate to the item. Optimising a plan against wrong durations produces a schedule that looks efficient and fails by mid-morning. Dispatchers also hold context no system has — which customer will tolerate a delay, which technician is best with a difficult site — which is why full automation is usually the wrong target for complex work.

How xMatix supports field service dispatch

xMatix Field Service provides an allocation console with three views over the same work: a map with live technician positions and travelled paths, an intraday timeline where dropping a job onto a lane schedules it, and a board where unassigned work is dragged onto a person. An optimize-day action fills the day's unassigned backlog into free slots, and the same console can allocate any record type — service orders, cases, visit plans — rather than being limited to one.

Underneath it, omni-channel routing assigns work by queue, required skill, capacity and presence, with accept, decline, transfer and reassign as first-class operations and a supervisor view of queue backlog and per-person load. Appointment scheduling adds slot capacity and holds, and an availability engine finds eligible, free bookable resources — which can be people, equipment such as a demo vehicle, or a facility such as a service bay.

Field execution is offline-first: job cards, checklists, parts consumption, labour hours, photographs and geofenced proof of attendance are captured on the mobile app without connectivity and reconciled through a durable outbox. Service commitments are measured against business-hours milestones, so a breach is visible before it happens rather than after.