The 'You Didn't Tell Me' Trap
Why this matters
"You never told me that" is one of the most common lines in a bad review, a chargeback dispute, or a heated phone call, and in a surprising number of cases the tech did say it, just once, quietly, while packing up. A fact spoken once and never written down did not fail to be communicated, it failed to be retained, and the customer's memory of the conversation will not hold up against their memory of the bill. Preventing this trap is not about talking more, it is about making the important facts survive past the moment you leave the driveway.
Why customers forget what you told them
This is not usually dishonesty. A few things are working against you every time you explain something verbally:
- Attention was elsewhere. They were signing a form, watching a kid, or thinking about the cost while you talked.
- Jargon did not land. If a term went past them, the sentence around it did not stick either. See related: Translating Jargon Without Sounding Condescending.
- Timing was bad. Information delivered while you are packing tools and heading for the door gets a fraction of the attention information delivered while you have their full focus.
- There was too much of it. Five things said in thirty seconds means the customer retains one, and it is rarely the one that later matters.
- Stress compresses memory. A customer dealing with a broken system, a leak, or a no-heat call is not in a great state to retain new information, even when they nod along.
None of this makes the customer wrong to say they were not told. From their side, they genuinely were not, because it did not stick.
The fix: say it, then put it in writing, then confirm it landed
A fact that matters for a future decision, a warranty condition, or a safety outcome needs to clear three checkpoints, not one:
- Say it out loud, at a moment when they are actually listening, not mid-task or mid-packing-up. If you notice their attention drifting, pause and re-anchor it: "This next part matters, so bear with me a second."
- Write it down on the invoice notes, the leave-behind, or a follow-up message. See related: The Leave-Behind That Actually Gets Read. Verbal-only communication has no defense later; written communication does.
- Confirm it landed, using the teach-back method: ask them to repeat the key point back in their own words, or ask a specific question that only makes sense if they understood. "So just to make sure that's clear, what would you do if you heard that sound again?" A nod is not confirmation. A correct answer is.
What belongs in writing every time, no exceptions
Some facts are important enough that verbal-only delivery is never acceptable, regardless of how attentive the customer seemed:
- Anything that affects warranty coverage or voids it under certain conditions.
- Any safety-relevant limitation ("this repair fixes X, but Y is still a risk, watch for Z").
- Scope boundaries: what was fixed, and just as important, what was not.
- Any recommendation you made that was declined. If you flagged a related issue and the customer chose not to address it, write that down. This protects both sides: the customer has a record to make an informed choice later, and you have a record that you disclosed it.
The scope-boundary version of this trap
A specific and very common version: you fixed the reported problem but noticed something else during the visit, mentioned it in passing, and did not write it down. Weeks later a different issue surfaces and the customer says "well, you were just here, why didn't you catch this." If you did flag it and it is not written anywhere, you have no way to show that. Every observation outside the original scope of the call, even a minor one, belongs in the notes.
The trap in reverse: over-documenting as a shield
Do not swing so far toward documentation that every visit generates a wall of disclaimers designed to protect you rather than inform the customer. A leave-behind or invoice note that reads like a legal waiver undermines trust just as much as under-communicating does. Write down what genuinely matters to their future decisions and safety, not everything you are technically capable of saying.
References
- See related: The Leave-Behind That Actually Gets Read
- See related: Translating Jargon Without Sounding Condescending
- See related: Documenting a Customer Refusal the Right Way
- Trade-standard practice for service documentation and dispute prevention