Reducing No Fault Found truck rolls: A visual triage protocol for verifying faults before dispatch

A No Fault Found (NFF) truck roll happens when a technician arrives on site and finds nothing to fix, or a problem simple enough that a phone call could have solved it. Visual triage closes that gap by having someone look at the fault before a vehicle ever leaves, confirming what’s actually wrong and what the visit will need before it’s scheduled.

This isn’t about replacing technical judgment with a video call. It’s about offering a way to see the problem instead of just hearing a description of it, using the same visual remote assistance software many teams already rely on when a technician is on-site.

Key takeaways:

• An NFF truck roll isn’t a technician failure, but a triage failure. The decision to dispatch was made without confirming what was actually wrong.

• Visual triage moves fault verification earlier in the workflow, before scheduling, not during the visit itself.

• The most common causes of NFF dispatches—vague reports, configuration errors, wrong parts, and intermittent faults—are all things a short video check can catch.

• Visual triage complements in-visit expert guidance rather than replacing it; they solve different problems in the same dispatch workflow.

• You can add a visual triage checkpoint to an existing dispatch process without a new intake system or extra headcount.

What is an NFF truck roll?   

A No Fault Found (NFF) truck roll is a dispatch where the technician arrives and finds no verifiable problem, or one that never needed an on-site visit. NFF dispatches go by different names depending on the industry: no trouble found in telecom, non-actionable dispatches in utilities, callback with nothing found in HVAC. The label changes but the pattern doesn’t. A truck was dispatched even if it wasn’t required.

NFF often hides inside metrics you may already track: second-visit rate, cost per incident, mean time to resolve. If you’re already tracking those, stabilizing first-time fix rates walks through how they’re defined and calculated.

Why NFF dispatches keep happening   

Most NFF dispatches trace back to one of four patterns, and none of them are about technician skill: vague reporting, mismatched error complexities, inaccurate resource allocation, and intermittent faults.

Vague or incomplete fault reports   

When a customer calls about “weird” noises from the machine, they’re describing a symptom, not the fault. A dispatcher, or a support agent taking that report, has no way to verify it beyond a phone description, so the safest option is sending someone to look. Multiply that by a few hundred calls a week, and vague reporting alone accounts for a meaningful share of avoidable dispatches.

Configuration and setup errors mistaken for hardware failure   

A misconfigured router, a thermostat set to the wrong mode, or a sensor that’s simply misaligned aren’t hardware failures, but they present exactly like one over the phone. The equipment isn’t broken. It’s set up wrong, and that’s usually a five-minute fix once someone can actually see it.

Wrong resources for the job   

A technician shows up with a general toolkit for what turns out to be a specialized repair, or without the one replacement part the job actually needs. The visit happens, yet it ends in a second dispatch. This is arguably worse than an NFF call because it costs the same as a failed visit but looks like a successful one in your scheduling data.

Intermittent faults that don’t reproduce on demand   

Equipment that “acts up” occasionally often looks completely fine by the time someone arrives to check it. Without a way to catch the fault in the moment it’s happening, or close to it, these cases get dispatched, resolved as NFF, and reopened again a few weeks later.

How visual-first triage works as a pre-dispatch gate   

The mechanism is straightforward: Verify before you schedule, not after you arrive.

Collect the incoming report 

Nothing changes about how the issue first comes in, by phone, ticket, or app. Collect all of the details regarding the issue to preserve the initial context.

Request a visual verification session   

Instead of assigning it to a work order immediately, the dispatcher or support agent sends a link inviting whoever’s on-site to open their camera. No app or account is required on their end so they can join directly from the browser.

Live inspection and routing decision   

A remote expert reviews the live feed, checks it against the reported symptom, and annotates directly on what they’re seeing. They circle the suspect component, using OCR to read a model number or error code without asking anyone to type it out. From there, one of three things happens: The issue gets resolved on the spot and the dispatch is skipped entirely; the fault is confirmed and the work order goes out with the correct part and skill already specified; or the visit proceeds exactly as it would have, minus the guesswork.

Where visual triage fits with your first-time fix strategy

Visual triage and in-visit expert guidance solve two different problems, and most service organizations eventually need both. One decides whether a technician should go at all. The other makes sure that once they’re there, they have the expertise to finish the job on that first visit.

If you’ve already looked at closing the technician skills gap with visual remote support, it covers the post-dispatch situation. Visual triage covers the pre-dispatch area. Neither replaces the other, and organizations with a high NFF rate but a strong on-site fix rate (or the reverse) are often solving only half the problem.

What to measure  

TSIA’s State of Field Services 2022 report notes that when field teams have pre-call intelligence about what’s wrong and what a job needs, technicians arrive prepared instead of guessing. Visual triage is an effective way to generate that intelligence without waiting for telemetry data to exist for every asset you service.

You don’t need a new KPI to prove this out. Track the same you may already use, but segment them by whether the dispatch went through a triage check first. If triaged cases resolve remotely more often and generate fewer second visits than non-triaged ones, that’s your evidence, measured against your own baseline rather than an industry benchmark.

Building a visual triage checkpoint into your dispatch workflow   

You don’t need to start from scratch. All you have to do is add one mandatory step— i.e., a visual verification request—for dispatch categories where NFF shows up most often. Start with whichever failure type generates the most repeat calls or “nothing found” closures in your existing ticketing data; that’s usually where the fastest proof point is. Run it for two to four weeks, track the remote resolution rate and second-visit rate, and expand to additional categories once the pattern holds.

Wrapping up   

An NFF truck roll isn’t a sign that your technicians need more training. It’s a sign that the decision to dispatch was made too early, before anyone confirmed what was actually wrong. Visual triage doesn’t add process for its own sake. It moves verification to where it actually helps, before the vehicle leaves instead of after.

FAQ   

What’s the difference between visual triage and on-site visual assistance? 

Visual triage happens before a technician is dispatched, to confirm whether a visit is even necessary. On-site visual assistance happens when a technician has already been dispatched who needs expert guidance on site to finish the job. Most service teams need both at different points in the same workflow.

Do you need smartglasses or special hardware to run a pre-dispatch visual check? 

No. A pre-dispatch triage session typically starts with whoever reported the issue, where they click a browser link to share the issue using their existing phone camera. No app or hardware purchase is required to start. Smartglasses become relevant later, for hands-free in-visit work, not for the triage step itself.

Does visual triage work if the person on site isn’t a trained technician? 

Yes, and that’s actually the more common case for pre-dispatch triage. The remote expert makes the technical call. The person holding the camera just needs to point it at the equipment and follow simple directions, which is why app-free, link-based access matters more here than in a technician-to-technician session.

How does visual triage affect the first-time fix rate if a technician still has to visit? 

It improves FTFR indirectly by making sure the visits that do happen are the right ones, with the right part and skill already confirmed. A triage session correctly flags whether an issue needs a dispatch and specifies what the job requires, reducing the odds of failure of that dispatch.