This post in 30 seconds.
- The move: send the customer a guided capture link from the ticket, review the footage when it lands, and only dispatch when the footage says so.
- What to ask for: four things, in order. The device and its identifiers, the display or indicator state, the connections, and the sound of a start attempt.
- The number: avoidable dispatch runs at 24% for the bottom fifth of service organisations and 3% for the best, according to Aquant's 2025 benchmark. Seeing the fault first is most of that gap.
- Who this is for: technical support managers and service desk leads at equipment manufacturers, installers, and vendors who ship hardware with their software.
"Screen blank, please advise." That is the whole ticket. No model number, no photo, no idea whether the unit has power. Your first-line agent now has two choices: ring the customer and ask them to describe a machine they don't understand, or book a remote session for Thursday and hope both sides turn up.
There is a third option, and most desks already use a rough version of it over WhatsApp. Ask the customer to film it. The difference between "send us a video" and remote technical support with video done properly is that your desk decides what gets filmed, in what order, and the recording lands in the ticket as a case your team can act on.
This post is about that third option for a technical support desk specifically: what the flow asks for, how the ticket runs, when you can close from the footage and when you still escalate to dispatch, and how it plugs into the ticketing system you already run.
If you manage a support desk that keeps sending engineers to faults a customer could have shown you in 90 seconds, this is the workflow we built Venta Capture, VentaVid's guided capture product, to run. Start for free and send a capture link to your own phone before you read on; it takes less time than the average hold queue.
In this post:
Why the phone description and the scheduled screen-share both fail
A phone description is a translation done by the wrong person. The customer sees a light, a code, a cable and a noise, and turns all four into words. Your agent turns the words back into a guess. "It's making a sort of clicking" can be a relay, a fan blade, a loose panel or the customer's dog.
First-line support then closes on that guess or escalates on it. Either way the guess travels: into the knowledge base article you send, into the parts the second-line engineer orders, into the van.
The scheduled screen-share was supposed to fix this, and for distance it does. Nobody drives. But look at what it keeps. Two calendars, one slot, one party waiting for the other, and a support engineer sitting in a queue of booked sessions while the SLA clock runs on the tickets behind them. A live session is a very good way to talk someone through a fix. It is an expensive way to find out what the fault is.
The cost of deciding blind shows up on the dispatch board, not on the support desk's dashboard. Aquant's 2025 Field Service Benchmark, built on more than 600,000 technician records, puts avoidable dispatch at 3% for top performers and 24% for the bottom 20%. One in seven truck rolls across the sample was unnecessary.
The engineers you would put on those sessions are not idle either. TSIA's field services benchmarking (August 2025) puts engineer utilisation at 83% on average and 90.6% for pacesetters, so a queue of booked video sessions comes straight out of billable time.
The desk pays too, in its own currency. MetricNet's shift-left benchmark for North American support (2020 figures) puts a fully loaded level 1 ticket at roughly $22 and a field support ticket at roughly $220, with escalation costs stacking on top of each other. Every fault your first line can see, and settle, is a ticket that never climbs that ladder.
For faults on machines with engineers already on site, the remote diagnostics for field service post covers the operator-side version of this. Here we stay at the support desk, where the person holding the phone is a customer.
What a technical-support capture flow asks for
Anyone can ask a customer for a video. What comes back is 40 seconds of the wrong side of the cabinet with the fault code just out of frame, because the customer doesn't know what a support engineer needs to see. Guided capture fixes that by putting your engineer's checklist into the flow itself, so the customer only has to follow it.
For a technical fault, that checklist is shorter than most desks expect. Four asks, in this order, settle the large majority of first-line questions.
- The device and its identifiers. A scan of the serial or model plate (the flow shows an example photo of where the sticker sits, with a torch and a typed fallback), then one wide shot of the installation. This ends the "which model is it?" exchange and shows the environment: dust, damp, a heater next to the vent.
- The display or indicator state. A close-up of the screen, the fault code or the LED pattern. A yes/no question first ("Is anything shown on the display?") steers the next step: a code gets a code close-up, no code gets a 10-second clip of the lights.
- The connections. One photo slot per thing that matters on that product: the power lead, the isolator or breaker, the data cable, the network port. Each slot carries its own example photo and one plain-language line, so "check the connections" becomes four specific pictures.
- The sound. A 15 to 20 second video of a start attempt, with the instruction overlay reading "press start and describe out loud what you hear". Sound is the one input a phone description mangles and a photo can't carry at all. The spoken part is transcribed into the case, so "it clicks three times then stops" is text your engineer can search.
A fifth, optional ask closes the loop: a free-text or spoken answer to "what happened just before it stopped?". Customers volunteer the power cut, the firmware update or the new extension lead here, and rarely on the phone.
Four guided asks in a fixed order turn "send us a video" into a minimum evidence set your desk can rely on. The capture flow enforces the order and marks each step required or optional, so a submission with the plate missing can't be sent.
Two practical notes. A standard support flow comes ready-made and your own team adjusts the steps, slots and wording in the builder; a flow that branches by product line or routes by fault code to different queues is set up around your process on a scoped call. And build one flow per product family, not one per fault: the point is that the customer never has to know what's wrong to film the right things.
The photo-only version of the same idea, for faults that don't move or make noise, is in the guided photo capture guide. The guided video capture page shows what the customer sees on screen.
How the ticket runs, from link to review
Take an installer's support desk on a Monday. A heat pump customer emails: "outdoor unit not running, E14 on the controller." The agent opens the ticket and, instead of phoning, does this.
- Send a secure, personal capture link from the ticket. By SMS, WhatsApp or email, or as a QR code on the controller's service screen or the sticker on the outdoor unit. The link carries the ticket number, so the case arrives already matched. See request video by link.
- The customer opens it in the browser. No app, no account, any phone, in their own language. Opened on a laptop, the page shows a QR code to continue on the phone, because the recording has to be made on the device in their hand.
- They follow the four asks. Plate scan, wide shot of the outdoor unit, the controller showing E14, the isolator, the fuse spur, then a 15-second clip of a restart with "describe what you hear". Recorded now, on this device, with timestamps and device context logged as they go. A retake is one tap, and it asks why.
- The submission becomes a case. It lands in the desk's shared inbox with your own reference format and the ticket number in the "your reference" field. An agent claims it, adds a note, moves the status. Workflows forward it by status to whoever needs it next. See video review and retake.
- The engineer reviews when ready. Between calls, or first thing tomorrow. Nobody booked a slot.
What lands is not a video in an inbox. It is a structured evidence package: the media next to the question each item answered, the spoken description as searchable text, the customer's details, and an activity log of when the link was sent, opened and submitted. That is digital evidence in the proper sense, and it outlives the ticket.
In our own test flows the customer side takes a few minutes and the review side takes an engineer about as long as a coffee, which is why the asynchronous capture model scales in a way a session-based desk does not. That argument, and the maths behind it, belongs to another post; here the point is narrower. The support engineer reviewing the E14 case has, in under five minutes, more than a 20-minute call would have given them.
If you want to see this on your own ticket types rather than a heat pump, book a demo and bring last month's no-fix visits.
Close remotely or escalate: the two-question rule
The footage is in. The engineer has the plate, the code, four connection photos and a clip. The decision that follows has a simple shape, and it is worth writing into your desk's process.
Ask two questions of the footage:
- Does it change what the customer does next? Then close remotely. Reply with the instruction, keep the ticket open until they confirm, done. The isolator was off. The data cable was seated in the wrong port. The setting was changed by the last person to touch it.
- Does it change what your team does next? Then escalate, with the case attached. Second-line review for the intermittent fault the clip caught mid-click. A parts order for the fan you can hear scraping. A dispatch with the right engineer, the right part and a photo of the site access, because the footage told you all three.
That is the whole escalation path, and the honest version of it keeps a third answer: neither. The footage didn't settle it, so request a retake with a sharper instruction ("film the display for a full 30 seconds after power-on"). A retake on Venta Capture is one click, asks the customer why they're recording again, and becomes a new case linked to the original.
The dispatch that still happens is the one that changes most, because the engineer leaves knowing what they're walking into. Aquant's benchmark found a failed first visit adds two more visits on average and 14 days to resolution, and that top performers hit an 86% first-time fix rate against 53% at the bottom. The pre-visit assessment post takes the informed-dispatch side apart in detail; the reduce truck rolls post covers the visits that shouldn't happen at all.
On the close-remotely side, the numbers Venta Capture reports on its customer support page are 23% of customer problems solved without dispatching a technician, and 4 out of 5 issues handled and closed the same day.
One discipline to keep. Capture doesn't diagnose; your engineer does. The flow gives second-line support better visual access, and the call on what the clicking is stays with the person qualified to make it.
Fitting it into your ticketing system
A support manager's real objection is rarely "will customers film it". It's "I am not running a second inbox". Fair. Here is how the case stays inside the ticket.
- Two reference numbers, both yours. The case gets a number in your own format (prefix, digits, year, so
TS-2026-00417), and a separate "your reference" field carries the ticket ID from your help desk. Search either. - View link, no login. Every case has a copy-view-link button. Paste it into the ticket and the second-line engineer, the parts desk or the field engineer opens the footage without an account. A "copy for CRM" button pastes the case summary into whatever holds the ticket.
- Notifications that go where the ticket lives. Per route, on new submission, claim, assignment, status change or note, immediately or batched, with the view link, the dashboard link or both.
- Statuses that mirror yours. New, In progress, Completed and Closed ship; add your own so the case and the ticket speak the same states. Routing rules per form can carry an SLA in hours.
- Webhooks and a REST API. Auto-forward a case by status to your ticketing or CRM, or pull it with scoped keys. Middleware-ready for the desks that run everything through an integration layer. See video workflow automation.
- Visibility, retention, audit. Visibility per form (everyone, or named people, for the enterprise accounts with NDAs), configurable retention and auto-purge, and an audit trail of who opened, claimed and changed what.
Treat the capture link as a ticket macro, not a new channel: the agent triggers it from the ticket, and the case comes back to the ticket. Agents who already send "can you email me a photo?" adopt it in an afternoon, because the only thing that changed is that the photo now arrives in the right order, with a serial number attached.
Now the illustrative maths, with MetricNet's ladder as the shape and your own figures as the inputs. Say your desk logs 800 hardware tickets a month, escalates 30% to level 2 or 3 and dispatches 12%. On MetricNet's North American benchmark that dispatch slice alone is roughly 96 field tickets at about $220, call it $21,000 a month, before the truck. If seeing the fault first moves even a quarter of those back to a level 1 or level 2 close, the dispatch line drops by around $5,000 a month and the customers involved are fixed the same day instead of next week. Swap in your own ticket mix; the ladder does the rest.
The Venta Capture product page shows the case view and inbox. For a desk that supports installed equipment in the field, the field service page has the flows teams usually start with, and you can start for free with a single product family this week.
Where video intake doesn't help
Say this part out loud on the desk, so nobody oversells it.
- Safety-critical steps. If a customer has to isolate a supply, vent a system or leave the area, you want a voice in their ear now. That is remote assistance territory, and the live call earns its slot.
- The fix happens during the conversation. Reseat the module while I watch, run the reset sequence, turn the valve a quarter turn. When the guidance is the repair, go live.
- Faults that need an instrument. A customer can film a multimeter, but most won't own one. If the diagnosis needs a reading, a recording moves you one step, not to the answer.
- Intermittent faults with long gaps. A 20-second clip may miss it. Ask for a second recording when it recurs, and accept that some of these still need a logger or an engineer.
Three honest limits on the record itself. The timestamp proves when your system received the recording, not when the fault occurred. A sealed submission is harder to manipulate, not impossible to stage. And remote-first is not remote-only: the aim is to see first and act second, so the visits that remain are the right ones.
Where a recorded capture sits against a live session, and against a physical visit, is a comparison of its own; for this post, the working rule is the same one your desk already uses for remote troubleshooting. If the answer changes what the customer does in the next five minutes, call them. If it changes what your team does next, ask them to show you.
The operating model behind this is asynchronous video support. For the field-service equivalent, where the person on site is your own technician, see remote support for field technicians.
Frequently asked questions
What is remote technical support with video?
It is technical support where the person at the fault records guided video and photos on their own phone, and the support desk reviews the recording to resolve or route the ticket. In the recorded model described here, nobody needs to be online at the same time; a live video call is the other variant, and it still has its place for safety-critical steps.
Do customers need to install an app to record the video?
No. On Venta Capture the customer opens a secure, personal link in the mobile browser on any phone, with no app and no account, and the flow runs in their own language. If they open it on a computer, the page shows a QR code to continue on the phone.
Can a recorded video replace a live remote support session?
For finding out what the fault is, usually yes, and it removes the appointment. For talking someone through a fix in the moment, or any step with a safety element, a live call is still the right tool. Most desks end up using the recording to decide which tickets need the call at all.
What should the customer film for a technical fault?
Four things, in order: the device and its serial or model plate, the display or indicator state, each relevant connection, and a short clip of a start attempt with sound. A guided flow asks for each as a separate step with an example photo, so the customer doesn't have to know what's wrong to film the right things.
How does the video get into our ticketing system?
The case carries your ticket number in a "your reference" field, has a view link that opens without a login, and can be pushed to your help desk or CRM by webhook or REST API when its status changes. Most desks paste the view link into the ticket on day one and wire the webhook once the flow has settled.
Is it secure and GDPR-compliant?
Recordings are encrypted in transit and at rest, retention and auto-purge are configurable per organisation, and every case keeps an audit log of who opened and changed what. The customer sees a consent line linking to your own privacy statement before they record.
Is this just self-service with extra steps?
No. A person on your desk reviews every case and decides; only the intake is unattended. That matters because Gartner's August 2024 survey of 5,728 customers found only 14% of service issues fully resolve in self-service; guided video keeps the human in the loop and moves the waiting out of it.
How fast can a support desk start?
Venta Capture has a free plan with no credit card, and a first standard flow can be live in about 10 minutes: build the four asks, send the link to your own phone, review the test case. If you get stuck, a free setup call builds the first flow with you.
Try it on one ticket type
If your first-line desk closes tickets on a guess and your dispatch board pays for it, run one ticket type through a guided flow this week. Pick the product family that generates the most "please advise" tickets, build the four asks, and send the link instead of making the next call.
What it takes to start.
- A free plan, no credit card. Build the flow, send a test link to yourself, review the case.
- Live in about 10 minutes for a standard support flow; branching and routing flows are set up around your process on a call.
- Stuck? Book a free setup call and we build your first flow together.
The VentaVid team builds Venta Capture and Venta Video for service, support and sales teams.
Start for free or book a demo and bring the ticket that says "screen blank".