Equipify.ai

Troubleshooting

Dispatch

Capacity overload, wrong assignments, invisible backlog, and access-related failures—symptom-first triage aligned to dispatch triage workflows.

Quick answer

Start here

Dispatch symptoms usually reflect triage policy gaps: unclear priorities, missing parts readiness, or schedules that don’t reflect true technician time. Stabilize triage tiers and backlog aging visibility before tuning territories.

Issues & fixes

Dispatch board looks out of syncFilters, time zones, and stale client views mimic sync failures. Confirm server-side assignment timestamps, then reset filters and widen the time window.Tap to expand steps & related links

Recommended checks

  1. Check time zone — Dispatchers traveling or remote work often mis-set TZ.
  2. Reset board filters — Saved boards hide subsets silently.
  3. Verify websocket/network — Corporate proxies can interrupt live updates.
  4. Hard refresh — Eliminate client cache before deeper investigation.
  5. Compare to work order list — If list is correct, it’s a UI view issue—not data loss.
Playbook: Dispatch optimizationDispatch triage & capacityService schedulingField service operations
Same-day column is overloaded / everything is “hot”If everything is urgent, nothing is. Re-tier priorities, enforce access confirmation for commercial same-day, and publish honest capacity promises by region.Tap to expand steps & related links

Recommended checks

  1. Define hot criteria — Document what qualifies for same-day vs next-day.
  2. Add confirmation gates — Access and parts readiness before hard commit.
  3. Visualize backlog aging — Make overdue tiers visible daily.
  4. Rebalance territories — Seasonal shifts need periodic review.
  5. Measure first-trip completion — Hot boards should not increase callbacks.
Use case: Dispatch inefficiencyDispatch triage & capacityTechnician assignmentRoute efficiency