Service dispatch software: what it has to do before the price matters

Service dispatch software takes incoming jobs — breakdowns, installations, planned maintenance — and gets the right engineer to the right address with the right parts, then tells the customer when to expect them. For a field operation it sits closer to the centre of the business than any accounting system: a dispatcher working from a whiteboard and three phone lines is the constraint on how many jobs a day the company can complete.

What service dispatch software must handle

• Job intake with the details that decide scheduling: address, equipment, fault, access constraints, contract or SLA.
• Engineer skills and certifications, so gas, electrical or refrigerant work is only assigned to someone qualified.
• Scheduling with travel time, not just a slot — a 45-minute job two hours away is a half-day.
• Parts and van stock visibility, because the second visit is the expensive one.
• Mobile access for engineers, working offline in basements and plant rooms.
• Customer notifications: appointment confirmed, engineer en route, job complete.
• Job completion capture — photos, readings, signatures — feeding invoicing without retyping.

The features that matter less than the demo suggests

Automatic route optimisation looks impressive and helps most when engineers cover wide areas with short jobs. Where jobs are long or territories are tight, sensible zones and a dispatcher who knows the patch beat the algorithm. Predictive maintenance modules assume telemetry most equipment does not send. Treat both as nice-to-have and judge the tool on intake, skills matching, parts and mobile reliability instead — those are what break on a busy Monday.

Test the mobile app on the worst phone your engineers actually use, in a place with no signal. Field software fails at the van door far more often than in the office.

Heating and cooling work adds constraints a general tool ignores. HVAC dispatch software has to protect contract maintenance visits, enforce refrigerant and gas certifications at assignment, and survive the week demand triples.

What a small operation can run without software

1. Keep one job list everybody works from — a shared table with status, engineer, date and address beats a whiteboard because it survives people being off.
2. Record engineer certifications with expiry dates next to the schedule, so assignment is a check rather than a memory.
3. Log parts used per job, even roughly, to see where second visits come from.
4. Send confirmation and completion messages manually until volume makes it painful.
5. Measure first-time fix rate and jobs completed per engineer per day; those two numbers decide whether software would pay for itself.

Ettex Records covers that stage: a jobs table with status and assignment, an engineers table with skills and certification expiry, and a parts-used log per job, all visible to the office at once. When volume outgrows it, the same fields map onto the dispatch tools above — and you will know from your own numbers which features you are actually buying, alongside the work order tracking you already keep.