Job explainer

You know exactly what "capacitor failed on the outdoor condenser unit" means. Most customers don't, and being handed a technical term with no explanation makes people nervous about a job that might actually be routine. This tool takes the fault note you'd write for yourself and turns it into two to four plain-English sentences you can send the customer — what was actually wrong, without the jargon and without overstating how serious it was.

Why the explanation is worth sending

A customer who understands what went wrong trusts the invoice more and the callout less. Send nothing and they're left guessing whether they were overcharged for something simple; send the raw technical note and they're left guessing what it even means. A short, honest explanation in plain terms closes both gaps at once, and it's the kind of small thing that makes a customer more likely to call you again rather than shop around next time.

A worked example

Notes in: "capacitor failed on the outdoor condenser unit." Explanation out: "The fault was down to a failed capacitor on your outdoor condenser unit — this is the part that gives the compressor motor the extra push it needs to start up. When it fails, the system either won't start or struggles to keep running properly. We've replaced the capacitor and tested the unit, and it's now running as it should." Same fault, written so the customer knows what happened and what was done about it.

What this isn't

This is a first draft, generated only from the notes you type in — it doesn't know anything about the job beyond what you tell it, so read it back before sending it to a customer. It's built to explain, not to alarm, but it can't judge tone as well as you can, and it won't catch it if your original notes were unclear or wrong. Treat it as a quick draft that saves you writing the explanation from scratch, not a substitute for checking it says what actually happened.