Service dispatching that runs on your rules, not a new board.
Which tech gets which job lives in one dispatcher’s head. We encode those rules on the systems you already run. Triage before a truck rolls.
Official services partner of the platforms defining AI
NVIDIA
Anthropic
The jobs come in by email. The rules live in one head.
From service organizations we have sat inside: family-owned equipment dealers, PE-backed industrial distributors, multi-branch operations running hundreds of field techs.
The nearest tech is not the right tech
Routing decides by proximity, not part on the truck or error code. Techs arrive without the part; the second visit is booked before the first.
Jobs come in via email
Service requests land in an inbox and get matched by hand to technician availability, location, and specialty — across branches and hundreds of field techs.
Morning priorities, mined by hand
Service supervisors assemble the morning plan by hand from multiple dashboards, every day, before 9am. The data is all there; somebody still has to decide who rolls first.
The phones transcribe. Nothing reaches the CRM.
The phone system already transcribes every inbound call, and none of it becomes a job. Triage and dispatch validation happen after the truck rolls, if at all.
Every van is a warehouse
One dealer runs 374 active warehouses once you count technician vehicles. The same part sits scattered across branches and truck stock, shipped twice, over-sent, and aged out.
The rules retire when she does
Dispatch judgment lives in one long-tenured dispatcher: which customer cannot wait, which error code means a swap, who has the part. None of it is written down.
The repeat visit is a line item, not a feeling.
What we have measured inside multi-branch service organizations. Your numbers will differ — the two-week audit puts figures on yours before anything gets built.
From anonymized engagements — office-equipment dealers, industrial equipment distribution
We encode your exceptions.
No new system for your team to learn. The rules your senior dispatcher carries become the triage.
- 01
Shadow the dispatcher
We harvest the real rules from ERP dispatch logs, call transcripts, and the dispatcher’s head. The tribal knowledge becomes a written rule set — yours to keep.
- 02
Encode the triage
Inbound calls and emails become validated jobs — right tech, right part — before a truck rolls, on the ERP and phone system you already run.
- 03
Route the exceptions to humans
The system clears the routine majority. Judgment calls land in an exception queue with the rule behind each one documented. We monitor, tune, and hand over.
New dispatch software won’t know your Tuesday rules.
Dispatch software sells the board and the migration; telematics sells dots on a map. A dot tells you where the truck is, not whether the right part is on it. Neither survives your first Tuesday.
We encode your dispatch rules on the systems you run — AI reads each inbound call and email; your rules do the triage before a truck rolls, the rule set documented and handed over. Nobody sells that, so it has to be built.
Dispatch routes by proximity only, not by part availability or error code.
Led by Peter Enestrom.
Asked by service VPs and ops directors.
The straight answers, before you book anything.
Service dispatching is the work of assigning field technicians to incoming service jobs: who goes, in what order, with which part. The term covers HVAC dispatch, office-equipment service, and industrial equipment service — any operation where technicians roll with parts on a van.
Scheduling decides when jobs happen and builds the calendar. Dispatching decides who takes which job as work actually arrives — against part availability, error codes, skill, and how far behind each technician already is. Scheduling is the plan; dispatching is triage against it.
Because dispatch usually routes by proximity alone. Part availability lives in an inventory system that counts every van as a warehouse — one dealer runs 374 of them — and the error code on the ticket is never checked against either. The assignment is made before anyone looks.
Yes. The rules that decide which tech gets which job can be encoded on top of the ERP and phone system you already run. Inbound calls and emails become validated jobs — right tech, right part — before a truck rolls, and the judgment calls route to a human exception queue. No migration, no new board for the team to learn.
First-time fix rate is the share of jobs resolved on the first visit. Dispatch drives it because the outcome is largely set at assignment: a technician sent without the right part or the error-code context cannot finish the job. Rules-checked dispatch — part, skill, load — moves the metric more than anything that happens after the truck rolls.
Start with one workflow.
Tell us where your team loses hours. We will come back with a straight answer on whether AI can help, what it would take, and what it would pay.