Customer experience

Explaining what you found in plain English

A show, simplify and choose method for explaining plumbing and heating faults, with a jargon translation table and a written options template.

Ava research teamPublished 7 min read

On this page
  1. Why good engineers give bad explanations
  2. The method: show, simplify, choose
  3. A jargon translation table
  4. Explaining safety findings without drama
  5. Give options in writing
  6. Reading, language and memory
  7. Talking about cost without awkwardness
  8. When the customer disagrees with your diagnosis
  9. Example: one fault, explained twice
  10. Making it a team habit
  11. Frequently asked questions
  12. References

Key takeaways

  • Use a three-step method: show the customer the problem, explain it in one or two plain sentences, then give options with prices.
  • Replace jargon with what the part does and what happens if it fails.
  • Put options in writing; almost one in five adults aged 16 to 65 in England has very poor literacy, so keep it short and talk it through too.
  • What you say about a fault and a fix can become part of the contract, so be accurate rather than dramatic.

Why good engineers give bad explanations

Engineers spend their working lives with diverter valves, expansion vessels, PCBs and heat exchangers. Those words are precise and useful to them. To most customers they are noise. When an engineer says 'your diverter's sticking and the plate heat exchanger's furred up', the customer hears two things: something expensive is wrong, and I do not understand it. The natural reaction is suspicion.

That suspicion is not unreasonable. In the government's consumer protection study, people were asked how their consumer problems made them feel, and in 59% of the problems they reported they felt misled to some or a great extent[1]. Customers who do not understand what you found cannot tell an honest diagnosis from an invented one. A clear explanation is how you prove you are the honest kind.

Explanations usually go wrong in one of three ways. There is too much jargon. There is too much detail, so the important point is buried in a lecture on hydraulics. Or there is no choice, just a verdict and a price. The method below fixes all three.

The method: show, simplify, choose

  1. Show

    Let the customer see the problem: the leaking joint, the corroded part, the pressure gauge dropping, a photo on your phone of the inside of the boiler. Seeing is more convincing than any explanation.

  2. Simplify

    Explain in one or two sentences what the part does, what has gone wrong and what happens if it is left. No part numbers, no acronyms.

  3. Choose

    Give the options, usually two or three, with the price, the time and the trade-off for each. Then stop talking and let the customer decide.

A good test for the simplify step: could the customer explain it to someone else in the household after you have gone? If not, try again with fewer words.

A jargon translation table

Most firms find the same ten or so terms cause most confusion. Agree plain-English versions as a team, so every engineer explains them the same way.

Plain-English versions of common terms, agreed across the team
Engineer termPlain EnglishWhat the customer notices if it fails
Diverter valveThe switch inside the boiler that sends hot water either to the taps or to the radiatorsHot water but no heating, or the other way round
Expansion vesselA small tank that gives the water room to expand when it heats upPressure keeps dropping and the boiler needs topping up
PCBThe boiler's control board, its brainBoiler will not start or shows error codes
Heat exchangerThe part where the flame heats the waterNoises, poor heating, sometimes leaks
Sludge or sedimentRust and dirt that builds up inside the system over timeCold patches at the bottom of radiators, noisy boiler
Pressure relief valveA safety valve that lets water out if pressure gets too highWater dripping from a pipe outside
Condensate pipeThe small pipe that drains water from the boilerBoiler stops in freezing weather
Isolation valveA tap on the pipe that lets us turn off water to one fittingNothing, until we need to work on that fitting

Explaining safety findings without drama

The hardest explanations are about safety. When an engineer finds a gas appliance that is unsafe, the customer needs to understand the risk and what happens next, but fear makes people stop listening. Keep it calm and factual: what you found, why it matters, what you have done to make it safe and what they must not do.

Script: 'I've found that the flue isn't sealed properly, which means fumes could come back into the room. That's a carbon monoxide risk, so I've turned the boiler off and labelled it. Please don't turn it back on. I'll give you a written notice explaining this, and here are your options for getting it fixed.'

Then follow your firm's unsafe situations procedure and paperwork exactly. Do not exaggerate to win the repair, and do not play down the risk to avoid an awkward conversation. The service has to be performed with reasonable care and skill[2], and a clear, written warning is part of that.

Give options in writing

Spoken explanations are forgotten or misremembered by the evening. Follow up with a short written note, by text, email or on the job sheet, that the customer can show to a partner, landlord or adult child. It protects you as well: what you say about the service can become a term of the contract if the customer relies on it[3], and having the words written down means there is no dispute later about what was promised.

Template: 'What we found: the expansion vessel has lost its charge, which is why the boiler pressure keeps dropping. Option 1: recharge the vessel today, about 30 minutes, may only last a few months. Option 2: replace the vessel, about two hours, part ordered for Thursday. Option 3: leave it for now and top up the pressure as shown; call us if it drops below 1 bar. Prices for each option are on the attached quote.'

Always include a price for each option, or a clear price basis. Where no price is agreed for a service, the law only requires the customer to pay a reasonable price[4], which is exactly the kind of vague arrangement that leads to arguments.

Reading, language and memory

Do not assume a written note does the job on its own. The National Literacy Trust, drawing on the Survey of Adult Skills 2023, reports that 18% of adults aged 16 to 65 in England, about 6.6 million people, have very poor literacy skills[5]. Many of them are capable, intelligent people who simply struggle with dense text.

Adults aged 16 to 65 in England with very poor literacy skills
Adults aged 16 to 65 in England with very poor literacy skillsDonut chart. Very poor literacy skills: 18%.Very poor literacy skills: 18%18%
  • Very poor literacy skills 18%

Source: National Literacy Trust, 2026[5]

Show the data
ItemValue
Very poor literacy skills18%
  • Keep written notes short: what we found, the options, what happens next.
  • Use photos with arrows or circles rather than long descriptions.
  • Offer to talk the options through on the phone with the customer or someone they trust.
  • Avoid attaching long PDFs to texts; put the key facts in the message itself.
  • Ask 'What would you like to do?' rather than 'Do you understand?', which few people answer honestly.

Talking about cost without awkwardness

Many engineers are comfortable explaining a fault and uncomfortable saying what it will cost. They mumble the price, apologise for it or leave it to the office, and the customer reads the hesitation as a sign that something is off. Price is part of the explanation, not an awkward add-on.

  • Say the price clearly and then stop. Do not fill the silence with justifications.
  • Give the price for each option side by side, so the customer compares options rather than judging one number.
  • Say what is included: parts, labour, guarantee, disposal of the old part.
  • If you cannot price it on the spot, say when the written quote will arrive and stick to it.
  • Never quote one price verbally and a different one on the invoice without explaining why first.

When the customer disagrees with your diagnosis

Sometimes customers have read something online, or another firm told them something different. Treat the disagreement as a question to answer, not a challenge to win. Explain what you checked and what you found, show the evidence, and say plainly what you would do if it were your own home. If they still want a second opinion, offer to put your findings in writing so the next engineer can see what was tested. Customers remember the firm that was confident without being defensive, and many come back.

If the customer insists on a repair you believe will not fix the problem, record that you advised otherwise, in writing, before doing it. That protects you if the fault returns and keeps the relationship honest.

Example: one fault, explained twice

Example: a fictional customer's boiler keeps losing pressure. Engineer one says: 'Your vessel's flat and the PRV's weeping, I'd do both, it's the usual.' The customer, unsure whether this is real, asks for a written quote and gets a second opinion.

Engineer two shows the customer the dripping pipe outside, explains that the safety valve is letting water out because a small tank inside the boiler that absorbs expansion has gone flat, and offers three options with prices and times. He texts the options before he leaves. In this example the customer chooses the middle option on the spot and books the boiler service with the same firm, because she understood exactly what she was paying for.

Making it a team habit

  • Build the translation table together in a team meeting and keep it in the van and the job app.
  • Practise the show, simplify, choose method with real faults during induction.
  • Read a sample of written notes each month and check they would make sense to a customer.
  • Collect the questions customers ask most often and add plain answers to your website and quotes.

Plain English is not dumbing down. It is the professional skill of making a technical judgement understandable to the person paying for it. Customers who understand what you found trust what you recommend.

Frequently asked questions

How do I explain a boiler fault without sounding like I am upselling?

Show the problem, explain it in plain words, and give real options including the cheapest safe one. Put the options and prices in writing and let the customer decide without pressure.

Should I give technical details if the customer asks?

Yes. Some customers want the detail. Start simple and go deeper only if they ask; never use detail to avoid answering the question.

Do I need to put my findings in writing?

It is good practice for anything beyond a simple fix, and essential for safety findings. Written options also protect you if there is a later dispute about what was agreed.

References

  1. Department for Business, Energy and Industrial Strategy (GOV.UK) (2022). Consumer protection study 2022 (Figure 16, impact on consumers' feelings) (opens in a new tab) ↑

  2. legislation.gov.uk (The National Archives) (2015). Consumer Rights Act 2015, section 49 (opens in a new tab) ↑

  3. legislation.gov.uk (The National Archives) (2015). Consumer Rights Act 2015, section 50 (opens in a new tab) ↑

  4. legislation.gov.uk (The National Archives) (2015). Consumer Rights Act 2015, section 51 (opens in a new tab) ↑

  5. National Literacy Trust (2026). Adult literacy (opens in a new tab) ↑

Book a demo

See Ava handle your calls.

Book a short demo. We’ll walk through your calls and workflow, and agree what Ava should take care of.

Book a demo