The Sound a Customer Describes Doesn't Match Any Known Fault: Decision Tree

Why this matters

Every experienced tech has a mental library of sounds mapped to causes, and every so often a customer describes something that does not fit any entry in it. The instinct is to translate their words into the closest-sounding known fault and diagnose toward that, but a forced match is one of the quieter ways a diagnosis goes wrong: you spend the visit confirming or ruling out the wrong thing because you anchored on a sound that was never actually happening. This tree is about getting an unfamiliar sound description into something you can actually act on, instead of guessing which known category it is closest to.

Start here: is the mismatch in the words, or in the sound itself

Before assuming this is a genuinely novel fault, rule out the more common explanation: the customer's vocabulary for describing sound is limited, and the actual sound is a familiar one described unusually.

1. Ask for a recording. A short phone-recorded audio or video clip resolves more of these than any amount of further questioning (see the related article on what a recorded sound clip can tell you remotely). If a clip is available, that supersedes verbal description for this step.
2. Ask for comparison language instead of adjectives. "Does it sound more like two pieces of metal rubbing, or more like moving air, or more like something electrical buzzing" gets further than "can you describe it again," because most people struggle to invent new descriptive words but can usually pick the closest comparison.
3. Ask about rhythm and timing separately from the sound quality itself. "Is it constant, or does it happen in a pattern, and if so how often" is a different question from "what does it sound like," and customers often answer it more precisely.

If these steps produce a description that now matches a known fault signature, proceed with that diagnosis. If the description still does not match anything familiar after this, move to the next section.

If the sound genuinely does not match a known signature

1. Do not force it into the closest category anyway. Anchoring on a plausible-but-wrong match wastes the visit confirming or ruling out something that was never the actual issue, and it delays finding the real one.
2. Widen your search rather than narrow it. Ask what else changed around the same time the sound started: a new installation nearby, a change in usage pattern, recent work done by someone else, a seasonal change. An unfamiliar sound is sometimes a familiar fault in an unfamiliar context (a normal sound from an adjacent system being misattributed, for instance) rather than a new fault type entirely.
3. Consider whether the sound is coming from a source other than the equipment you were called about. A sound attributed to one system can actually originate from a neighboring system, a structural element, or an unrelated appliance, especially in a space where several systems run near each other. Confirm the actual physical origin before diagnosing the wrong equipment entirely.
4. On site, try to reproduce the sound under the conditions the customer describes rather than under generic test conditions. A sound tied to a specific mode, load level, or timing will not necessarily show up during a routine check that never puts the equipment in that exact state.
5. If you can reproduce it, isolate systematically: does it change with load, with mode, with a specific component running or not. Build your own description of the sound now that you can hear it directly, rather than continuing to rely on the customer's original words.
6. If you cannot reproduce it during the visit, do not close the call as no-fault-found without a plan. Ask the customer to record a clip the next time it occurs, and set a clear, specific description of what conditions seem to trigger it based on everything gathered so far, so the next attempt has a real target instead of starting from zero again.

When the answer really is unfamiliar

Occasionally the sound truly does correspond to a fault outside your normal experience, an uncommon failure mode, an unusual interaction between components, or a condition you have not personally encountered before. That is a legitimate outcome, not a failure of process. The right move is escalation, a second opinion, a manufacturer technical line, or documented research, rather than committing to a confident diagnosis built on a forced match to something more familiar but wrong.

Recap

1. Get a recording if at all possible; it resolves most word-choice ambiguity.
2. Use comparison language and separate rhythm from sound quality when a recording is not available.
3. If the description still does not match anything, widen your search rather than force a familiar-but-wrong match.
4. Confirm the physical origin of the sound before diagnosing the wrong equipment.
5. If you cannot reproduce it, set up a clear plan for next time rather than closing the call unresolved with no path forward.

References

• Trade-standard practice for sound-based fault triage and customer intake
• Manufacturer documentation on characteristic fault sounds by component category
• See related: What a Recorded Sound Clip Can Tell You Remotely; It Only Fails When the Customer Operates It a Specific Way