Short answer: the technician should roll with the equipment history, the last promise to the customer, and anything the attic did last time. That information already exists in the office. The handover is the gap. AI can assemble it. A person still sends it, and the tech still decides what to do on site.
Missed calls and open estimates are the front door. This is the middle of the job: office to truck. The customer already told someone "the furnace on the left, the one we replaced the inducer on." That sentence dies in a note the tech will not see until they are on the roof.
What goes wrong without a handover
- The tech diagnoses a problem you already fixed last March.
- The part that is usually on that model is not on the truck.
- The customer is quoted something you already promised in a different tone.
- The office learns what happened when the tech calls from the driveway, which is also when the next customer starts waiting.
None of that is a lazy technician. It is a system that stores the history in Jobber or ServiceTitan and the useful sentences in email, then expects the field to mind-read.
What the handover should include
- Address, access notes, pets, attic-pull, no-freight-elevator — the things that waste a first visit.
- Equipment: brand, age, last repair, last part.
- Why we are there, in the customer's words, plus what the office already tried.
- What we must not promise. "We'll have you running tonight" is an office sentence, not a truck sentence, unless someone with schedule in front of them said it.
What AI may do
- Pull the last jobs and supplier notes onto one page.
- Draft a short brief the dispatcher can send by text to the tech who already has a phone.
- Flag missing access info before the roll, not after.
What it must never do
- Give the tech a new app to log into before they can see the job. If it does not arrive in a text or in the software they already open, it will not be read.
- Diagnose from the office. "It's the capacitor" in a briefing becomes a missed real failure on site.
- Change the schedule or the price because the model thought the job was smaller.
The questions to ask
- Does the brief come through a channel the tech already uses?
- Can I see which job and which email each line came from?
- Who sends it — software, or the dispatcher?
- What happens when the history is messy or missing? The correct behavior is to say so, not to smooth it over.
Jobber and ServiceTitan are named as the software shops already run. That is not a connector claim.
A realistic first step
For one week, have the office send a three-line brief before every first-time or no-heat job: last visit, equipment, access. Do it by hand if you have to. The jobs that still go sideways will tell you whether you have a writing problem or a finding-the-record problem. Only the second one needs software.
If you want those briefs assembled from the systems you already use — talk with us. If a better dispatch checklist is enough, we will say so.
Related: On the first cold night, do not let AI book the truck. · AI for missed HVAC calls · our approach for home services.