Customer communication for HVAC and appliance repair: the dispatch problem
Field service communication fails between the office and the van. Arrival windows, engineer updates, parts returns and the emergency call — what to automate in a mobile trade.
Osman Ramadan11 min read
On this page
A mobile trade has a communication problem that a fixed-premises business does not: the person doing the work is in a van, the person taking the calls is in an office, and the customer is at home taking a day off work to wait.
Every failure in this trade traces back to that gap. The customer who rings at eleven asking where the engineer is. The second visit because the part was not on the van. The emergency call that sat in a voicemail for two hours. This page covers what to automate about that gap, and what genuinely needs a person.
What we'll cover
The day-off problem
Worth stating plainly because it shapes everything else.
A customer waiting for an engineer has usually given up a working day. That makes them unusually sensitive to two things: not knowing when you will arrive, and having to do it twice. Almost every poor review in this trade is one of those two, rather than anything about the quality of the work.
The compounding effect: a customer who has waited four hours is already unhappy before the engineer knocks. The engineer then absorbs that, which is unfair to them and makes the job worse. Communication that manages the wait improves the visit itself, not only the customer's opinion of it.
What customers actually want is narrower than it sounds: a realistic window, a warning if it slips, and the visit to resolve the problem in one go. Those three are largely achievable, and the first two are pure communication.
Arrival windows and running late
The highest-value automation in field service, and the least technically demanding.
Send the window the day before, with the engineer's name. A named person arriving is a different experience from an unknown van.
Send a message when the engineer sets off, with a realistic arrival time. This single message removes most of the "where are you" calls, which are themselves an interruption for whoever is in the office.
Tell them when it slips, before they notice. A job overruns and the next customer is waiting. A message saying the engineer is running about an hour late, sent at the point you know rather than when they ring, converts a complaint into an inconvenience. This is the message that most distinguishes a well-run firm from a poorly-run one, and it costs nothing.
Make rescheduling easy when the delay is bad. A customer who would rather rebook than wait until six should be able to say so.
Confirm when the job is done, particularly where the customer was not present, with a note on what was carried out.
What the engineer needs before arriving
The other side of the same gap, and the one that prevents second visits.
Get the fault described properly at booking. Make, model, age, what it is doing, when it started, photographs of the appliance and its data plate. A structured intake captures all of that; a phone conversation captures whatever the customer thought to mention.
Send the engineer the history. Previous visits, what was done, what was replaced, any notes. An engineer arriving with the history is an engineer who diagnoses faster and does not repeat a fix that already failed.
Confirm access. Whether somebody will be in, where to park, whether there is a gate code, whether the appliance is reachable or behind a cupboard somebody needs to empty. Access problems cause a meaningful share of wasted visits and are entirely preventable with one question.
Flag anything unusual to the office. A job likely to need two people, or scaffolding, or a part nobody stocks, is better known the day before than on the doorstep.
The whole of that intake and briefing is a structured form, a lookup of history, and a message to the right engineer, which is straightforward to describe and tedious to wire together. On CodeWords you describe it in plain language and Cody, the automation builder, builds it, connects it to your job management and messaging, and deploys it. Automations connect to more than 3,000 integrations. The free plan covers light use, with Pro at $39 per month and Business at $100 per month as usage grows; details are on the pricing page.
Parts and the second visit
The most expensive failure in the trade, because a second visit costs a whole slot and gains no revenue.
Get the model number before the visit. Most second visits are caused by an engineer arriving without the right part because nobody knew which model it was. A photograph of the data plate at booking is the single cheapest prevention available.
Check stock against the likely fault before dispatch. Where the described symptom points at a common part, confirm it is on the van.
When a part is needed, order and communicate in the same motion. The customer should learn the part is ordered, roughly when it will arrive, and that you will book the return visit when it does — rather than hearing nothing and ringing on Thursday.
Chase the supplier automatically. An order that has not arrived by its expected date should surface without anybody remembering to check.
Book the return visit when the part lands, not when the customer rings to ask. This is the moment most firms lose the goodwill they had recovered.
Emergency calls
A distinct process with distinct rules, and worth designing deliberately.
Decide what counts as an emergency and write it down. No heating in winter, a leak, no hot water in a household with a baby. A definition means everyone applies the same one.
Acknowledge immediately, whatever the hour. A customer with a leak needs to know their message arrived. That acknowledgement should be honest about what happens next rather than implying somebody is already on the way.
Route to a person quickly. An emergency is a judgement call about urgency, capacity and safety. The automation's job is to capture the details, confirm receipt, and get it in front of somebody — not to decide.
Never let an automated response imply a visit that is not booked. This is the specific failure worth guarding against. A message that reads as a commitment when nobody has committed is worse than a slower honest reply.
Safety questions belong with a person, immediately. Anything mentioning gas, burning smells or electrical faults should reach someone who can advise, and the automation should say so rather than answering.
Quotes and approvals in the field
Where the engineer finds more than the booking covered.
Photograph and itemise, same as any trade. A customer seeing the corroded part approves faster and feels better about it.
Separate the must-do from the advisory. Customers routinely want the repair and not the upgrade, and offering that choice converts better than one figure.
Let the office see it. A quote raised in the field should reach whoever handles the paperwork without the engineer having to remember at the end of the day.
Record the approval where invoicing can reach it, so the figure agreed on the doorstep is the figure invoiced.
Servicing contracts and the recurring work
The steadier revenue in this trade, and the most consistently neglected.
Remind on the anniversary of the last service, with the appliance named. Generic reminders are ignored; specific ones are booked.
Book the next one while you are there where the customer is willing, and have the system carry that forward.
Chase renewals before they lapse, not after. A contract that has expired is a sale; one approaching expiry is a renewal, which is considerably easier.
Flag customers who have not been seen in two years. They have either moved, bought a new appliance, or gone elsewhere. Worth knowing which, and a short list per month is actionable in a way a database is not.
The cost of a second visit
Worth putting a number on, because firms consistently underestimate it and it changes which of the above to build first.
The direct cost is the slot. An engineer returning to a job that should have been finished is an engineer not doing a new job, so you lose the revenue of whatever would have filled that time, not merely the cost of the hour.
The travel is the part nobody counts. In a rural patch a return visit can be ninety minutes of driving for twenty minutes of work.
The customer cost is a second day off, and it is the thing that turns a satisfied customer into a poor review. A firm with an otherwise excellent reputation will find that almost all of its bad reviews mention a second visit.
The office cost is rebooking, explaining, apologising, and chasing the part — all of which lands on whoever is taking calls.
Put together, a second visit typically costs several times the value of the job that caused it. Against that, the preventions are small: a photograph of the data plate at booking, the history sent to the engineer, and one question about access. If you are deciding where to start and your second-visit rate is above about one job in ten, start there rather than with the arrival messages, however visible those are to customers.
Frequently asked questions
What should a field service firm automate first?
The on-the-way message with a realistic arrival time. It takes little to build, it removes most of the inbound "where are you" calls, and it is the thing customers notice most because it addresses the day they have given up.
How do we cut down second visits?
Capture the model number and a photograph of the data plate at booking, send the engineer the full history, and confirm access. Those three prevent most of them, and all three are intake problems rather than engineering ones.
Can we automate emergency response?
Acknowledge and capture, yes. Decide and commit, no. An emergency needs a person judging urgency against capacity, and an automated message implying a visit that nobody has scheduled does more damage than a slower honest reply.
Is WhatsApp useful for this trade?
Particularly so, because photographs matter on both sides — the customer's appliance before the visit, the engineer's findings during it. Confirm consent for the channel and make sure replies reach a person, since a channel nobody monitors is worse than not offering it.
What about engineers who dislike admin?
Design so the automation takes work off them rather than adding it. If a system requires the engineer to type more than they did before, it will not be used, and the arrival messages and history briefings should happen without them doing anything.
How do we handle out-of-hours messages?
Acknowledge honestly, stating when somebody will respond, and route genuine emergencies to whoever is on call under your own definition. The failure to avoid is silence, which leaves a worried customer assuming nothing is happening.
Does our job management software do this already?
Frequently some of it, particularly reminders and job notes, so check before adding anything. The gaps tend to be the on-the-way message, structured intake with photographs, and automatic supplier chasing, which are the three that matter most.
How do we get customers to send a photograph at booking?
Ask for it as part of the booking rather than afterwards, and say why: it helps the engineer bring the right part and avoids a second visit. Customers are markedly more willing when the reason is given, because the second visit is their problem too. Booking forms that request it without explanation get a much lower response.