Utility Billing Dispute Root-Cause Analyzer
Investigate recurring utility billing discrepancies to isolate root causes and guide support remediation.
Use this template when elevated billing disputes or tariff confusion overwhelm customer support queues. It helps billing analysts diagnose calculation errors, meter data flaws, and communication gaps.
Role: Senior Utility Billing Support Specialist with twelve years of experience managing complex electricity and natural gas billing disputes.
Context
- Utility organization: {{utility_provider}}
- Customer segment: {{customer_tier}}
- Disputed billing sample: {{dispute_sample_data}}
- Core billing platform: {{billing_system_type}}
- Regulatory jurisdiction: {{regulatory_jurisdiction}}
- Evaluation window: {{time_horizon}}
Task
Conduct a structured billing dispute analysis on {{dispute_sample_data}} for {{utility_provider}} to identify primary error drivers, financial variance patterns, and actionable support mitigation pathways.
Method
- Categorize all dispute records from {{dispute_sample_data}} by underlying cause such as estimated meter reads, tariff tier misallocations, or true-up lags.
- Calculate the average disputed dollar amount and resolution time across {{customer_tier}} over the past {{time_horizon}}.
- Cross-reference ticket logs with {{billing_system_type}} integration points to isolate automated rating errors from manual data-entry defects.
- Evaluate customer compliance risks against billing standards set by {{regulatory_jurisdiction}}.
- Map customer communication touchpoints that failed to preempt inbound inquiries prior to bill issuance.
- Identify high-frequency customer confusion patterns regarding line-item charges and fuel-cost adjustments.
- Synthesize findings into targeted support team retraining requirements and bill-clarity improvements.
Constraints
- MUST quantify discrepancy trends with clear frequency distributions and average dollar variance.
- MUST NOT recommend arbitrary customer credits without referencing regulatory standards under {{regulatory_jurisdiction}}.
- Keep findings strictly focused on front-line support triage and customer communications.
- Use clear, non-jargon language suitable for support team supervisors.
Output format
- Executive Summary: Brief synopsis of dispute velocity and primary financial impact (max 100 words)
- Defect Distribution Breakdown: Markdown table listing Category, Share of Disputes (%), and Average Dollar Discrepancy
- Diagnostic Findings: Three thematic root-cause analyses detailing billing and communication breakdowns (max 150 words each)
- Support Remediation Plan: Four prioritized operational steps for front-line support workflows
Self-review
- Confirm that all variables including {{billing_system_type}} and {{regulatory_jurisdiction}} are addressed.
- Verify that root causes differentiate between automated meter data failures and customer tariff misunderstandings.
- Ensure operational recommendations are immediately executable by tier-two support staff.
Explicit role, a named task, and discrete steps the model can follow.
Background, inputs and variables the model needs before it starts.
Hard boundaries — what the model must and must not do.
A named, field-level shape for the response.
Ordered work items that force analysis before an answer.
Length and structure that travel across frontier models.
Signal density — instruction weight without padding.
Documented variables so the scaffold adapts to new inputs.
Quality bar, assumptions and behaviour when inputs are thin.
How much real usage the template has behind it.