Core requirements
Board visibility
A dispatcher should see status, location context, job duration, promised windows, skills and downstream impact without opening several records. Test the board on a busy day with at least 20 calls.
Skill and equipment matching
The system should help match technicians to equipment type, certification, geography and job category. Ask whether matching is rule-based, manual or driven by an add-on.
Emergency changes
Move an urgent no-cool call into the schedule, notify the assigned technician and update affected customers. Count clicks and identify which messages are automatic.
Field-office handoff
Technicians need complete customer, equipment, warranty and prior-work context. Dispatchers need usable status updates—not free-text notes they must interpret.
Demo checklist
- Live technician and job status
- Skill and territory rules
- Drag-and-drop reassignment with conflict warnings
- Arrival-window communication
- GPS context with a clear privacy policy
- On-call and after-hours workflows
- Dispatch metrics and audit history
Make the demo measurable. Give every vendor the same sample customer, schedule and job. Record steps, missing data, required add-ons and whether the workflow works on the mobile app.
