Visual diagnosis can prevent some repeat utility fault contacts when a safely visible detail answers a question that changes the advisor’s next action. Its value continues after the interaction: the finding must reach the team responsible for progressing the fault so the customer does not have to explain the same uncertainty again.
Consider a customer calling about a loss of electricity supply. The advisor checks the account and outage information, asks about the meter display and records an uncertain description. The case moves on, but the uncertainty moves with it. On the next contact, someone asks the customer to describe the same display again.
That diagnostic loop is different from a call asking when power will return. Seeing a relevant detail may settle a triage question; it will not repair the network or remove the need for restoration updates. A call that ends in appropriate escalation can be successful triage even while the customer’s power remains off.
Find the repeated question before adding video
Two customers can call again about the same loss of supply for different reasons. One still has not received a meaningful fault assessment. The other knows the fault is being investigated and wants a restoration update. Both are same-issue repeat contacts, but they need different operational fixes.
The diagnostic loop starts when an unclear description leaves a decision unresolved. The advisor records something vague, the case reaches another team without a usable finding and discovery starts again. Human-assisted visual diagnosis could interrupt that loop if it answers the missing question.
Other repeat demand needs different treatment:
- Restoration enquiries: The fault is understood, but the customer needs current information about the work.
- Missed update contacts: An expected update did not arrive or did not explain what happens next.
- Changed-condition reports: The situation has changed, potentially requiring fresh safety screening or escalation.
- New faults: A separate problem needs its own assessment.
Review repeat-contact notes for the question that keeps returning. “Which message is displayed?” is a potential visual-assistance opportunity. “When will the crew arrive?” usually points to update quality or operational visibility instead.
Before offering video, the advisor should be able to complete this sentence: If I can establish this detail, the approved next action could change from one response to another. If neither the guidance nor the routing changes, there may be little reason to add a visual step.
Use a safe view to answer a specific triage question
Consider a hypothetical electricity customer whose goal is straightforward: restore power and understand what will happen next. The account record and available incident information do not explain the reported loss of supply. The customer says there is a message on an already accessible meter display, but their description leaves the advisor unsure what it says.
The interaction starts with the utility’s approved safety screening and outage checks. Reported danger indicators, such as sparking, damaged equipment, a downed line or a suspected gas escape, trigger the relevant emergency procedure without further customer-led inspection. An established outage follows the incident process. Neither response should depend on the customer providing video.
Only if those checks leave a specific question unanswered should the advisor consider a visual interaction. In this example, the customer can already see the display from their existing safe position. The advisor explains that a view may help identify the displayed message and asks whether the customer wants to proceed.
The advisor uses remote visual assistance for one purpose: to read the message the customer is struggling to describe. The question is narrow: what does the display say, and does approved guidance for that meter model assign it to a different triage route?
Suppose that guidance assigns the observed message to a meter-specialist assessment. Reading it accurately would let the advisor select that route rather than pass on a generic report of an uncertain display. The specialist could receive the actual observation and the checks already completed, reducing the need to ask the customer to describe it again.
That relationship must come from equipment-specific guidance. A visible message does not, by itself, establish why the property has lost supply or prove which component has failed. The advisor has established what the display showed at a particular time and used it to inform triage.
An externally visible equipment identifier offers a different, simpler use. If the unresolved question is which asset the report concerns, a readable identifier from the customer’s existing safe position may help match the report to the correct asset record. That can support the appropriate investigation request without another call to clarify the asset. It does not establish the asset’s condition or justify canceling an investigation.
The observation ends if obtaining a view would require the customer to approach damaged equipment, open an enclosure, touch wiring or perform an electrical test. It also ends if the view is unreadable or new hazard information emerges. Customers who decline video, cannot connect or cannot provide a useful view retain the nonvisual service route. An inconclusive camera view is a reason to proceed with the remaining uncertainty, not to keep asking the customer to try harder.
Make the finding usable after the call
The visual interaction has little lasting value if the case note says only “video troubleshooting completed.” That records an activity, not a finding. The receiving team still has to discover what the advisor saw and why the case was routed to them.
For the hypothetical meter case, a useful record would include:
- Relevant asset: The meter or equipment identified, including any identifier established safely.
- Direct observation: The exact message read from the display and whether any part was unclear.
- Observation time: When the message was seen, since conditions may change.
- Completed checks: Relevant safety screening, account checks and incident checks, with their outcomes.
- Interpretation: The approved guidance used to select the route, kept separate from the observed fact.
- Remaining uncertainty: What the interaction did not establish, including the cause of the loss of supply.
- Next action: The receiving team, requested assessment and agreed customer communication.
Ordinary case notes can carry this information. Recording the interaction, capturing an image or transferring evidence automatically is not a prerequisite. The operational requirement is that the receiving team can find and use the record. Any image retention should serve a specific need and follow the utility’s approved policy.
The advisor then explains the result in customer terms: the message has been identified, it supports a specialist assessment and the cause of the power loss remains unconfirmed. The customer receives the case reference, who owns the next action and when or how the next update should arrive. If no restoration estimate is available, the advisor should distinguish that from the update commitment rather than imply a repair time.
The utility’s existing case management, specialist routing and dispatch processes carry the work forward. Visual assistance supplies a relevant observation; it does not replace those processes.
If this customer contacts support again while waiting, the next advisor should start with the recorded finding and current case status. They should not automatically repeat the visual assessment. New symptoms may justify fresh triage, while an unchanged situation may require a meaningful update.
Start with a fault category the receiving team can use
Choose one meter family or tightly defined fault category rather than offering video across every loss-of-supply call. Use the recurring unanswered question identified in contact reviews to define the scope. Utility operations and safety specialists should establish the permitted observation, relevant guidance and stop conditions. The receiving team should confirm that the proposed finding will help them progress the case.
Advisor preparation should cover how to explain the purpose, ask permission, recognize an inconclusive view and record observation separately from interpretation. Keep the view limited to the relevant equipment detail rather than unrelated household information. Define any image-handling requirements before capture is offered.
Also check the handoff in practice. Can the specialist find the note? Does it contain enough information to act? Are advisors selecting the intended route? A useful visual finding that disappears into an inaccessible record will not solve repeated discovery.
The pilot should test the whole path from missing information to downstream action. Counting video sessions only shows that the channel was used.
Measure repeated diagnosis alongside restoration
Use an issue-based cohort rather than counting every repeat caller as a failure. Define an index case as the first eligible fault case in the pilot category and choose the follow-up window in advance. Seven calendar days, for example, could be a pilot window, but the period should fit the utility’s fault-handling cycle and remain consistent across comparisons.
Same-issue repeat-contact rate = eligible index fault cases with at least one subsequent customer-initiated same-issue contact within the selected window ÷ all eligible index fault cases with a complete observation window × 100.
A case with several subsequent contacts counts once in that rate. Track the number of repeat contacts separately to understand the workload.
Match contacts across available channels using consistent case, incident, customer and service-point information. Account matching alone may combine unrelated faults. Cases that have not completed the follow-up window should not enter the denominator yet.
Report repeat-contact reasons separately: repeated diagnostic discovery, ongoing-outage status enquiries, missed updates and changed conditions. Exclude genuinely new faults from the same-issue numerator. Report planned follow-ups separately, including planned outbound contacts, which are outside this customer-initiated measure.
Show the diagnostic recontact rate as a subset of the overall same-issue rate. This makes it possible to see whether repeated discovery fell even if customers still needed restoration updates.
Compare similar eligible cases. Meter type, fault category, outage conditions and service area can affect the work. Comparing customers who accepted video with everyone who declined it can also mislead because those groups may differ in ways that affect outcomes.
Read the contact measures alongside:
- Escalation appropriateness: Whether reviewed cases followed the approved route, including cases correctly escalated without video.
- Restoration status: Whether supply is confirmed restored through approved operational records or customer follow-up appropriate to the affected service point, remains unresolved or is unknown.
- Safety and access: Whether urgent responses were delayed or customers without video encountered barriers.
- Operational effort: Total handling time across the issue and dispatches later judged unnecessary, where these can be assessed reliably.
A longer first interaction may be worthwhile if it prevents repeated discovery later. Fewer contacts alone cannot show that service improved: customers may stop calling while their power remains off. Keep triage completion, accepted escalation and confirmed restoration as distinct states so the pilot shows where service improved and where work remains.
Keep the finding useful until service is restored
An unresolved fault should not become an unexplained fault again at the next handoff. When the receiving team can see what was observed, why it mattered and what remains unknown, it can continue the investigation instead of asking the customer to reconstruct the first conversation.
Once that finding has served its triage purpose, the customer’s need moves on. The utility must keep ownership and updates clear, respond to changed conditions and confirm restoration. Carrying the observation forward allows the service conversation to move forward too.
