Software for technicians is bought by people who will never use it, which is why so much of it is abandoned in the third week. The features that win a demo are the office ones: the drag and drop board, the map, the colour coding. The features that decide whether the thing is still in use at Christmas are all on the van seat, and there are about four of them.
Today opens first, and opens without signal
A technician standing in a basement with one bar of reception wants the next address and the fault description in under three seconds. An app whose first screen is a dashboard, or which needs a round trip to a server before showing anything, gets replaced by a screenshot of the day sent over text within a fortnight, and the office goes back to ringing the van.
Marking a job done is one action
Every field between finished and done is a field that gets left empty or filled with a full stop. Capture the completion first, then ask for the detail while the van is moving. The notes that are actually worth reading are the ones somebody typed in ninety seconds, not the ones a mandatory form demanded at the end of a long day.
The paperwork is produced at the address
A work order written on site is a record. The same document written that evening is a reconstruction, and so is the photograph nobody took and the meter reading nobody wrote down. If the app cannot produce the document where the work happened, the office retypes it later, which is the exact cost the app was bought to remove.
Time on the job, because it is paid time
Arrival and departure per job give the real length of a call, which is the input every other figure depends on. It is also the record that answers a payroll question later. What counts as hours worked has a specific meaning under the Fair Labor Standards Act, and reconstructing it from memory a month afterwards is how disputes start.
Questions people ask about field service technician software
What if half the team will not use a phone app?
Then the board still works with the office updating status, and it is slower and less accurate. Adoption problems are usually design problems: if the first screen is their jobs and finishing one is a single tap, most teams are fine.
Does it need to work offline?
The day has to be readable without signal and completions should queue until there is some. Treat an app that goes blank in a basement as unsuitable whatever else it does.
Is there a charge per technician?
Not here. Dispatchzo Pro is one price for the whole team, so putting somebody on the board never costs more.