Runny is the AI dispatcher built into the dispatch board. Click Balance day and Runny picks the best assignment and order for the day's jobs.
Where Runny lives
At the bottom of the dispatch board. Look for the chat-style panel — that's the Runny popover.
What Runny does
Runny takes the day's jobs + the day's techs as input and produces an assignment plan that:
| Constraint | What it does |
|---|---|
| Customer-requested techs | Honored if your dispatch settings prefer it. |
| Member-favorite techs | Honored for membership visits. |
| Skills | Respected if skill-matching is on in your dispatch settings. |
| Drive time | Minimized across the day's route. |
| Conflicts | Off-shift hours, blocked windows, locked jobs, double-bookings are avoided. |
| Scoring weights | Falls back to your weights to break ties. |
How to run it
- Open the dispatch board.
- Click into the Runny popover at the bottom-right.
- Click Balance day (or type the equivalent prompt — Runny accepts free-text too).
- Runny streams its reasoning in real time as it works.
You'll see the tool-by-tool execution: "Loaded 14 jobs… computed 8 candidate plans… picked plan B."
Approving the plan
When Runny finishes, it shows the proposed changes:
- Job X moves from Tom → Sarah.
- Job Y's time slot shifts to 2:30.
- Etc.
You can:
| Action | What it does |
|---|---|
| Approve all | Applies every change. |
| Approve some | Tick specific changes. |
| Reject | Discard the plan and reroll. |
What Runny won't touch
- Jobs that are already En Route or further along. Once a tech is rolling, the assignment is locked.
- Jobs with a manual lock (a dispatcher pinned them).
- Jobs outside the day Runny is balancing.
Configuring Runny's behavior
Under the dispatch settings (org-wide), you can tune:
| Setting | What it controls |
|---|---|
| Customer favorite tech | Mode — strict, prefer, or off. |
| Member favorite tech | Same options. |
| Require skills for dispatch | Block assignments that fail skill match. |
| Scoring weights | How much weight to put on drive time vs continuity vs other factors. |
Per-tech settings (service areas, on-call status) also flow into Runny's math.
When Runny gets it wrong
It happens. Runny is making a best-effort plan from imperfect data — if your skills are wrong on the team page, Runny's assignments will be wrong too. Common things to check:
- Tech service areas (does the tech actually work in that zip?).
- Tech availability for the day (vacation, time off).
- Job time windows (did the customer commit to a slot?).