Multi-tech dispatch is the tool for orgs with more than one field tech. It takes today's due stops and splits them across the techs you specify, keeping each route geographically tight and the stop counts balanced.
Prerequisites
- Your org needs at least two operators with role
TECHorADMIN. - Each tech should have a home base address set in their profile — the dispatcher clusters from that starting point. If no home base is set, the org's business address is used.
- Every eligible customer needs a geocoded address (lat/lng).
Run a dispatch
From the web admin, open Dispatch → New dispatch. Pick the date, the techs, and optionally their start locations (defaults to home base). Click Dispatch.
The dispatcher runs a clustered k-means over the due stops with a load-balancing constraint so no single tech gets more than 15% above the average stop count. It writes the result as a RoutePlan row per tech.
Reviewing and adjusting
Each tech's plan appears as a column on the dispatch board. You can drag a stop from one tech to another; the app re-computes drive time on the fly. Once you're happy, click Publish and every tech's mobile app pulls the updated route on their next sync.
Idempotency
Running dispatch again for the same date replaces the previous plan for that date. If a tech has already checked in to a stop, that stop is pinned and stays on their route regardless of re-dispatch — no work is lost.
When not to use it
For a solo op, just plan a single route from the mobile app — dispatch adds latency without adding value.