The Questions That Get a Useful Video From a Customer
Why this matters
"Can you send me a video of that" gets you ten seconds of a dark hallway with the sound muffled by a thumb over the microphone, most of the time. The problem is rarely that the customer will not cooperate; it is that nobody told them what actually makes a video useful. A few specific, plain-language prompts at intake turn a wasted clip into something you can genuinely triage from, and that difference is the gap between rolling with a plan and rolling blind.
Why the generic ask fails
"Send me a video" leaves every decision to a non-technical person: what to point at, how close to stand, whether to include sound, how long to record. Left to guess, most customers film the symptom for two seconds from across the room, in bad light, with no context. The fix is not a longer explanation; it is a short, specific list of instructions given at the moment you ask.
The five prompts that do the work
Give these as simple instructions, not a checklist read aloud verbatim. Adjust the wording to the specific complaint, but hit all five ideas.
- "Show me the whole thing first, then move in close." This gets you the wide context (what unit, what setting, what is around it) before the close-up, so you are not guessing what you are even looking at.
- "Let it run for at least twenty or thirty seconds before you stop recording." A two-second clip cannot show a rhythm, a hesitation, or a sound that comes and goes. Time is what turns a snapshot into a diagnosis.
- "Hold the phone still and get close enough that the microphone can actually pick up the sound." Most phone microphones are worse than customers expect. If sound matters to the complaint, tell them explicitly to get close and stay quiet themselves while recording.
- "Film it from the start, if you can catch it starting up (or a cold start) as well as while it's running." A fault that only shows on startup, or only after it has run a while, needs to be captured at that specific moment. Ask which part of the cycle the problem happens in, and have them film that moment specifically.
- "Tell me out loud, on the video or in the text after, what you're seeing or hearing that's not normal." Their narration, even a single sentence, tells you what they think matters, which may or may not be what actually matters, but it saves you from misreading the frame.
Match the ask to the complaint
Do not send the same five prompts for every call. Tune the emphasis to what you are actually trying to learn.
| Complaint type | What to emphasize |
|---|---|
| An intermittent noise | Record length (30+ seconds), stillness, getting close for sound |
| A startup or cold-only fault | Catch the exact moment it starts, not just steady running |
| A leak or drip | Wide shot for source, then close on the drip itself, with something for scale |
| A visible motion problem (wobble, hesitation) | Steady framing, moderate distance so the whole motion is in frame |
| An error display or reading | Close, steady, well-lit shot held long enough to read, not just glimpse |
What to do with a video that still is not useful
Sometimes, even with good instructions, the video does not tell you enough: bad lighting, a shy or rushed customer, a phone that cannot focus close. Do not keep asking for reshoots past one polite follow-up. Two rounds of poor video is a signal that this call needs a technician on site or a live video call instead of an asynchronous clip. Know when to stop asking and just schedule.
References
- Trade-standard practice for remote triage and customer intake
- See related: What a Customer's Phone Video Can (and Can't) Tell You; Reading the Customer's Photos Before Arrival