Maps
Geographic context on the Dispatch board: site pins, operational bases, and a straight line between them. This is not live van tracking, customer ETA, or a route optimizer.
Path: Operations → Dispatch → panel Map. Pins are sites, not moving technicians. A visit uses the work-order site, not the customer billing address.
Capability/entitlement travel_intelligence where gated.
What the Map panel shows
Section titled “What the Map panel shows”- Open Dispatch. Default panel is Schedule (lanes). Switch to Map.
- Pins are Sites (job geography) and technician home / operational bases.
- The line between points is a straight polyline for context. It is not the driving route OSRM would use for travel minutes.
Empty pin: the site has no latitude/longitude. On the site profile use Geocode address (not live GPS). Until then, travel feasibility is unknown — a warning, not a hard block. You can still Assign.
Travel feasibility is separate
Section titled “Travel feasibility is separate”Find candidates can enrich travel minutes via OSRM or the Fake provider. TRAVEL_INFEASIBLE is a hard constraint on manual assign (overridable with Assign anyway). That math does not draw roads on the Map panel and does not reorder the day’s stops.
What V1 does not ship
Section titled “What V1 does not ship”Not released: live van tracking (live_gps), customer ETA, route optimization. Field PWA and native Field do not stream location in 1.0.0.
Map tiles follow workspace/platform map settings (API keys in the UI — do not paste keys into documentation). A blank map is usually a missing key, CSP, or a locked-down office network. Dispatch lanes still work without tiles.
If it fails
Section titled “If it fails”- No pins — site not geocoded; Geocode on Sites.
- Travel always unknown — missing coordinates or provider down (assign still allowed).
- Expecting the map to move with the technician — not in this product version.