The Words That Build Trust Mid-Diagnosis vs the Words That Erode It
Why this matters
The facts of an unresolved diagnosis are usually the same whether the customer ends up confident in you or not. What changes the outcome is the specific language you reach for under pressure. A handful of phrases reliably build confidence, and a handful of very similar-sounding phrases reliably tear it down, and most techs use both without noticing which is which. This is the field key: the exact contrast, side by side, so you can hear the difference before it costs you a customer's trust.
The comparison table
| Situation | Erodes trust | Builds trust |
|---|---|---|
| You have not found the cause | "I'm not really sure, could be a bunch of things" | "I've ruled out the power supply and the sensor, that leaves two things I'm checking next" |
| You need more time | "This one's tricky, I'll keep looking" | "I've run everything I can with what's on the truck, I need [a specific part or test] to go further, here's the plan" |
| The customer asks for a timeline | "Hopefully soon" | "I expect to have a confirmed answer within [a bounded window], and I'll update you either way, even if it's not resolved by then" |
| You found a contributing factor, not the root cause | "Found it, this should fix it" | "This is a contributing factor, I want to confirm it's the whole story before I call this done" |
| The customer pushes for a guess | "Probably the [component], let's just try that" | "I don't want to guess on something this important, here's what confirming it actually takes" |
| You are billing for unresolved time | Silence about the bill until it arrives | "I want to be upfront that this diagnostic time is billing even without a confirmed answer yet, here's why, and here's where we stand" |
Why the "erodes trust" column fails, specifically
Each weak phrase shares a common flaw: it is vague where a strong version would be specific, or it avoids naming the actual state of things because that state feels uncomfortable to say out loud. "Could be a bunch of things" sounds identical whether you have ruled out nothing or ruled out five possibilities, so the customer cannot tell competent uncertainty from a shrug. Specificity is what signals real work happened, even when the work has not yet produced an answer.
Why the "builds trust" column works, specifically
Every strong phrase does the same three things: it names what has actually been confirmed, it names what has not, and it gives a next step or a bound. None of the strong phrases claim more certainty than you actually have. They simply refuse to be vague about the uncertainty itself. A customer cannot tell the difference between a real diagnosis in progress and someone stalling unless you give them evidence, and specific language is the evidence.
The phrases to retire entirely
A few phrases are close to useless regardless of context, because they carry no information:
- "These things happen." (Says nothing about this specific case.)
- "It's an older unit, you know how it is." (A real observation, age and wear, wrapped in a dismissive tone that reads as an excuse rather than a diagnosis.)
- "I've seen this before." (Meaningless unless followed by what you saw and what it turned out to be.)
- "Let's just see what happens." (Fine as an internal plan, corrosive as something you say to a customer with no explanation of what you are watching for or why.)
Each of these can be replaced with a specific version carrying the same honest content: "this component's failure rate does increase past its typical service life, and here's why I think that's what's happening here" says the same thing as "these things happen" but actually supports it.
The one thing that overrides all of this
None of these phrases matter if they are not true. Choosing the "builds trust" language to describe work you have not actually done, or confidence you do not actually have, is worse than an honest weak phrase, because it is a lie dressed as competence, and it collapses completely the moment the diagnosis proves you wrong. The language in this reference is for communicating real progress and real uncertainty clearly. It is not a script for making thin work sound thorough.
References
- See related: Telling a Customer You Haven't Found It Yet, Without Losing Their Confidence
- See related: The Difference Between Honest Uncertainty and Looking Incompetent
- Trade-standard practice for transparent customer communication during service