For utility meter queries, first contact resolution means completing the customer’s specific request during the initial interaction, with no outstanding work or further contact needed to finish it. A useful explanation can resolve a display question. It cannot, by itself, establish that a reading was accepted or a bill corrected.
An advisor can identify the right meter register, forward a reading and close the contact while the customer’s disputed bill remains unchanged. Whether that interaction qualifies as resolved depends on what the customer originally asked to accomplish.
A broad “resolved” code can hide that unfinished work and overstate service performance. Closure records need to show whether the original request was completed, not merely whether the advisor finished handling the contact.
Keep the original request attached to the outcome
Start with what the customer wanted to accomplish, before selecting a closure code. “Which number is my reading?” is different from “Please submit my reading.” Both differ from “Please correct the estimated bill using my reading.”
The examples below illustrate how to distinguish completion from progress, using the utility’s own meter guidance and transaction records to make each decision.
| Original request | What can count as resolved on first contact | What remains progress rather than resolution |
| Explain a meter display or register | The advisor answers the specific question and checks that the customer understands the relevant value | Sending general instructions while uncertainty remains |
| Submit a meter reading | Acceptance is confirmed against the correct account, meter and relevant register | A reading is sent, received for review or referred for investigation without confirmed acceptance |
| Correct an estimated bill | The required correction is completed and its result is confirmed in the authorized billing record | A reading is accepted but the billing correction remains queued |
| Resolve a suspected meter fault | The requested fault outcome is completed and supported by the appropriate record | A fault report is raised or an investigation visit is scheduled |
| Book a meter appointment | The requested booking is confirmed with the agreed details | A booking request is passed to another team without confirmation |
The appointment distinction matters. A confirmed visit can resolve a request to book a visit. It does not resolve a request to investigate and fix a suspected fault.
Likewise, a bill-correction request must not become a reading-submission success halfway through the conversation. Preserve the original outcome even when the advisor completes a useful step toward it. If explanation and submission are both necessary to fulfill one request, both must succeed before that issue counts as resolved.
Make the closure evidence match the task
Closure needs evidence of the requested outcome, not just a note that the advisor took action. Before recording resolution, the advisor should establish:
- Request: What did the customer ask to accomplish?
- Identity and context: Which account, meter and register does the request concern?
- Action: What explanation, submission or correction was made?
- Result: What record or confirmation shows that the requested outcome succeeded?
- Dependency: Does anything still need to happen to finish the request?
Check the utility’s existing authorized records for confirmation of completion rather than creating a status that merely repeats the advisor’s judgment.
Customer confirmation has a different role. It can support an explanation outcome: the customer can now identify the requested register and understands what the value represents. Agreement that the number looks right cannot establish that an account was updated or substitute for transaction evidence.
A concise record can preserve the distinction: “Customer requested reading submission. Relevant register identified using meter-specific guidance. Reading provided through authorized process. Acceptance not yet confirmed. Validation remains outstanding.” That is a useful service record, but it is not first contact resolution.
When seeing the meter changes the next action
A meter-reading submission shows why understanding and transaction evidence need separate checks. Suppose a customer wants to submit the correct reading but has confused the cumulative register with another display value. The advisor first establishes the intended outcome, meter type and relevant register using account information and meter-specific guidance.
If the customer’s description still leaves the value uncertain, permissioned live visual assistance could help the advisor identify the relevant register on a safely accessible display. Keep an accessible nonvisual route available and never ask the customer to open an enclosure or reach an unsafe location. If existing records or a clear verbal explanation settle the question, a live view adds no necessary step.
A retained image serves a separate purpose. Request one through the utility’s authorized submission route only if its acceptance process requires that evidence. Seeing the display may resolve uncertainty about the number; supplying an image may satisfy an evidence requirement. The advisor should record the agreed meter, register, reading and submission purpose so the next person handling the case can understand what was established.
Close the submission request as resolved only when the utility confirms acceptance during the interaction. Give the customer the available reference or confirmation. If acceptance remains pending, explain what still needs to happen and record that dependency.
Count issues consistently, including unfinished ones
Use an issue-level measure so the calculation follows customer outcomes rather than call volumes:
Meter-query FCR = (eligible meter-query issues resolved on first contact ÷ all eligible meter-query issues in the same defined cohort) × 100.
Define each cohort by initial-contact date, included query types and channel coverage. First contact resolution can span phone, chat and other included channels. Telephone-only first call resolution is a narrower measure and should be labeled accordingly.
Document the counting rules before comparing teams or periods:
- Multiple requests: Separate genuinely distinct issues and retain their link to the original interaction. Do not split the necessary steps of one task into smaller successes. Explaining a register so a customer can submit a reading is normally part of that submission issue.
- Transfers: A transfer within one continuous interaction can qualify if the requested outcome is completed there. Moving the customer to another advisor is not automatically failure.
- Callbacks: A callback required to finish the issue means it was not resolved on first contact, even if the utility initiates it.
- Escalations and pending work: A referral, correction queue or investigation still required to finish the request keeps it outside the numerator. The eligible issue remains in the denominator.
- Exclusions: Publish them and show their volumes. Do not remove difficult fault or billing issues simply because they rarely finish during an initial interaction.
Report query types alongside the overall rate. Display explanations and physical fault investigations have different completion paths. A changing mix can move the aggregate rate without any change in advisor performance.
Separate advisor quality from the customer outcome. A correct referral can be excellent service while the underlying issue remains unresolved. Supporting measures such as successful referrals or reading acceptance can recognize useful work without giving it FCR credit for a bill correction or fault that remains outstanding.
Later back-office completion should update the eventual outcome, but it must not retrospectively turn an unfinished first interaction into an FCR success.
Check whether reported resolution holds
Treat an initial resolution classification as provisional until its validation window has elapsed. Validate it using the first-contact record, relevant acceptance or correction records, customer confirmation where appropriate and same-issue return checks. Report provisional and validated cohort results separately so recent contacts are not compared with fully observed outcomes.
Declare the observation window in the measurement policy. It should fit the query’s processing cycle rather than an arbitrary universal interval. A straightforward display explanation may suit a short fixed window. A billing-related outcome may need observation through the relevant billing event so the operation can see whether the requested correction held.
Match continuations across included channels where records permit. A customer who calls after an unresolved chat has returned about the same issue even though the channel changed. Use the account, meter, issue description and relevant transaction to distinguish that continuation from an unrelated inquiry. Disclose material matching gaps rather than treating unmatched contacts as proof of success.
A subsequent contact about a different meter or a new bill is not automatically an FCR failure. Review whether the customer is returning because the original task remained unfinished or the original answer was incorrect. A repeat contact caused by an unaccepted reading can overturn the initial resolution classification.
Silence is not proof of resolution. A customer may wait, abandon the task or pursue another route. Positive completion evidence is still required. Conversely, a status-check contact should trigger review rather than automatically erase a verified completed transaction: establish whether required work was actually left outstanding.
Audit a sample of both reported successes and pending cases. Compare what the customer requested with what the record proves. That exposes premature closure without treating every later contact as a failure.
Use the gap to choose the fix
The useful finding is what prevented completion. Misidentified registers, rejected evidence and delayed bill corrections require different responses.
If advisors repeatedly identify the wrong register, improve meter-specific guidance and offer visual assistance where it resolves genuine uncertainty. If required images are rejected, clarify the evidence requirements and submission route. If readings are sent without confirmed acceptance, improve the acceptance check. If accepted readings leave disputed bills unchanged, clarify correction ownership and follow-through. Another explanation of the display will not resolve that dependency.
Correct inaccurate closure classifications before setting a new FCR target. Then compare baseline and follow-up cohorts using the same definitions, comparable query mixes and the same observation rules. Judge the change through verified outcomes and same-issue returns, rather than a rise in the closure rate alone.
An FCR review should reveal which requested action failed and who can change it. Advisors deserve credit for appropriate action, while unfinished customer work stays visible. Changing the closure code fixes neither the reading nor the bill.
