This post in 30 seconds.
- The model: asynchronous video support means the person standing at the problem records guided video and photos when it suits them. Your team reviews when it is ready. Nobody books a slot.
- The number: a failed first visit adds two more visits and 14 days to resolution, according to Aquant's 2025 field service benchmark. Seeing the fault before anyone moves is how you stop that.
- The honest limit: live video still wins when someone has to be talked through a step right now. Asynchronous wins almost everywhere else.
- Who this is for: service managers, heads of field operations, dispatch leads and technical support managers at equipment makers, dealers, installers, utilities and maintenance providers.
Every live support appointment has the same shape. Two calendars, one slot, and one party waiting for the other. The customer takes the afternoon off for a two-hour window. Your engineer sits in a queue of booked video sessions, half of which start late because the customer is still finding the fuse box.
Asynchronous video support removes the slot. The customer, tenant, operator or technician records what you asked them to record, when they can. Your team opens it when they can. Nobody has to be online at the same time, and the recording becomes a case your team can act on, route and keep.
This post explains what that means in practice, how it differs from a live video call, where live still deserves the appointment, and why the asynchronous model scales in a way a staffed video desk never will.
Service leaders who dispatch technicians from a ticket that says "unit not working" already know the cost of deciding blind: the wasted trip, the wrong part on the van, the second visit. We build Venta Capture, VentaVid's guided capture product, so that the person already standing next to the fault can show it to you first. Start for free and send a capture link to your own phone before you read the rest.
In this post:
What asynchronous video support actually means
Strip the jargon and the definition is short. Asynchronous video support is support where the person with the problem records video and photos on their own phone, guided by the questions your team wrote, and your team reviews the recording later. The two halves of the conversation happen on different clocks.
That direction matters. The video travels from the customer or technician to the business, not the other way round. A support agent recording a screen walkthrough to send to a customer is asynchronous communication too, and useful, but it is a different job. This post is about seeing the problem, not explaining the fix.
The model runs on three clocks: the customer's, the reviewer's, and the record's, and none of them has to match. Here is how they come apart:
- The customer's clock. They open a link on whatever phone they have, no app, no account, and record when it suits them. Tuesday at 21:40 is fine.
- The reviewer's clock. Submissions land in a queue, not a calendar. An engineer works through them between jobs, or a support desk clears them first thing.
- The record's clock. The asynchronous capture is a dated case with answers, a transcript and an activity log. It outlives both the customer's evening and the reviewer's morning.
One thing it is not: self-service. Gartner's August 2024 survey of 5,728 customers found only 14% of service issues fully resolve in self-service, even though 73% of customers try it at some point. Customers told Gartner the tools were too rigid for the complexity of their problem.
Asynchronous video support is assisted service on a different timetable. A human still looks, still decides, still calls the customer back if the footage says so. Only the timing moved, which is why the 14% figure is a warning about deflection, not about visual support with a person on the other end.
How it works, step by step
The mechanics are unglamorous, which is the point. Here is the loop as it runs on Venta Capture; other tools in the category vary the details.
- Send a secure, personal capture link. By email, SMS or WhatsApp, or as a QR code on a service screen, an invoice, or a sticker on the machine. Staff on site can also start a capture themselves without sending anything. See request video by link.
- The person opens it in the browser. No app to install, no account to create, any phone. Opened on a laptop, the page shows a QR code to continue on the phone, because the recording has to happen on the device in the person's hand.
- Guided steps, in your order. A scan of the serial plate. A wide shot of the installation. A close-up of the fault. A 20-second clip of the start attempt, with sound. A spoken answer to "what happens when you press start?" A yes/no question that decides which step comes next.
- Recorded now, on this device. Timestamps and device context are logged automatically. A retake is one tap, and it asks why.
- The submission becomes a case. It lands in a shared inbox with your own reference number, gets claimed or assigned, collects internal notes, and moves through statuses. Workflows forward it by status to the people or systems that need it. See video review and retake.
The load-bearing word in that list is "guided", in the sense of guided capture: the organisation decides what gets filmed, in what order, with what instructions. Anyone can ask a customer to send a video. What comes back is 40 seconds of the wrong side of the machine with the fault code just out of frame, because a customer doesn't know what a service engineer needs to see.
Guided capture puts the expert's knowledge into the flow, so the person on site only has to follow it. Your best engineer writes the five steps once. Every submission after that is shot to the same standard by someone who has never been trained.
Take an equipment dealer's support desk. "Compressor won't start" arrives by phone at 16:50 on a Friday. Instead of booking a call for Monday, the desk sends the link. By 17:30 the capture flow has come back with the model plate, the control panel showing E42, the isolator in the off position, and a clip in which you can hear nothing happening at all. Monday's first job is a five-minute review and one message: "flip the isolator, then try again".
The same loop, built for photos instead of video, is covered in the guided photo capture guide.
How it differs from a live video call
A live video call is the customer holding up their phone while your engineer watches and talks. Remote assistance tools of that kind take the engineer's travel off the road, and that is a real saving.
But look at what survives. The appointment does. Two people still need to be free at the same moment, and one of them still waits for the other. J.D. Power's U.S. Telecom In-Home Service Technician Study found appointment satisfaction 49 points higher with a one-hour window than a two-hour one, and the gap grew to 104 points at four hours. Customers are not measuring your drive time. They are measuring how much of their day you took.
Live video moves the engineer's travel; asynchronous video removes the appointment itself. That is the whole difference, and it decides which one you reach for.
The live call still deserves the slot in three situations:
- Safety-critical steps. If someone has to be talked through isolating a supply, venting a system or leaving the area, you want a voice in their ear now, not a review queue.
- Hands-on guidance in the moment. When the fix happens during the conversation (reseat the cable, run the reset sequence, turn the valve a quarter turn while you watch), the call is the repair.
- One-shot access. The contractor is on site now and leaves in an hour. If you need to steer what they look at while they are there, go live.
A rule of thumb that holds up: if the answer changes what the person does in the next five minutes, go live. If the answer changes what your team does next, go asynchronous. Most remote troubleshooting sits in the second group, as the remote diagnostics for field service post works through in detail.
If you would rather see the two side by side on your own ticket types, book a demo and bring last month's no-fix visits.
The record it leaves behind
Ask what a live call leaves you with once it ends. An engineer's memory, a line in the ticket, and if you are lucky a recording that sits in a folder nobody indexes. Six months later, when the same machine fails again or the customer disputes what was agreed, that is what you have.
An asynchronous submission is different in kind, not just in timing. What comes back is a structured evidence package rather than a video sitting in an inbox. On Venta Capture that means:
- The media and the answers together. Every photo and clip sits next to the question it answered, so "was the isolator on?" is a field, not a thing you scrub for.
- The spoken description, transcribed. What the customer said while filming is text in the case, and searchable across cases.
- Receipt time, device context and an activity log. When the link was created and by whom, each time it was opened (recorded server side), when the submission arrived, who claimed it, who assigned it, every note. That is an audit trail in the proper sense of the term.
- A seal. Each submission carries a digital fingerprint and a downloadable manifest, so a third party can check the file has not changed since it arrived.
One discipline worth stating plainly: the timestamp proves when your system received the recording, not when the fault occurred. Say that in your own process documents too. It keeps the digital evidence honest.
Why does the record matter to a service manager rather than a lawyer? Because of the second visit. Aquant's 2025 Field Service Benchmark Report, built on 600,000 technician records, found a failed first visit adds two more visits on average and stretches resolution by 14 days. The second engineer opening the case and seeing exactly what the first one saw, plus what the customer showed before anyone went, is how the second visit stops being a repeat of the first.
The same record does quieter work downstream: the warranty claim already has the fault on file, the contractor's completion capture sits next to the original request, and a dispute is settled by opening the case rather than by who remembers what. The proof of work in field service post covers the completion side; the product overview shows what a case looks like from the inside.
Why it scales where live video can't
This is the argument that gets missed, so it gets numbers. Treat every figure below as an input to swap for your own.
A live video desk is capped by staffed session hours. Four support engineers, seven productive hours each, sessions of about 20 minutes: that is around 84 sessions a day, and every one of them also needs a matching slot in a customer's day. No-shows, late starts and "can you call back after school pick-up" all come out of the 84. To handle 300 video requests in a day, you either hire or you queue people into next week.
An asynchronous desk has no intake ceiling, because intake is not staffed. Send 300 links on Monday morning and they come back Monday lunchtime, Monday evening, Tuesday at 07:15. The only staffed step is review, and a guided case reviews fast because the steps were fixed in advance: the plate, the panel, the fault in action, the answers. Call it five minutes.
Capture capacity is decoupled from staff availability: at 1,000 captures you do not staff 1,000 video appointments. In our own test flows, the recording side takes a customer a few minutes and the review side takes an engineer about as long as a coffee. Those are the only two clocks that spend anyone's time.
The effect shows up in the dispatch numbers first. On the customer support page, Venta Capture reports 23% of customer problems solved without dispatching a technician, and 4 out of 5 issues handled and closed the same day. Aquant's benchmark puts the ceiling higher still: one-third of service queries, it found, are solvable without a professional on site, and 14% of truck rolls turn out to be unnecessary.
The dispatch that still happens gets better too. The engineer leaves with the right part and the right skills, because the case told them what they were walking into. That is what a rising first-time fix rate looks like from the van. The reduce truck rolls and pre-visit assessment posts take each of those apart; the field service page shows the flows teams start with.
Gartner's August 2025 survey of 265 service executives expects self-service and live chat to overtake phone and email by 2027. Read that next to the 14% resolution figure and the gap is obvious: teams want channels that don't need a human at both ends at once, and customers want a human to look. Asynchronous video is one of the few channels that gives both.
Where asynchronous video support falls over
It would be dishonest to leave this section out, so here are the failure modes we see and what to do about them.
- The person won't film, or can't. No smartphone, no signal in the plant room, an emergency, or a customer who simply refuses. Keep the phone line and keep the visit. Remote-first is not remote-only.
- Bad instructions produce bad footage. If the flow asks for "a video of the problem", you will get one, and it will be useless. Write the steps with the engineer who reviews them, and put an example photo on every slot.
- Nobody owns the queue. "Review when ready" becomes "review never" without an owner and a target. Route submissions to a named person or team, set an SLA in hours, and batch the notifications so they don't drown the service desk.
- It doesn't diagnose. The footage gives your expert better eyes. The judgment stays with the expert, and some cases will still end in "send someone".
Asynchronous video support earns its place by making the remaining calls and visits better informed, not by promising there will be none. Teams that treat it as a remote triage step in front of everything else get the most from it. If you are weighing the wider category, remote inspection software explains where the boundaries between tools sit.
For the support desk version of this, read remote technical support with video; for how it compares to messaging apps, WhatsApp vs guided video for service diagnosis.
Frequently asked questions
What is asynchronous video support?
Support where the customer, operator or technician records guided video and photos on their own phone when it suits them, and the support team reviews the recording later. Neither side has to be online at the same time. The recording arrives as a structured case rather than a file in an inbox.
Is asynchronous video support the same as self-service?
No. In self-service the customer is expected to solve the problem alone, which Gartner found happens fully in only 14% of cases. In asynchronous video support a person on your team still reviews and decides; only the timing is decoupled.
When should a support team use a live video call instead?
When the answer changes what the person does in the next five minutes: safety-critical steps, hands-on guidance where the fix happens during the call, or a contractor who is on site now and leaving soon. For everything else, asynchronous is cheaper for you and easier for them.
Does the customer need to install an app?
Not on Venta Capture. The capture link opens in the phone's browser, with no app and no account, in the customer's own language. A desktop visitor gets a QR code to continue on their phone, because the recording happens on the device in their hand.
What does the support team receive?
A case with the video and photos, the answers to each guided question, a transcript of anything the person said while filming, the receipt time and device context, and an activity log of who opened, claimed and handled it. Cases carry your own reference number and can be shared by view link with someone who has no login.
Can field technicians use asynchronous video with a remote expert?
Yes, and it is one of the most common uses. A junior engineer on site follows the same guided steps, a senior engineer reviews between jobs, and the answer goes back without the two of them having to find a shared slot. Staff can also start a capture themselves without sending a link.
How do you start with asynchronous video support?
Pick one ticket type that regularly turns into a no-fix visit or a call you had to book. Write down the five things a good submission would show, build them as steps, and send the link to yourself first. On a free Venta Capture plan a first standard flow is live in about 10 minutes.
Try it on one ticket type
Pick the ticket type that most often turns into a no-fix visit or a call you had to book. Write the five steps a good submission needs, put an example photo on each, and send the link to your own phone. You will know within a week whether the footage that comes back changes the dispatch decision.
What it takes to start.
- Free plan, no credit card. Build the flow, test it on yourself, then send it to the next customer who says "it doesn't work".
- Live in 10 minutes for a first standard flow. Stuck? Book a free setup call and we build it together.
- Everything goes out in your own branding, in the customer's language, with no app to install.
The VentaVid team builds Venta Capture and runs the free setup call on your own ticket types.
See how field service teams use Venta Capture
Or start for free and build the first flow this afternoon. If you would rather see it against your own tickets first, book a demo and bring your worst case type.