This post in 30 seconds.
- What it is: a technician records a defined set of shots, a short spoken explanation and a few routing answers on their own phone, and the update lands on the desk as a case with a reference, not as a phone call or a photo in a group chat.
- Why it matters: a failed first visit adds two more visits and 14 days to resolution, according to Aquant's 2025 benchmark. A lot of those failures start with a finding on site that never reached the right person in a usable shape.
- Who this is for: heads of field operations, service managers, dispatch and planning leads, and service desk managers at equipment makers, dealers, installers and maintenance providers.
A technician is in a plant room at 10:40. The job card says "annual service, air handling unit 3". The unit is fine. The isolation valve next to it is not: corroded through, weeping, and about a week away from a callout at 2 a.m.
He rings the desk. Voicemail. He sends two photos to the team group chat with "AHU3 valve, needs replacing, ok to quote?". The site manager is standing next to him asking whether it can be done today.
Forty minutes later the planner sees the photos, cannot tell which valve it is from the close-up, and rings him back. He is already on the motorway to job two.
If you run field operations, a service desk or a dispatch board, that morning is your communication system. This post is about the technician side of it: how a field technician sends a video update to head office through a guided flow, what that replaces, why it shortens approvals for extra work, and what stays on the record afterwards. The customer side (a customer filming a fault before you send anyone) is a different subject, covered in pre-visit assessment for field service.
Service leaders keep telling us the same thing about the desk: the phone never stops, and half the calls are a technician trying to describe something a camera would show in ten seconds. Venta Capture, a product of VentaVid, turns that description into a guided submission the desk can act on. Start a free account and build the first technician flow this afternoon.
The four moments a technician needs head office
Strip out the small talk and a technician contacts the desk for four reasons.
- The condition found is not what the ticket said. The customer reported a leak; the technician finds a failed pump and a flooded sump. The plan for the visit has just changed, and someone off site needs to know before the next decision is made.
- Unexpected extra work. Work outside the job's scope, parts not on the van, or a repair that needs a quote before anyone touches it. The technician cannot proceed until someone says yes.
- A second opinion. An unfamiliar controller, a fault that does not match the manual, a safety call. The technician wants a senior engineer's eyes on it, not a diagnosis by phone description.
- Completion. The job is done, and the desk needs to know what was done, what was left, and what the customer should be told before the invoice goes out.
Each of these is a request for a decision from someone who is not standing where the problem is. The desk cannot make a good decision on a verbal description, and the technician cannot wait on site for one.
That tension shows up in the numbers. In ServiceTrade's Technician Insights Report, which surveyed more than 800 technicians, the two top frustrations were miscommunication (45%) and inefficient scheduling (44%). The report calls both what they are: coordination problems between the field and the office.
Today the four moments are handled by whatever is fastest: a phone call, a photo in a chat, or a line on the job card written up at 5 p.m.
What a video update replaces
Nobody chose the call-plus-group-chat system. It grew. Here is what the desk gets from each channel, and where it breaks.
The phone call is the expensive one. Repair-CRM's guide for small field teams does the arithmetic: one technician calling the office four times a day for five-minute clarifications loses twenty minutes of work a day, and a five-person crew loses more than eight hours a week.
The group chat is the one that feels like it works. Photos arrive, someone replies, the job gets done. Then a customer disputes an invoice three weeks later and the office spends an hour scrolling. As MotionOps puts it, in a chat app photos are not linked to jobs; they live in someone's chat history or camera roll.
The free-text note is the one nobody reads until it matters. A note on a work order records that the technician wrote something; it does not show the desk what he saw. It also depends on the technician remembering, at 5 p.m., what he found at 10:40.
There is a fourth cost that sits underneath all three. Salesforce's State of Field Service research found that 61% of mobile workers lack access to the customer data they need. Half the calls to the desk are the technician asking for context that should have travelled with the job; the other half are the desk asking for context that should have travelled back. A guided update fixes the second half.
Photos are the subject of a separate post, guided photo capture: what it is and why uploads fail; the rest of this one is about video and the technician.
How a guided technician flow works
The difference between "send me a video" and a guided flow is who decides what is in it. In an open request, the technician decides. In a guided capture, the desk has already decided, once, for every technician and every job.
Getting the flow to the technician
There is no app to install and no account to create. The technician opens a secure, personal capture link in the phone's browser, or scans a QR code. Where that QR code lives is your choice: on the printed job sheet, in the dispatch SMS, on the asset label in the plant room, or on the work order screen in your field service app.
That detail matters more for the people you do not employ. A subcontractor on their first day for you can run the same update flow as a ten-year engineer, without a login to your field service system. The request video by link mechanism was built for customers who will never install anything; it works exactly the same for a contractor's phone.
A technician can also start a capture themselves, without waiting for the desk to send anything. For completion updates that is the normal pattern: the job ends, the technician opens the flow, records, submits, leaves.
The desk writes the steps
A capture flow is a sequence: show this, record this, answer this. The steps a technician sees are defined in the builder by the person who has to act on the result. This is the point of the guided video capture feature, and it is the part that a phone call can never have.
Built from the standard flow in the builder, the "unexpected extra work" update comes to six steps:
- Scan the job reference. A scan field reads the QR or barcode on the job sheet or asset label, with manual entry as a fallback, so the case is tied to the work order before anything is filmed.
- Wide shot of the location. One photo slot with an example picture: the whole unit and its surroundings, so the reviewer knows where this is and how to get to it.
- Close-up of the finding. A second photo slot, labelled, required: the failed component and any identifier on it.
- Twenty seconds of spoken explanation. A video step with an instruction overlay while filming ("show the fault and say what you think it needs"). The spoken part is transcribed and searchable in the case.
- Three routing answers. Can the customer be left safe today (yes/no)? Parts needed (a short list)? Does this need a quote before work (yes/no)? A yes on the last one steers the flow to a free-text field for the estimate.
- Submit. The technician gets a reference number on the thank-you page and moves on.
Under two minutes on site, and the desk gets it in a shape it can route. The value is that it is the same six steps every time, so a reviewer knows what to expect before opening the case.
One thing surprised me during the research for this post: search "field technician video" and the results are day-in-the-life videos and training clips. The idea of a technician sending a structured update to the office has almost nobody writing about it.
What lands on the desk
The submission arrives in a shared inbox as a case. It carries its own reference number in your format, a separate field for the work order number your own system already uses, the media, the answers to each question, the transcript, and the receipt time.
From there it behaves like a ticket, not a message:
- Status. New, in progress, completed, closed, or your own set. A routing rule per form decides who sees it first and can carry an SLA in hours.
- Ownership. A reviewer claims it or is assigned it. Anyone can escalate it to a manager with a reason, and the manager is asked to approve or reject.
- Notes. Internal notes stay with the case, with author and time.
- Sharing. A view link goes to a supervisor or a customer contact who has no login. "Copy for CRM" pastes the case into whatever holds the job.
This is asynchronous capture in the ordinary sense: the technician submits when the finding is in front of him, the desk reviews when the case reaches the front of the queue, and neither waits for the other to be free.
If you would rather see that flow against your own job types than read about it, book a demo and bring the update that causes the most calls.
Shorter approvals for extra work
Extra work is where the call-based system costs the most, because two people are waiting on it: the technician on site and the customer who wants an answer.
The loop today: technician finds the problem and rings the desk. Desk rings the customer and describes it second-hand. Customer asks a question the desk cannot answer, so the desk rings the technician back. Somewhere in there someone says "go ahead", and nobody writes down who, when, or what exactly was approved.
Simply Connected Systems, in a guide on approval delays in property maintenance, puts idle crew time waiting for office approvals at $75 to $150 per hour, and a single day of delay on a three-person crew at $600 to $1,800. Their own recommendation is the one that matters here: approvals should be asynchronous, so the technician moves on instead of waiting on site.
A guided update makes that possible because the desk no longer needs the technician on the line to understand the finding. The video, the close-up and the three routing answers arrive together. The reviewer can forward the view link to the customer, attach the estimate, and set the status. The technician gets the notification on the status change and either returns, or the desk books the follow-up with the parts already on the list.
The approval loop shrinks from four phone calls to one submission and one status change, and the finding is on video for everyone who has to sign it off.
Two honest limits. The decision still happens in your own systems: a green-status button in Venta Capture sets a workflow status, it does not raise a purchase order or approve a quote. And a video of a corroded valve is not a diagnosis; a qualified person still decides what the repair is. What changes is that the person deciding can see it.
Venta Capture's own support and field-service numbers put it at 4 out of 5 issues handled and closed the same day. On the field side, the same mechanism is what keeps a finding from turning into a second visit: Aquant's benchmark of 160 service organisations found that a failed first visit adds two more visits on average and stretches resolution by 14 days. The truck roll you avoid by approving extra work while the technician is still on site is the cheapest one you will ever save. There is more on that side of the maths in how to reduce truck rolls.
Want to try the extra-work update on one crew? Start for free, no credit card, and send the first link to your own phone.
A record that stays on the job
A phone call leaves nothing behind. A chat thread leaves too much, in the wrong place. A case leaves exactly what happened.
Every submission carries an activity log: the capture link created and by whom, each time it was opened (recorded on the server), the moment it was received, who claimed it, who it was assigned to, every note, and every status change. That is an audit trail in the plain sense: a record of what happened, when, and on whose account.
Three details of that record matter on a service desk.
- Linked cases. A retake, or a follow-up update on the same job, becomes a new case explicitly linked to the original. The extra-work submission from Tuesday and the completion submission from Thursday sit in one file, with the approval in between.
- The retake replaces the call-back. If the close-up does not show the identifier, the reviewer requests a retake in one click and the technician gets the request, not a phone call. The technician's reason for re-recording is stored with a timestamp. More on that in video review and retake.
- A copy for the customer. Per form, the submission can be sent to the customer as well, so a site manager who approved extra work holds the same record you do. When there is a dispute, both parties look at the same file.
Be precise about what the record proves. The receipt time is the time the system received the submission, not the time the valve failed. A sealed submission with a SHA-256 fingerprint proves the file has not changed since it arrived; it does not prove what happened before the camera came out. That is still far more than a note that says "customer approved by phone".
A job is complete when the record shows what was found, what was approved, what was done and who reviewed it, and a guided completion update is the fastest way to get all four from a technician who wants to go home. The completion side, and how it holds up with contractors, is covered in proof of work in field service.
Rolling it out without slowing the crew down
Do not launch all four update types to every technician on a Monday. Start smaller.
- Pick one update type. Unexpected extra work is the best first candidate, because it is the one where everyone is currently waiting on someone.
- Pick one crew and two weeks. Five technicians, one planner reviewing, and a clear statement that nothing else changes.
- Put the QR where the technician already looks. The job sheet, the dispatch text, or the asset label. If they have to search for the link, they will ring instead.
- Write the routing questions with the desk. The planner knows which three answers would have saved the last ten call-backs. Those are the questions.
- Measure three things. Calls to the desk per technician per day, time from finding to approval, and how often a case needs a retake.
The standard flow comes ready-made and your own team adjusts it in the builder: steps, photo slots, questions, the instruction the technician sees while filming. Flows with branching between paths, routing rules and connections into your work order system are set up around your process with VentaVid on a call. Ask for that when the first flow has proved itself, not before.
For the desk side of the same rollout (deciding from a submission instead of a description), read remote diagnostics for field service. And when the update volume justifies it, workflow automation forwards cases by status so the planner stops being the router. The full field-service picture is on the Venta Capture field service page.
When the technician needs help rather than sending an update, see remote support for field technicians. What head office does with the updates is in field service quality control.
Frequently asked questions
Is a field technician video update the same as a video call with the office?
No. A video call needs the technician and a reviewer free at the same moment, which is exactly the problem the phone call already has. A guided update is recorded on site when the finding is in front of the technician, and reviewed when the desk gets to it.
Our technicians already send photos on WhatsApp. What changes?
The photos stop being attachments and become a case tied to the job reference, with the steps the desk asked for, the answers, the transcript and a receipt time. Nobody scrolls a thread to find the "before" photo, and the approval sits on the same case as the finding.
Do technicians need to install an app or get a login?
No. The flow opens in the phone's browser from a link or a QR code. That is also why it works for subcontractors and new starters on day one.
Does this replace our work order or field service system?
No. Your work order system stays the record of the job. The case carries your work order number in its own field, can be pasted into your system with "copy for CRM", and can be forwarded by status through the API or a webhook.
Can subcontractors run the same update flow?
Yes, and that is often where the value shows first. A contractor follows the same steps as your own engineers, without an account, so completion evidence arrives in the same shape from everyone.
What if there is no signal on site?
The flow runs in the browser, so submitting needs a connection. In a basement plant room the practical answer is to record once back in coverage, the way the phone call would have had to wait too. We do not promise offline capture.
What does Venta Capture cost?
Prices are not published. There is a free plan with no credit card required, which is enough to build one technician flow, send it to your own phone, and run it with one crew.
Start with the extra-work update
If your desk's phone is the system, you already know which call to fix first: the one where a technician is describing a part he could show you, while a customer waits for a yes.
Write down the six things that update should contain. That list is your first flow. Put the QR on next week's job sheets for one crew and count the calls.
Venta Capture is free to start, with no credit card, and a first standard flow is live in about ten minutes. Stuck? Book a free setup call and we build it together.
The VentaVid team builds Venta Capture for service, claims and inspection teams.
Start for free and build the technician flow
Prefer to see it against your own update types first? Book a demo and bring the job that generates the most calls.