How to Question a Customer to Pin Down When a Fault Happens

Why this matters

"It just does it sometimes" is where most intermittent diagnoses die. When a fault happens is often the single biggest clue to why, and the customer holds that data. They just do not know how to hand it to you, and the standard questions are too blunt to pull it out. A tech who can interview for timing leaves with "every cold morning, right after the first cycle" instead of "it has been acting up." One is a lead. The other is nothing.

Do not ask "when did it start" cold

It is the obvious question and it gets a useless answer, because people do not file faults by date. They remember events. Ask around the fault, not straight at it, and you get something real.

Anchor to events the customer remembers

Tie the fault to things that already have dates attached: a holiday, a birthday, the move-in, the kids going back to school, the last big storm, a power bill that looked high. "Was it doing this before or after the Fourth of July?" gets a real answer where "what date did it begin" gets a shrug.

Separate when they noticed from when it started

The day they noticed is rarely the day it began. Push past first notice: "Thinking back before that, was there anything small, a noise, a smell, a light flickering, a bill creeping up?" Onset usually predates the complaint, and that gap is itself a clue, the fingerprint of a slow leak, a drifting part, or a filter loading up over weeks.

Pin the conditions, not just the clock

Timing is more than the hour of the day. For each occurrence, dig for what was true when it happened:

• What was running or in use at that exact moment?
• What was the weather doing, hot, cold, wet, the first cold snap of the season?
• Who was home, and what had just been switched on?
• Was it at start-up, at shut-down, or during steady running?

Counter a vague answer with a menu

When they say "I do not know," do not accept it, offer choices. "Morning, afternoon, or night?" "Every day, or once in a while?" "When it is hot out or cold out?" A menu jogs a memory that an open question leaves buried. Most customers who answer "no idea" answer a specific either-or just fine.

Test the answer against a mechanism

A timing pattern only helps if it points at a physical cause. "Only when it rains" points at water intrusion or a ground fault. "Only in the afternoon" points at heat or peak load. "Only right after it starts" points at a start component. If the timing they describe fits no plausible mechanism, keep digging, because you may be looking at two faults or a coincidence, not one clean pattern.

Write it in their words, then translate

Capture the raw answer ("acts up when the AC and the dryer are both on") before you interpret it. The raw version is the data. Your translation (shared circuit, combined draw) is the hypothesis, and keeping them separate stops you from locking onto a theory before the evidence earns it. Feed the confirmed timing into a timeline to find the pattern across occurrences.

References

• Trade-standard practice for customer interviewing and fault-history taking
• See related: How to Build a Timeline of When a Fault Appears; How to Log an Intermittent Fault Over Days