Reducing unnecessary utility engineer visits starts with better dispatch decisions, not fewer bookings at any cost. Remote visual triage is useful when a safe observation supplies missing information that changes the next action: resolve the issue remotely, send the right service team or escalate urgently.
An unfamiliar meter indicator is one example. Seeing the exact display may help an advisor determine the appropriate response before booking. The test is whether that observation supports confirmed remote resolution or better-informed attendance, rather than merely deferring work.
Find the uncertainty behind the visit
Start with a sample of completed visits for one recurring call reason. Read the initial contact record alongside the field findings. Ask what the advisor needed to know when the booking was made, rather than judging the decision solely by what the engineer eventually found.
A visit is preventable when information and permitted assistance obtainable before dispatch could have safely removed the need for attendance. A no-repair visit does not automatically qualify. Physical testing, an authorized inspection or a safety assessment may have been necessary even though nothing was replaced.
For each reviewed case, identify:
- The uncertainty that justified attendance
- The specific observation that might have resolved it
- The approved decision that observation would support
- Whether testing or inspection would still have been required
This creates a more useful pilot shortlist than a ranking of no-repair visits. An unclear display message may be suitable if approved guidance links it to a permitted response. A suspected internal fault requiring physical testing is not a remote-resolution opportunity simply because the equipment looks normal.
Put safety and service responsibility before the camera
Screen the initial report for urgent hazards using the utility’s approved procedure before gathering routine service details. Suspected gas leaks, exposed electrical hazards or dangerous flooding are examples of reports that need immediate assessment under that procedure, not a camera session. The utility’s local procedures determine the emergency response. Do not delay it while arranging a connection. If safety remains uncertain, use the approved escalation path rather than asking the customer to investigate. Gather the remaining symptom and service details only if the emergency or escalation route is not triggered.
Establish who owns the equipment and which organization is responsible for the reported issue. Check known incidents and existing records too. A network incident or an already documented service restriction may determine the next action without any visual interaction. Cases requiring mandatory attendance should proceed through the established dispatch process.
Only then identify what remains unknown. Before offering remote visual assistance, the advisor should be able to complete this sentence: “Seeing this detail would help me decide between these approved next actions.” If there is no clear answer, video is likely to add handling time without improving the decision.
Any requested observation must be possible from an already safe position. Customers should not remove covers, touch connections, approach hazards or perform improvised checks. Customer actions must stay within the utility’s specifically approved instructions and the advisor’s authority.
Follow the meter inquiry through to an outcome
Consider a customer who sees an unfamiliar meter indicator and believes the meter needs replacing. The decision-changing detail is the exact display information: does it support a permitted customer action, require attendance or need specialist interpretation?
Once the case passes the safety and service-scope checks, the advisor asks permission to view the display. If the customer cannot show it, use the available nonvisual or field-service route.
When the display is visible, the advisor checks the exact message, symbol or reading against the applicable equipment guidance. The interpretation must come from an approved decision path for that meter, not from a general impression that the display looks familiar.
The observation can lead to three different responses:
- A permitted customer action applies. The advisor explains the approved instruction and checks that the customer understands it. After the action, the advisor checks the resulting display and the customer’s reported service status against the case’s resolution criteria.
- The indicator supports attendance. The advisor routes the case to the appropriate team with the observed display information and the reason a visit is required.
- The information remains unclear. An unreadable display, conflicting symptoms or an interpretation outside the advisor’s authority triggers specialist review or attendance under the approved process.
A changed display alone is not proof of resolution. If the original concern included a service interruption, the advisor must also establish whether that concern has been resolved through the permitted checks. If the result cannot be confirmed remotely, the case needs a next action rather than a resolved status.
Make necessary attendance a stronger outcome
Some observations improve the visit rather than remove it. An accessible equipment label may identify which service team should attend. The apparent location of a water leak, viewed from an already safe position, may help establish responsibility under the utility’s rules without proving the leak’s source.
Preserve those details so the receiving team can prepare. A concise handoff should contain:
- The customer’s reported symptom and service impact
- Relevant equipment identifiers
- What the advisor directly observed
- Any approved checks or customer actions already completed and their results
- Access constraints or communication needs
- The reason attendance is required and the team receiving the referral
Separate reports, observations and interpretations. “Customer reports intermittent loss of service” is different from “Advisor observed the displayed message.” Neither should become “Meter fault confirmed” unless the approved diagnostic process supports that conclusion.
Use the utility’s approved case-note or referral route, and make sure the receiving team can access the details. Include images only where capture and sharing are supported and permitted. Do not make the process depend on automatic evidence transfer or dispatch-system integration.
Before ending the conversation, tell the customer what happens next, who owns that action and what to do if the situation changes. Necessary attendance should be a clear service outcome, not an unexplained failure of remote support.
Pilot one decision, with a route for every customer
Choose one call reason with a repeatable information gap and a field-specialist-approved decision path. Favor clarity of the decision over dispatch volume. Define which cases are eligible, which hazards exclude them, what each relevant observation permits and what evidence confirms resolution. Agree the follow-up window before launch.
Train advisors on the decision and its limits, not only on starting a session. They need to recognize when the image is insufficient, when a customer action is outside scope and when further observation would add no value. Give them access to specialist review for uncertain cases.
The operating setup also needs a workable connection method, customer permission and clear privacy rules. Ask customers to show only the relevant equipment or detail. Where material can be captured, define what may be retained, who may access it and how it is handled.
Video must remain optional. A customer who declines, has weak connectivity, cannot safely access the equipment or needs another communication route still needs support. Offer the utility’s appropriate nonvisual assistance, specialist referral or attendance. Do not require participation in a camera session before allowing legitimate access to field service.
During the pilot, have contact center and field specialists review uncertain decisions together. Look for repeated gaps in guidance, unclear ownership rules and observations that rarely change the response. Those findings tell you whether to improve the decision path or stop using visual triage for that call reason.
Measure resolution, including what happens after the call
Define the eligible population before launch using call reason, risk level and service scope. Include eligible customers who do not use video. Measuring only completed sessions hides connection failures, declined sessions and access barriers.
Choose a follow-up window suited to the issue and a consistent method for linking repeat contacts and later bookings to the same problem. Then track a small set of measures:
| Measure | Definition or review question |
| Dispatch rate | Eligible issues resulting in dispatch within the follow-up window divided by all eligible issues. Include bookings made after the initial contact. |
| Confirmed remote resolution | Eligible issues meeting the predefined, case-specific resolution criteria without attendance during the follow-up window, checked against subsequent same-issue demand within that window, divided by all eligible issues. |
| Same-issue repeat demand | Repeat contacts and later attendance for the original issue within the follow-up window. |
| Avoidable dispatch rate | Dispatched cases within the eligible cohort judged safely preventable using information obtainable before dispatch divided by all dispatched cases reviewed within that cohort. |
| Routing accuracy | Did cases requiring attendance reach the appropriate team with sufficient information? Check against field findings, including cases requiring reassignment. |
Compare similar call reasons and risk levels against a baseline or suitable comparison group. For avoidable-dispatch reviews, report the sampling method and review criteria, and involve field specialists. Review what could reasonably have been established before dispatch, not what became obvious after testing on site.
Watch subsequent emergency attendance, safety escalations, customer effort and triage time alongside the headline results. An appropriate early escalation is not a failure. A falling initial booking rate followed by more unresolved contacts or later attendance is not convincing evidence of visit reduction.
Keep better-prepared visits separate from avoided visits. Both may be valuable, but they answer different operational questions.
Start with the decision you can improve
Use the reviewed results to improve the dispatch rule. If the observation consistently supports the intended decision without increasing unresolved demand or delaying necessary attendance, expand the approach to another suitable call reason. If it rarely changes the response, remove the camera step. The useful outcome of the pilot is a better dispatch rule, not a higher volume of visual sessions.
