Utilities, telecoms, HVAC and equipment service companies decide who goes where, whether work can start, and whether a job is covered, hundreds of times a day. Helixor applies your rules to each of those decisions, explains them, and keeps a record for when a customer or regulator asks.
These are examples, not a complete list. A decision usually fits when it has written criteria, pulls from several systems, happens often, and someone may later ask why it went the way it did. Pick one to jump to it.
The dispatcher weighs certifications, parts on the truck, SLA deadlines, overtime rules, drive time and customer preferences, usually on a board and a phone. The nearest technician isn't always the right one, and when a job overruns, several appointments shift at once.
Certifications, SLA terms, hours rules and parts requirements go into the pack. The solver builds each technician's route for the day and, when a job runs long or an emergency comes in, repairs only the affected routes instead of rebuilding the board. Every assignment is checked by the decision core, so the dispatcher can always see why a technician was or wasn't picked. The pack holds the hard rules and the goal. The solver searches for the best plan that satisfies every hard rule, working from the same typed state the decision core uses. If no plan can satisfy them all, it tells you so instead of quietly breaking one. The solvers are built for GPUs, and that's where large plans solve fastest. Solvers are in Preview today.
{
"plan": "DISPATCH-2026-09-28-R3",
"receipt": "hx_proof_62f0b8e1d4a97c35e0b2a1d9",
"pack": "acme.dispatch_rules v18",
"action": "plan_repaired",
"changed_jobs": ["WO-3318207", "WO-3318221"],
"binding_constraints": ["DSP-CERT-REQUIRED-REFRIGERANT", "DSP-SLA-4H-COMMERCIAL"],
"input_sha256": "0f4d...b3c8",
"logged_at": "2026-09-28T10:52:31Z"
}Before hazardous work starts, the crew confirms lockout, gas tests, isolation points and permits. It's usually a paper form, and whether each box was genuinely checked is hard to prove afterward.
Helixor checks the submitted permit data against the job's requirements and returns cleared to start, hold, or stop. It doesn't replace the crew lead's judgment or any safety system. It makes sure the documented steps were done before work begins, and keeps a receipt that shows it.
Whether a repair is covered depends on the contract, install date, serial number, failure code, parts used and service history. Techs guess in the field, and the back office cleans it up weeks later.
Each completed job comes back covered, partially covered, or not covered, with the contract term that decided it, before the invoice goes out.
| Decision | What Helixor decides |
|---|---|
| Truck stock replenishment | Decide what each van gets restocked with, based on upcoming jobs. |
| Callback triage | Decide whether a repeat visit is a warranty callback or a new job. |
| Workload | Pattern |
|---|---|
| Mobile apps and depots | In-process on the device or depot server, so checks work offline |
| Scheduling and dispatch systems | Loopback sidecar or shared decision service |
| Replanning | Hosted solvers (Preview) |
Start with certification and rest rules on dispatch. They're written down, they're easy to test against last month's assignments, and they're what a customer or regulator asks about first.
Go deeper on helixor.dev: Deployment patterns ↗ • Core concepts ↗ • Receipts ↗
Bring a written policy and a handful of past cases. We'll turn it into a pack and run it next to your current process so you can compare.