Customer video troubleshooting: let the customer show the fault
The short version.
- Customer video troubleshooting means the customer films the fault on their own phone and your team diagnoses from the footage, instead of from a description, a call, or a visit.
- Aberdeen puts the direct cost of one truck roll at $200 to $300, and one in four first visits fails, so every ticket you can settle from a 60-second video is money that stays in the department.
- The request has to be guided. "Send us a video" gets you the wrong side of the machine. A flow that asks for the fault in action, the label, the surroundings and the sound gets you a diagnosis.
- Written for heads of support, service operations managers and field service managers at companies that support appliances, equipment, installations, e-bikes, HVAC or telecom hardware. Software teams with screen recordings: this one isn't for you.
One quick clarification before anything else, because most of what ranks for this term is about screen-recording tools for software bugs. This post is about physical things. The boiler that locks out at 6 a.m., the e-bike motor that cuts under load, the router with a light nobody can name, the packaging line that jams on one shift only.
If you run support or service operations for products like that, the ticket usually starts the same way. The customer writes "it's making a noise", the agent asks four questions, the customer answers two, and three days later an engineer drives out to find a loose cable.
The problem was never the fault. The problem was that nobody on your side could see it.
You can fix that with a visit, with a live video call, or by letting the customer film it in their own time, and only the last one scales. Venta Capture, VentaVid's guided capture platform, is built for the third: you send the customer a secure, personal capture link, they film the fault step by step on their own phone with no app and no call, and the footage lands in your queue tied to the ticket. Don't schedule a video call just to see something.
Most support leads have already tried "send us a photo" and quietly given up on it. That's the right instinct about the wrong method: an unguided request fails, a guided one doesn't, and the difference is what you ask for and in what order. If your queue is full of tickets that bounce back and forth before an engineer goes out anyway, see how support teams use guided capture and judge it against your own worst ticket type.
In this post:
Why "describe the fault" and "send us a photo" fail
A customer describing a mechanical fault is translating. They hear a sound, see a light, feel a vibration, and turn it into words that mean something to them and not much to a technician. "Grinding" covers a bearing, a belt, and a bit of gravel in the drum.
The customer isn't a bad witness. They're a witness with no idea which detail matters. They will tell you the colour of the unit and forget to mention it only happens when the dishwasher runs at the same time.
Photos have the same problem in a different shape. A still image cannot show a fault that moves, flickers, or makes noise, and it usually arrives without the one thing your second-line team needs first: the model and serial plate.
So the agent replies asking for the label. The customer replies two days later, and the ticket is now a week old with nothing diagnosed.
The cost of that shows up in the field. In its report on first-time fix, Aberdeen Group found the average first-time fix rate sat at 75%, and that the calls not fixed first time needed 1.6 additional dispatches on average.
A big share of those failed first visits trace back to the engineer arriving without knowing what they were walking into. Some never had a fault to find at all: a Cranfield University researcher told diginomica that in aerospace service, roughly 20% of service calls were "no fault found", and nobody in consumer or industrial equipment thinks their number is much lower.
Written descriptions fail because the customer can't see what matters. Photos fail because they can't move. Both fail because nobody told the customer what to capture.
Three ways to see a customer's problem
Once you accept that someone on your side has to see the fault, the question is who, where, and when.
The call-out solves "someone needs to see it". The live call solves "our expert doesn't need to travel". The asynchronous request solves the part the other two leave open: our expert doesn't need to be there at the same time either.
Live video sounds like the modern answer, and customers keep declining it. Call Centre Helper's 2024 survey found video the least popular support channel, behind letters, with video chat stuck at around 0.5% of interactions.
The camera isn't the friction. The appointment is. A customer with a broken heat pump will happily film it at 9 p.m.; they will not book a slot at 2 p.m. on Tuesday to hold their phone up while an agent watches.
That's why the asynchronous route is the default and the other two are escalations. At 1,000 tickets a month you don't staff 1,000 video appointments. You send 1,000 links, review the ones that come back, and dispatch to the ones that need hands.
What a good video troubleshooting flow asks for, step by step
"Please send us a video" is the physical-product equivalent of "please describe the problem". It hands the decision about what matters back to the person least able to make it. A guided capture flow makes that decision for them, one step at a time, with an example image and a plain instruction on each screen.
This is the shot list that holds up across physical product lines. Adjust the wording per product; keep the order.
- The fault in action. A short video, 20 to 40 seconds, of the thing doing the thing. The instruction overlay while they film says exactly what to do: "Start the machine, hold the phone still, and keep filming until it stops." If the fault is intermittent, the flow says so and asks them to film when it next happens. The link doesn't expire at the end of the call, because there is no call.
- The label or serial. A scan step, not a photo step. The customer points the camera at the rating plate or QR code and the serial number is read into the case as text, with a typed fallback and an example photo showing where the sticker usually hides. Your second-line team now knows the model, the firmware generation and the warranty position before anyone reads a word.
- The surroundings. One wide shot. Where the unit sits, what it's connected to, what's next to it. This is the step that catches the extension lead, the blocked vent, the outdoor unit buried in leaves, and the install that was never done to spec.
- The sound. Ask the customer to hold the phone close to the unit for ten seconds with nobody talking. A compressor, a bearing, a relay clicking on and off: the audio is diagnostic, and no photo request in the world captures it. This is the step nobody in the how-to articles mentions. I'd put it above the wide shot if a flow only had room for three.
- One question that steers the next step. "Is the light flashing or solid?" A yes/no or single-choice answer that decides whether the flow asks for another shot or ends. The customer's spoken explanation is transcribed and searchable in the case file, so "it started after the power cut" doesn't get lost in a voice note.
The customer sees a page in your branding with a progress bar, a count of required items left, and a card that reads "Done in a few minutes. No app. No account. Just film."
Opened on a laptop, it shows a QR code to continue on the phone. When they submit, they get a reference number and, if you switch it on, their own copy of the report.
A standard support flow comes ready-made and your team adjusts the steps, slots and questions. Branching that follows your own triage tree across several paths is set up with VentaVid around your process, so the flow your customers see is your process, not a generic one.
Picture a "won't start" ticket on a commercial dishwasher. The description says "dead"; the wide shot shows the water inlet valve closed by whoever mopped the floor the night before.
That ticket closes with a two-line reply and no van, and the description alone would never have got there.
What it does to truck rolls and handle time
Walk one month. These are example numbers, chosen to be easy to redo with your own.
That's the visible line. The second line is the visits you still make, better prepared. TSIA puts the industry median at 87% of on-site incidents resolved in one visit; every engineer who arrives having already seen the fault, the serial and the surroundings is a first-time fix you didn't have to gamble on.
Aberdeen's 1.6 extra dispatches per failed first visit is the number you're protecting.
Then there's handle time. Loom reported that customers who attached a video to a support request waited 30% less for a resolution and were more often solved on the first reply. That's software support, but the mechanism travels: the agent's first reply is a diagnosis instead of a question.
Support teams using Venta Capture report 23% of customer problems solved without dispatching a technician. Your product mix decides your number. What doesn't change is the shape of the sum: fewer vans out, shorter tickets, and engineers who know before they go.
Plug your own call-out count and no-fault-found rate into that table. If the saving is bigger than one engineer's month, it's worth a look at how support teams run it before your next budget round.
How the video lands in the ticket
A video in an agent's WhatsApp is communication. A video in the case is evidence your system can act on. The second is the whole point of doing this properly.
Every submission becomes a case with a reference number in your own format, plus a separate "your reference" field that carries the ticket number from your helpdesk. So the case reads SUP-2026-00412 on our side and INC0098771 on yours, and either number finds it.
Inside the case, your team gets:
- The footage and photos per step, each labelled with what was asked, so nobody scrolls a two-minute clip looking for the serial plate.
- The answers to each question, as data, not prose. "Light flashing: yes" is filterable. "It's kind of blinking I think" is not.
- The transcript of anything the customer said while filming, searchable across cases. Search "power cut" and you find the other eleven tickets from the same street.
- Timestamps and an activity log. The timestamp is recorded when the system received the submission, server side, next to a log of who opened the link, when it was submitted, who claimed it and every note since. That proves when you received it, not when the fault happened, and the case says so.
- Device context for each item, marked "Taken via Venta Capture" when it was recorded in the session on that phone.
If a step is unusable (the fault didn't reproduce, the plate was out of focus), a retake is one click. The customer gets a fresh request for just that step, is asked why they're recording again, and the retake is linked to the original case.
From there the case follows your triage rules. Routing sends product-line A to one team and product-line B to another, with an SLA in hours on each route. Statuses, assignment and escalation to a manager sit in the shared inbox.
"Copy view link" hands the case to an engineer who has no login; "copy for CRM" pastes it into the ticket. And workflows, webhooks and a REST API push the whole package into your ticketing or field service system the moment it arrives, so the engineer's job card carries the footage.
The output is a structured evidence package, not a video file. That's what lets a support lead report on it: how many tickets came with a submission, how many closed without a visit, which product line generates the most retakes.
Where a live video call or a visit still wins
Asynchronous is the default, not a religion. Three situations still call for the other two routes.
- The customer has to do something with you watching. Resetting a controller through a six-step menu, bleeding a radiator, re-seating a card. If a wrong move breaks something, a live video call with an agent talking them through it beats a recording. Send the guided request first anyway; the live call is shorter when the agent has already seen the unit.
- Safety. Gas smell, exposed wiring, water near electrics, anything on a roof. Nobody should be filming that. The flow can say so on its first screen and route the ticket straight to dispatch.
- The fix needs hands and parts. Once the video shows a failed component, the visit is the answer. The difference is that the engineer now goes once, with the right part, having seen the install. That's pre-visit assessment, and it's the same flow the field service side of the business uses.
Remote-first, not remote-only. The promise is see first, act second, and make the visits that remain better informed. A support operation that treats every ticket as a potential live session has replaced one scheduling problem with another. One that sends a link first, and escalates from what comes back, gets the 0.5% video-chat problem out of the way and keeps the engineers for the jobs that need them.
Frequently asked questions
How do I ask a customer to send a video of the problem?
Send a secure, personal capture link by SMS, WhatsApp, email or a QR code on the confirmation screen, tied to their ticket. The link opens a guided flow that tells them what to film and in what order, so you're not relying on the customer to guess what matters. The request lives in the ticket, not in an agent's personal messaging app.
What should a customer troubleshooting video show?
Four things: the fault in action, the model or serial plate, a wide shot of the surroundings and connections, and ten seconds of sound with nobody talking. Add one steering question, such as whether a light is flashing or solid. That set answers most second-line questions before anyone has to ask them.
Is a live video call better than an asynchronous video request?
For diagnosis, no. A live call needs an agent and a customer free at the same moment, and Call Centre Helper's survey shows customers rarely take that option. Asynchronous works for the diagnosis, and a live call is the escalation for guided fixes the customer performs with you watching.
Does the customer need to install an app?
No. The flow runs in the phone's browser with no app and no account, in the customer's own language. Opened on a computer, the page shows a QR code to continue on a phone, because the recording has to happen on the device that's in front of the fault.
How long should the video be?
Short. Each step in a guided flow asks for 20 to 40 seconds, and the whole submission takes a few minutes. A single long free-form video is worse than four short labelled ones, because your team has to scrub through it to find the plate or the sound.
What about privacy when filming inside someone's home or on a site?
The flow only asks for the steps you define, shows a consent line linking to your own privacy statement before recording starts, and stores the case under your own retention and auto-purge settings. Ask for the unit and its surroundings, not the room. If a customer declines to share location, the case records that as neutral.
Does this replace engineer visits?
No, and anyone who promises that is selling something else. It removes the visits that were only ever there to look, and it makes the remaining visits first-time fixes more often because the engineer has seen the fault, the serial and the install before leaving the depot. Remote-first, not remote-only.
See it on one product line
If your queue has one ticket type that always ends in a van, that's the one to try this on. Build a four-step flow for it, send the link on the next twenty tickets, and count how many close without dispatch.
What it takes to start.
- Free plan, no credit card. Build the flow, run a test capture on your own phone, send the first link the same day.
- Live in 10 minutes. Stuck? Book a free setup call and we build your first support flow together.
- Runs in the browser. Nothing for your customers to install, nothing for your agents to learn beyond the inbox.
A real person from the VentaVid team builds your first flow with you on the setup call.
See how it works for support teams, or start for free and send your first capture link today.