What a Customer Consistently Gets Wrong Describing a Fault Remotely

Why this matters

Every dispatcher and every tech who takes intake calls has heard "it's making a weird noise" and "it's just not working right" a thousand times, and every one of them knows those descriptions are close to useless on their own. A customer is not lying or being unhelpful; they simply do not have the trade vocabulary or the diagnostic frame to describe what they are seeing accurately. Knowing the specific, predictable ways customer descriptions go wrong lets you ask the right follow-up question instead of taking the description at face value and dispatching (or not dispatching) on bad information.

Location gets confused

Customers routinely misidentify which piece of equipment, or which end of a system, is actually the source of a symptom. A noise, a smell, or a puddle can travel or telegraph a surprising distance from its true origin, and a customer will report the symptom's location, not necessarily the fault's location. "It's coming from the kitchen" might mean the fault is nowhere near the kitchen; it means that is where the customer noticed it. Ask where the symptom is most intense and whether it changes as they move around, rather than accepting a single reported location as the fault's address.

Timing gets compressed or exaggerated

"It's been doing this for weeks" often means "I noticed it a few days ago and I'm not sure how long before that," and "it just started" sometimes means "I just started paying attention to it." Customers are not being dishonest here either; ongoing low-grade symptoms are easy to not notice until they cross a threshold of annoyance. Ask when they first definitely remember noticing it, separate from when it became bad enough to call, and treat the gap between those two answers as real diagnostic information (a slow-building fault vs. a sudden one).

Severity gets over- or under-stated in both directions

Some customers minimize ("it's probably nothing, just a little water") because they do not want to sound alarmist or do not want an expensive-sounding problem; others catastrophize a normal operating sound or a cosmetic issue into "it's about to explode." Neither framing is reliable on its own. Ask for specific, observable facts instead of the customer's own severity assessment: how much water, exactly where, does it stop or does it keep going, rather than accepting "a little" or "a lot" as calibrated terms.

Sound and smell descriptions are the least reliable of all

Untrained ears and noses default to the closest common comparison they can think of, which is frequently wrong. "It smells electrical" sometimes really is an overheating fault and sometimes is a completely unrelated smell the customer associated with electricity. "It's making a grinding noise" can mean anything from a genuinely failing bearing to a loose panel rattling. Treat any sound or smell description as a hypothesis to verify, not a confirmed fact, with one exception: if the description matches a hazard pattern (rotten egg smell, burning smell, grinding paired with visible smoke), act on the hazard immediately rather than waiting to verify it, because the cost of over-reacting to a false hazard alarm is far lower than the cost of under-reacting to a real one.

"It just stopped working" hides which of several very different failures happened

A customer who reports "it just stopped" is describing an outcome, not a mechanism. That single sentence could mean a clean, silent shutdown; a loud trip or bang followed by silence; a slow fade to nothing over several minutes; or intermittent operation that has now settled into "off." Each of those points somewhere different. Ask specifically: did it make any sound when it stopped, did anything visibly happen (a light, a smell, a spark), or did it just quietly go quiet.

What actually improves the description

• Ask about the moment right before, not just the symptom itself. What was happening right before it started acting up is often more diagnostic than the symptom description.
• Ask them to compare to a known-normal state, not to describe in the abstract. "Is it louder than usual, quieter, or a different kind of sound entirely" beats "what does it sound like."
• Move to photo or video as soon as it's safe and practical. A visual removes most of the translation error that language introduces; see the related video-call article for how to direct it well.
• Never treat a remote description as a confirmed diagnosis. Use it to decide whether to attempt remote triage at all, not as the final word on what is wrong.

References

• Trade-standard practice for phone and remote intake triage
• See related: Coaching a Customer Through a Live Video Diagnostic Call
• See related: Diagnose It Remotely or This Needs Eyes on Site (decision tree)