Service Dispatching
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.
Built with the leading AI platforms
The broken Friday
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.
What manual costs
The repeat visit is a line item, not a feeling.
Reported operating examples show where manual work adds up. Your audit establishes the workload, error rates, and costs in your business.
From anonymized engagements — office-equipment dealers, industrial equipment distribution
How it works
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 work orders — 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.
Questions
Asked by service VPs and ops directors.
The straight answers, before you book anything.
What’s holding your business back?
A workflow ready for automation. An AI product you want to build. A problem that has sat on the roadmap for years. Let’s talk about what it would take to solve it.
Talk to Zaigo

