This post in 30 seconds.
- The model: the technician records the situation in a guided flow on their own phone; the senior engineer answers from a queue when free. No call to book, no expert to interrupt.
- The number: top-performing service organisations fix 86% of jobs first time, the bottom group 53%, according to Aquant's 2025 field service benchmark. The gap is mostly experience, and experience is the thing you cannot hire fast.
- The honest limit: a safety-critical sequence, a step that has to be talked through in order, or a customer who needs the senior's voice still gets a live session. Everything else can go in the queue.
- Who this is for: service managers and technical leads running a mixed-experience field team at an equipment maker, dealer, installer, utility or maintenance provider.
Picture the senior engineer on your team on a Tuesday. He is halfway into a compressor swap when his phone goes for the fourth time before lunch. A second-year technician two towns over is looking at a control board and does not know which of three wires the manual means. The senior wipes his hands, talks him through it for eleven minutes, hangs up, and spends the next ten working out where he was.
If you run a field team with two people who can fix the hard ones and six who are still learning, you know that phone. Remote support for field technicians is usually sold as a faster way to get the senior on that call: a video link, a headset, an annotation tool. Useful, and it still puts the same person on the line every time somebody is stuck.
This post is about the other model. The technician records what they are looking at in a guided flow, the senior reviews it when he is between jobs, and the answer comes back as a case the whole team can find next time. It also says plainly where a live session is still the right call.
Two people on the team can fix the hard ones and everyone else phones them: that is the shape of most field service departments, and it caps how many jobs a day the seniors can touch. We build Venta Capture, a product of VentaVid, so a technician can show the senior the fault in a structured way instead of describing it on a call. Start for free and run the first flow on your own phone before you read the rest.
In this post:
- Why "call the senior" stops scaling
- What remote support for field technicians looks like without a live call
- The six things a technician should capture before asking
- Every answered case becomes a solved case
- Where a live session or a second pair of hands still wins
- How to run this with a mixed-experience team
Why "call the senior" stops scaling
Technicians phone a colleague when they are stuck. That is not a habit you will train out of them, and you should not try. The Service Council's Voice of the Field Service Engineer survey (725 technicians, 23 industries) found that a significant majority prefer calling a colleague over any other option, and fewer than half prefer calling technical support. In the 2022 edition, asking or calling a colleague was the top method at 79%. By late 2024 Future of Field Service still had 58% phoning a colleague for support.
The colleague on the other end is the scarce part. Every field team has a handful of people who know the older units, the odd firmware, the site with the strange wiring. They are also the people you send to the jobs nobody else can do. So the phone rings while they are on a job of their own.
The expensive part of a phone call is not the eleven minutes, it is what the senior engineer was doing when it rang. Gloria Mark and colleagues at UC Irvine found that people who are interrupted compensate by working faster, at the cost of more stress, frustration, time pressure and effort. In her later field work, Mark puts the time to fully pick up an interrupted task at about 25 and a half minutes. That research is about office work, so treat it as an analogy, but anyone who has watched a technician restart a diagnostic sequence after a phone call will recognise it.
The cost shows up in the numbers the board reads. Aquant's 2025 Field Service Benchmark Report, built on 600,000 technician records, puts first-time fix at 86% for top performers and 53% for the bottom group, and avoidable dispatch at 3% versus 24%. A failed first visit adds two more visits and 14 days on average. Most of that gap is the distance between what the senior knows and what the technician on site knows, at the moment it matters.
Here is the shape of one senior's day under the two models. The numbers are illustrative, so put your own in.
Four minutes per case is not a guess pulled from the air: a 60 to 90 second clip with the nameplate and the fault in frame, a transcript to skim, and a two-line answer. The queue model wins on the second row, the part nobody logs.
What remote support for field technicians looks like without a live call
Keep the senior human and in the loop. Change only when the question reaches him and what it looks like when it does.
The flow is short:
- The technician opens a capture flow on their own phone. No app, no account, in the mobile browser. On Venta Capture, staff can start a capture themselves without anyone sending a link, so "ask for help" is a saved flow on the home screen.
- The flow walks them through what to record. Each step has an example photo and a plain-language instruction. The video step shows an overlay while filming ("show the display, then the terminal block, and say out loud what you have tried"). This is a guided workflow, so the senior's questions are asked before the senior is involved.
- The case lands in a queue. It arrives in a shared inbox with a reference number, the video and photos, the answers to each question, and a transcript of everything the technician said while filming.
- The senior claims it when he is free. He watches 60 seconds, skims the transcript, writes the answer as an internal note or in a short reply, and sets the status. A routing rule with an SLA in hours makes sure nothing sits there unnoticed.
- The technician carries on. They had another task on site, or the next job, in the meantime.
What reaches the senior is a structured case, not a shaky clip on a personal phone with "what's this??" underneath it. The difference matters at review time. A case has the model and serial in a photo slot, the error code in another, a yes/no on "has it been power cycled", and a spoken explanation already turned into text. He is not scrolling a chat thread to find the one frame where the wiring is visible.
I learned this the ordinary way. The question that comes in most often on the phone is a variant of "which wire", and on a call it takes four exchanges to establish what the technician is looking at before anyone can answer it. From a 40-second recording with the nameplate and the terminal block in frame, the same question is answered on the first look, because the senior can see what the technician cannot yet describe.
The same review model is what the customer-support use of Venta Capture is built on, where teams solve 23% of customer problems without dispatching a technician at all. Internally the person filming is your own technician, and the person reviewing is your senior, but the mechanism is identical: capture now, review when ready.
The six things a technician should capture before asking
The reason a phone call takes eleven minutes is that the first seven are the senior asking questions. Build those questions into the flow and the call disappears. For most equipment the list is short.
- The nameplate. Model, serial, and the firmware or revision sticker if there is one. A photo slot with an example picture of where the plate sits on that family of machine. This single step removes "which version is it" from every case.
- The fault as the machine shows it. Error code on the display, LED pattern, a reading on the technician's meter held next to the terminal it was taken from. Photo, not description.
- The component or connection in question. A short video, with a hand, a screwdriver or a probe in frame for scale and orientation. "Which of these three wires" is answered here.
- The machine running, with sound. Ten seconds. Bearings, relays, pumps and compressors say a lot to an experienced ear, and a phone microphone catches most of it.
- What has already been tried, and the result. A checklist of the standard first steps for that machine family (power cycle, reset, checked supply, swapped the known-good part), plus a free-text field. The senior is not going to suggest something the technician already did.
- The technician's own theory. One spoken sentence: "I think it is the contactor because the coil is cold." This is the training step. Twenty cases in, the theory is right more often than not, and the technician has learned what the senior looks at.
Optional seventh: the site constraint. Is the customer waiting, is the machine safe to leave open, is there a return visit already booked. That tells the senior how urgent the queue item is.
The guided flow is the senior's checklist, run by the junior, before the senior is involved. That is why this works for an apprentice technician and a third-year alike. The apprentice needs every step spelled out; the third-year skips the parts they already know and still delivers a complete case. If your team is organised by technician levels, the flow is the same, and the level decides who reviews.
The same discipline runs through guided photo capture generally and through remote diagnostics before dispatch: decide what has to be seen, put it in order, and let the person already on site provide the camera. Here the person on site happens to be your own technician.
Every answered case becomes a solved case
A phone call leaves nothing behind. The answer lives in the technician's memory for a while and in the senior's forever, and when the same fault turns up on the same machine family next month, somebody else phones the senior.
A reviewed case leaves everything behind. The nameplate, the fault, the recording, the transcript of what was tried, the senior's answer as an internal note with author and time, and the status that says it was solved. It is searchable in the inbox by reference, by the answers to the questions in the flow, and by the words in the transcript. Anyone on the team can be sent a view link without needing a login.
Nobody has to write a knowledge-base article, because the case is the article. That is the difference from the knowledge base most teams have tried to build and abandoned: the senior answered a real question about a real machine, in the words he uses on site, and the record wrote itself. The activity log shows who asked, who answered and when, which is an audit trail for the fix as well as a training record.
The retention data says this matters more than it used to. In the Service Council's survey, 60% of technicians said field service may or may not be their long-term career, and 91% agreed more knowledge is required now than when they started. Oracle's Christiane Soto, quoted by Field Service East, puts it bluntly: 40% of companies lose specialised knowledge faster than they gain it. A library of solved cases outlives the technician who asked and the senior who answered.
One caveat, stated plainly. This is a library, not a diagnosis engine. Venta Capture does not tell the technician what is wrong with the machine; it gets the senior's eyes on it without a call, and it keeps the senior's answer. Cases remember what people forget; the senior still has to know.
If you want to see what the queue looks like with two machine families of your own in it, book a demo and bring last month's most-asked question.
Where a live session or a second pair of hands still wins
Remote-first is not remote-only, and a queue is not for everything. Say this to the team up front, because a technician who is not sure whether he is allowed to call will either call for everything or call for nothing.
A live session, or a senior in the van, is still the right answer when:
- The next step is safety-critical. Isolation, live electrical work, pressurised systems, anything where the sequence matters and a wrong move is not recoverable. That is talked through, in order, in real time.
- The diagnosis needs the senior's own hands. Some faults are found by feel on the meter or the manifold, and no recording replaces that. Send the senior.
- The customer is standing there and needs a decision. A hospital plant room or a production line that is down is not a queue item. The senior takes the call or the site.
- The technician cannot safely leave the machine open for half an hour. If waiting is not an option, the case should not go in the queue.
- The question is really a request for a second pair of hands. Some jobs are two-person jobs. Remote support of any kind does not change that.
Most teams end up running both: the escalation path goes queue first, live second, van third. The queue takes the volume, which is what makes the live tool and the senior's van available for the cases that need them. It is the same logic that makes pre-visit assessment work before a job is even dispatched, and that cuts the truck rolls nobody should have made. Remote assistance in the live sense keeps its place; it just stops being the only door.
How to run this with a mixed-experience team
The rollout is smaller than it sounds. One flow, two machine families, one reviewer.
- Pick the two machine families that ring the senior's phone most. Ask him. He knows without looking at any data.
- Write the six-step flow for each family. Nameplate, fault display, component in question, running sound, what was tried, the technician's theory. Put an example photo on every step so the apprentice knows where the plate is on that model. A first standard flow like this is live in about 10 minutes on the free plan; a flow with branching between paths is set up around your process on a call.
- Name the reviewer and the SLA. Route cases for family A to one senior and family B to another, with an SLA in hours, and switch on notifications for new submissions. If the senior is out, escalate to manager with a reason is one click.
- Tell the team what can wait and what cannot. Use the table above. Print it if you have to.
- Close every case with the answer in a note. The note is the library entry. A case closed without the answer written down is a phone call with extra steps.
- Read the library once a month. The questions that keep coming back on the same family are your training plan, and sometimes your argument for a design change with the manufacturer. A repeat visit that traces back to the same unanswered question is the clearest signal you will get.
The same flow, run at the end of the job, doubles as proof of work: the senior's answer and the technician's completion evidence sit in linked cases. And once the queue is running, workflow rules can forward a solved case to the ticket or the work order so the answer lands where the next technician will look.
Start for free, build the flow for the family that generates the most calls, and send the first case from your own phone. If the senior answers it in under four minutes, you have your pilot.
The other direction, technician to office, is covered in field technician video updates. The same mechanism on the customer side is in remote technical support with video.
Frequently asked questions
What is remote support for field technicians?
It is any way of getting an experienced engineer's help to a technician on site without sending that engineer there. Most tools do it as a live video call; the model in this post does it as a guided recording the senior reviews when free, with a live session kept for the cases that need one.
Does the technician need an app or an account?
No. The capture flow opens in the phone's browser, in the technician's own language, and staff can start it themselves without a link being sent. A desktop visitor is shown a QR code to continue on the phone, because the recording happens on the device in their hand.
How fast does the senior engineer answer?
As fast as your routing rule says. Set an SLA in hours per machine family, send notifications on new submissions, and let the senior batch the queue between jobs. In practice a case with the nameplate, the fault and a transcript takes a few minutes to answer, which is why a queue of eight fits in a coffee break.
What if the technician cannot wait?
Then the case does not go in the queue. Safety-critical steps, a customer who needs a decision now, and a machine that cannot be left open go straight to a live call or a senior visit. Write that rule down before you start, so nobody has to guess.
How is this different from a WhatsApp group?
A group chat is unstructured, lives on personal phones, and cannot be searched by machine or fault six months later. A guided case asks the senior's questions in order, carries a transcript and a reference number, stays with the company, and can be routed, assigned and closed like any other job.
Does it replace our live remote assistance tool?
No. It takes the volume off it. The live tool and the senior's van stay for the safety-critical and time-critical cases, and stop being the only route for "which wire".
Can the same recording close the job?
Yes. Run the flow again at the end of the visit as completion evidence, and link it to the original help request. The senior's answer and the technician's before-and-after footage then sit together in one file.
Give the senior his afternoon back
Pick the two machine families that ring the senior's phone most, write the six steps, and route the queue to him with an SLA. Within a week you will know two things: how many of those calls could have waited twenty minutes, and how much faster they get answered when the nameplate is in frame.
What it takes to start.
- Free plan, no credit card. Build the help-request flow, run it on your own phone, and send the first case to your senior today.
- Live in 10 minutes for a first standard flow. Stuck? Book a free setup call and we build it together around your machine families.
- No app for the technician, no login for the reviewer's view link, and everything goes out in your own branding.
The VentaVid team builds Venta Capture and runs the free setup call on your own machine families.
See how field service teams use Venta Capture
Or start for free and send the first help request this afternoon. If you would rather see the queue against your own cases first, book a demo and bring the question your senior gets asked most.