The office phone never stops
It starts before eight. "What's the postcode for the first job?" "Who am I meeting there?" "What's the key safe code?" "Did anyone go out to this one before?" "What part did they fit last time?" The coordinator answers each call, looks it up, reads it out, and gets back to the email they were writing until the next call.
Engineers are not being lazy. The information exists, just not where they are. It is in the job system, the CRM, a spreadsheet or someone's inbox, and they are standing on a driveway with a phone.
Why the details are not reaching them
Usually the job reaches the engineer as a text, a WhatsApp message or a line on a printed schedule. That carries the bare minimum: a name, an address, a time. Everything else stays behind in the office.
Even where there is an engineer app, it may show only the job description, not the history or notes. The office system was set up for office staff, and nobody decided what an engineer needs to see before arriving.
The result is that the office staff become a human search engine for the field team.
A good deal of the most useful knowledge is not written anywhere at all. The coordinator just knows that the side gate sticks, that the customer works nights and should not be called before noon, or that the boiler at that address had the same fault last winter. When that person is off, the calls get longer and the answers get worse.
The cost of the calls
- Office staff interrupted all day, with their own work pushed back
- Engineers waiting on hold outside a customer's property
- Wrong information read out over a bad line
- Engineers arriving without the right part because they did not know what was needed
- Return visits that the job history would have avoided
| Question engineers call about | Where the answer usually lives |
|---|---|
| Address and contact | Job or CRM system |
| Access codes and parking | Notes field or a separate spreadsheet |
| Previous visits and fixes | Job history, old paper sheets |
| Parts needed or fitted before | Stock system, previous job sheets |
| Equipment details | Asset records or a folder of manuals |
What we build
- Information map. We list the calls the office gets over a normal week and where the answer to each lives. That tells us exactly what the engineer's screen needs.
- Connected job view. A phone app, or a secure mobile web page, shows each job with address and map link, contact, access notes, the equipment at the site, previous visits, previous notes and photos, and parts likely to be needed.
- Pulled from your systems. The job view reads from your job management system, CRM and stock system through their APIs, so there is no second place to maintain.
- Sensitive details handled properly. Access codes and personal details show only to the engineer assigned, only around the time of the visit.
- Notes back. Engineers can add notes for the next visit, like "dog in garden" or "stopcock under the stairs", which then appear for whoever goes next.
- Offline copy. The day's jobs are downloaded to the phone so the details are there even with no signal.
A quieter office
Engineers look it up themselves, on the driveway. The coordinator's phone rings for things that genuinely need a person, like a customer who has changed their mind or a job that has grown.
Fewer return visits are caused by missing information, because engineers can see what was done before and which parts were fitted. And the notes they add build up into a record that makes every future visit a little easier.
Is your office phone like this?
- Engineers call the office for addresses, codes and contacts
- Jobs are sent as texts or WhatsApp messages with minimal detail
- Engineers cannot see previous visits to the same site
- Access notes live in a spreadsheet or someone's head
- Coordinators struggle to get their own work done between calls