The job is at their place, not yours
Parts and hours go on as the engineer works, the service order comes out at the end, and the next visit opens on what was done last time.
What actually happens, and where it lands
- The call comes in
Customer, which of their sites, which unit. All three already exist if you have been there before, so it is three clicks rather than three questions.
- The engineer is on site
Parts used and hours worked go on the job as they happen. Photographs of what was found go on beside them — which is what settles the argument three months later.
- It needs a part
Status goes to pending, and the board shows it as waiting rather than as somebody being slow. Nobody has to ring the office to ask.
- Next year, same unit
The job opens with everything that was done to it last time already there, including what the engineer wrote about the awkward bit.
Three things that are different here
A customer is not a place
One customer can hold several sites, and a site can hold several units. So "the Riverside job" means something precise rather than meaning whichever of their four buildings somebody had in mind.
The unit has a service record
The same equipment fields that hold a motor hold a rooftop unit or a boiler — make, model, serial, and every visit it has ever had.
The paperwork writes itself at the end
The service order comes out of the record as a branded PDF with the parts and hours already on it, so the van does not come back with a job to type up.
Where to look next
What it would not do for you
There is no scheduling calendar and no dispatch map. Jobs are assigned to people with a priority and a status; if you live and die by a drag-and-drop day view, this is not that.
See it with your own work in it
Half an hour, screen shared, with a couple of your real jobs typed in first. Tell us what you do and a few times that suit you this week.
Get in touch