Customer communication for HVAC and appliance repair: the dispatch problem

HVAC (heating, ventilation and air conditioning) and appliance repair firms should automate five messages first: the arrival window, the on-the-way update, the late warning, the pre-visit intake and the part-ordered notice. These close the gap between the engineer in the van, the office taking calls and the customer waiting at home.

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, and the emergency call that sat in voicemail for two hours. This page covers what to automate and what needs a person.

What we'll cover

• The day-off problem
• Arrival windows and running late
• What the engineer needs before arriving
• Parts and the second visit
• Emergency calls
• Quotes and approvals in the field
• Servicing contracts and the recurring work
• The cost of a second visit
• Frequently asked questions

Key takeaways

• The on-the-way message with a realistic arrival time removes most "where are you" calls and costs little to build.
• A photograph of the appliance data plate at booking is the cheapest way to prevent a second visit.
• Automation should acknowledge and capture an emergency call, and a person should decide the response.
• An automated message must never imply a visit that nobody has booked.
• A specific service reminder that names the appliance gets booked, and a generic reminder gets ignored.

The day-off problem

The day-off problem is that a customer waiting for an engineer has usually given up a working day. That makes the customer sensitive to two things: not knowing when the engineer will arrive, and needing a second visit. Most poor reviews in this trade cite one of those two, not the quality of the work.

A customer who has waited four hours is already unhappy when the engineer knocks, and the engineer absorbs that. Communication that manages the wait therefore improves the visit itself, not only the customer's opinion of it.

Customers want three things: a realistic window, a warning if it slips, and a visit that resolves the problem in one go. The first two are pure communication.

Arrival windows and running late

The highest-value automation in field service is the arrival message sequence, and it is also the least technically demanding. It has five parts:

1. Send the window the day before, with the engineer's name. A named person arriving is a different experience from an unknown van.
2. Send a message when the engineer sets off, with a realistic arrival time. This one message removes most "where are you" calls, which interrupt whoever is in the office.
3. Tell the customer when the visit slips, before they notice. A message saying the engineer is running about an hour late, sent when you know, turns a complaint into an inconvenience.
4. Make rescheduling easy when the delay is long, so a customer who would rather rebook than wait until six can say so.
5. Confirm when the job is done, with a note on what was carried out, particularly when the customer was not present.

What the engineer needs before arriving

Before arriving, the engineer needs a structured fault description, the job history, confirmed access and a flag for anything unusual. This is the other side of the same communication gap, and it prevents second visits.

• Get the fault described properly at booking: make, model, age, what the appliance is doing, when it started, and photographs of the appliance and its data plate. A structured intake captures all of that, while a phone call captures what the customer thought to mention.
• Send the engineer the history: previous visits, what was done, what was replaced and any notes. The engineer diagnoses faster and does not repeat a fix that already failed.
• Confirm access: whether someone will be in, where to park, whether there is a gate code, and whether the appliance is reachable. One question prevents most access problems.
• Flag anything unusual to the office. A job that needs two people, scaffolding or an unstocked part is better known the day before than on the doorstep.

This intake and briefing is a structured form, a history lookup and a message to the right engineer. On CodeWords you describe it in plain language, and Cody, the automation builder, builds it, connects it to your job management and messaging tools, and deploys it. Automations connect to 3,000+ integrations (CodeWords integrations page, 2026). The Free plan covers light use. Pro costs $39 per month and Business costs $100 per month (CodeWords pricing page, 2026). Details are on the pricing page.

Parts and the second visit

To prevent a second visit, get the model number before dispatch, check stock against the likely fault, and tell the customer when a part is ordered. A second visit is the most expensive failure in the trade, because it uses a whole slot and earns no extra revenue.

• Get the model number before the visit. An engineer who arrives without the right part usually did not know the model. A photograph of the data plate at booking is the cheapest prevention.
• Check stock against the likely fault before dispatch. When the symptom points at a common part, confirm the part is on the van.
• Order and communicate together. Tell the customer the part is ordered, roughly when it arrives, and that you will book the return visit then.
• Chase the supplier automatically. An order that has not arrived by its expected date should raise an alert without anyone remembering to check.
• Book the return visit when the part arrives, not when the customer rings. This is the moment many firms lose goodwill they had recovered.

Emergency calls

Emergency calls need their own written rules. Automation should acknowledge the call, capture the details and put the call in front of a person quickly. A person decides the response, because urgency, capacity and safety are judgement calls.

• Define what counts as an emergency and write it down, for example no heating in winter, a leak, or no hot water in a household with a baby. A written definition means everyone applies the same one.
• Acknowledge immediately, whatever the hour. A customer with a leak needs to know the message arrived. The acknowledgement should say honestly what happens next.
• Never imply a visit that is not booked. A message that reads as a commitment when nobody has committed is worse than a slower honest reply.
• Send safety questions to a person immediately. Anything that mentions gas, burning smells or electrical faults should reach someone who can advise, and the automation should say so instead of answering.

Quotes and approvals in the field

For quotes in the field, the engineer photographs and itemises the extra work, the customer approves it, and the approval reaches invoicing. This covers cases where the engineer finds more than the booking covered.

• Photograph and itemise. A customer who sees the corroded part approves faster and trusts the quote more.
• Separate the must-do from the advisory. Customers often want the repair and not the upgrade, so offer that choice instead of one figure.
• Let the office see the quote. A quote raised in the field should reach the paperwork team without the engineer remembering 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

Servicing contracts give the steadier revenue in this trade, and automation keeps them from lapsing through four routines:

• Remind on the anniversary of the last service, with the appliance named. Generic reminders are ignored, and specific ones get booked.
• Book the next service while the engineer is there, when the customer is willing, and have the system carry the date forward.
• Chase renewals before they lapse. An expired contract is a new sale, and a contract near expiry is a renewal, which is easier.
• Flag customers not seen in two years. They have moved, bought a new appliance or gone elsewhere, and a short monthly list is actionable where a database is not.

The cost of a second visit

A second visit costs the lost slot, the travel, the customer's second day off and the office time to rebook. Counting these costs changes which automation to build first.

• The slot: an engineer returning to an unfinished job is not doing a new job, so you lose the revenue the slot would have earned, not only the hour.
• The travel: in a rural area, a return visit can mean a long drive for a short repair.
• The customer: a second day off turns a satisfied customer into a poor review.
• The office: rebooking, explaining, apologising and chasing the part all land on whoever takes calls.

The preventions are small: a data plate photograph at booking, the history sent to the engineer, and one question about access. If your second-visit rate is high, start with those preventions before the arrival messages, however visible the messages are to customers.

Frequently asked questions

What should a field service firm automate first?

Automate the on-the-way message with a realistic arrival time first. It is cheap to build, it removes most inbound "where are you" calls, and customers notice it most because it addresses the day they gave up.

How do we cut down second visits?

Capture the model number and a data plate photograph at booking, send the engineer the full history, and confirm access. These three steps prevent most second visits, and all three are intake tasks, not engineering tasks.

Can we automate emergency response?

Automate the acknowledgement and the capture of details, but not the decision or the commitment. An emergency needs a person to judge urgency against capacity, and an automated message that implies an unscheduled visit does more damage than a slower honest reply.

Is WhatsApp useful for this trade?

Yes, because photographs matter on both sides: the customer's appliance before the visit and the engineer's findings during it. Confirm consent for the channel and make sure replies reach a person, since an unmonitored channel is worse than none.

What about engineers who dislike admin?

Design the automation to take work off engineers, not add it. A system that makes the engineer type more than before will not be used, so the arrival messages and history briefings should run without the engineer doing anything.

How do we handle out-of-hours messages?

Acknowledge the message honestly, state when someone will respond, and route genuine emergencies to the person on call under your own definition. Avoid silence, which leaves a worried customer assuming nothing is happening.

Does our job management software do this already?

Job management software often covers reminders and job notes, so check it before adding anything. The usual gaps are the on-the-way message, structured intake with photographs and automatic supplier chasing, and these three matter most.

How do we get customers to send a photograph at booking?

Ask for the photograph as part of the booking and say why: it helps the engineer bring the right part and avoids a second visit. Customers send photographs more readily when they know the reason. Booking forms that give no reason get fewer photographs.

Related reading

• Automated dispatch and job updates via WhatsApp for field service teams
• WhatsApp automation for plumbers, electricians, and repair techs
• Customer communication for independent garages: the approval bottleneck
• CodeWords integrations and templates