The dispatch board is where field service software is either adopted or quietly abandoned. Most evaluations test it on an empty calendar.
Test it at eight in the morning, not in a demo
A demo dispatch board has six jobs and no conflicts. A real one has forty, three of which are emergencies, one technician calling in sick and a parts delivery that did not arrive.
The evaluation that predicts adoption is: take a real day from last month, load it, and then break it. Pull a tech. Add two emergencies. Move a four-hour job across the city. Count the clicks and count the customers who need to be told.
What separates products at this size
Reassignment cost. Moving a job between technicians should be one drag and one automatic notification, not a delete and a rebook.
Travel awareness. A board that does not know two jobs are forty minutes apart will produce a schedule no one can run.
Capacity visibility. Can the person answering the phone see, without asking, whether Thursday afternoon has room?
The customer side. Arrival windows, on-the-way notifications and reschedules that reach the customer without a phone call are the largest single reduction in office workload most shops get from this software.
Service boards and project calendars are different tools
A service-call shop needs the board described above. An installation contractor needs a calendar that holds a crew against a multi-day job, a delivery date and an inspection, and that does not fall over when the job slips a week.
Products lean one way or the other. Which way yours needs to lean is the shop-type question, and it should be settled before the demos start rather than during them.
Sources
- Workyard — secondary unverified, read
Vendor pricing changes without notice. Every figure above carries the date it was read. If a vendor’s current page disagrees with this one, the vendor’s page is right and this one is stale — and that is a bug worth reporting.
