Can AI assign repair orders to my techs?
Auto Advisor's Dispatch agent plans assignments for unassigned repair orders with a deterministic algorithm, lowest current load first, ties broken by highest efficiency, and queues each one for a one-tap approval by default. It only fills empty assignments; it never reshuffles work a human already placed.
What does the Dispatch agent actually do?
Fills the job board: hands every unassigned repair order to the least-loaded tech, watches bay load, and warns when the day’s workload puts promise times at risk.
- 01
Plans assignments for unassigned open repair orders with a deterministic greedy algorithm: lowest current load first, ties broken by highest stored efficiency, capped at ten per run.
- 02
Queues each assignment for one-tap approval by default; in Auto mode it assigns inline through the same tested write, with a claim-first idempotency guard.
- 03
Echoes an executed assignment into your connected Tekmetric repair order as a write-back when the order carries an external reference, best-effort and never fatal to the internal assignment.
- 04
Raises a promise-time risk draft when open-RO load exceeds roughly two jobs per bay for the day.
- 05
Computes crew technician efficiency and today’s bay utilization from booked bay-hours.
What it reads to do the work
- Your open repair orders, technicians, bays, and appointments
- Your shop’s bay count (the default capacity yardstick)
- The autonomy mode you set for it (defaults to Approve)
How do I stay in control of what it does?
Every agent runs in the mode you choose, Off, Approve, or Auto, and every agent starts in Approve so a human signs off before anything happens. Here is what Dispatch can do, with the gate on each action, and the rails that hold in code, not in a policy document.
The actions, and their gates
- Assign an unassigned repair order to a technicianYou approve it
- Echo the assignment into Tekmetric when the RO is connector-syncedRuns logged, no tap needed
- Flag a promise-time risk dayYou approve it
The guardrails, held in code
- It only fills UNASSIGNED orders; it never reassigns an RO a human already placed, so it cannot reshuffle the board.
- Claim-before-write in Auto mode: the idempotency row is claimed before the assignment, so a same-day re-run dedupes and skips the write.
- One assignment per order per day.
- Approved executions re-validate the payload and reuse the same tested data-layer write; a write-back failure never breaks the internal assignment.
- No AI model anywhere: assignment and risk are pure code.
What does Dispatch not do yet?
Every claim on this page maps to shipped, tested code, and the same discipline applies to the limits. Here is where the edge of the product is today, stated plainly, so nothing on your shop rests on a promise.
- Assignment is load-and-efficiency based; it does not yet read technician certifications, so matching a specialty job to a specialty tech stays a human judgment.
- In Auto mode it assigns without waiting for a tap; the default is Approve, and the dial is yours per agent.
- Promise-time risk is a shop-level load heuristic, not per-RO promise tracking.
- It runs when triggered, not yet on its own timer.
Which numbers does Dispatch actually move?
Only measured numbers are listed here; a metric the product does not compute does not get claimed.
- Technician efficiency versus the 85 to 120% band
- Bay utilization versus the 85% target
- Assignments applied versus proposed per run, and risk days flagged
The rest of the crew
Dispatch is one of fifteen agents. Each has its own charter page, its own autonomy dial, and the same honesty rule.
Put Dispatch to work in your shop.
Request a Service-Drive Audit. We map exactly where the crew recovers time and revenue, on your numbers, in a live demo on sample data.
No obligation · no high-pressure pitch · plain, public pricing