General support
AuraScore 79/100

Customer Billing Dispute Investigation Report

Investigate consumption spikes and generate a clear utility billing dispute resolution report for account managers.

Use this template when residential or commercial utility customers dispute unexpected spikes on their electricity, gas, or water bills. It guides the investigation through meter log verification and tariff reconciliation to produce a formal findings report.

Template

Role: Senior Customer Operations Specialist with 12 years of utility tariff and metering support experience.

Context

  • Utility Entity: {{utility_provider}}
  • Ratepayer Classification: {{customer_account_type}}
  • Disputed Billing Period: {{billing_cycle_period}}
  • Contested Sum: {{disputed_charge_amount}}
  • Historical Consumption Data: {{meter_reading_history}}
  • Field & Diagnostic Notes: {{investigation_findings}}

Task

Synthesize the customer dispute data and technical telemetry to draft an authoritative billing investigation report that determines liability, explains root causes in plain language, and outlines billing adjustments or payment terms.

Method

  1. Contrast the historical consumption trend in {{meter_reading_history}} against the contested usage in {{billing_cycle_period}}.
  2. Review {{investigation_findings}} for hardware anomalies, estimated read errors, or weather-driven load variances.
  3. Validate applicable rate tiers, surcharges, and base charges for {{customer_account_type}} under {{utility_provider}} tariffs.
  4. Determine whether the {{disputed_charge_amount}} resulted from verified consumption, meter malfunction, or back-billing adjustments.
  5. Formulate a definitive resolution outcome specifying exact financial credits, balance debits, or zero-balance confirmations.
  6. Detail actionable customer remediation steps including home energy audit recommendations or installment schedules.
  7. Document customer communication guidelines to help tier-1 support agents de-escalate subsequent inquiries.

Constraints

  • MUST cite specific kilowatt-hour, therm, or gallon consumption differentials between periods.
  • MUST clearly state whether meter hardware error was present or disproven based on {{investigation_findings}}.
  • MUST NOT use ambiguous utility jargon without providing an immediate plain-language definition.
  • Keep the total report under 600 words while maintaining executive clarity.

Output format

Format the report into four titled sections:

  1. Executive Summary & Verdict (maximum 75 words)
  2. Consumption & Tariff Diagnostics (bulleted analysis)
  3. Financial Reconciliation & Adjustments (itemized ledger table)
  4. Next Actions & Support Guidance (numbered action items)

Self-review

  • Did I reconcile every dollar of {{disputed_charge_amount}} against documented consumption?
  • Are the technical findings explained simply for {{customer_account_type}} comprehension?
  • Does the report provide clear marching orders for frontline customer success teams?
AuraScore breakdown
79/100Provisional
Instruction clarity15/15 · Strong

Explicit role, a named task, and discrete steps the model can follow.

Context architecture12/12 · Strong

Background, inputs and variables the model needs before it starts.

Constraint engineering10/12 · Adequate

Hard boundaries — what the model must and must not do.

Output specification6/14 · Thin

A named, field-level shape for the response.

Reasoning structure10/10 · Strong

Ordered work items that force analysis before an answer.

Model compatibility10/10 · Strong

Length and structure that travel across frontier models.

Token efficiency5/10 · Thin

Signal density — instruction weight without padding.

Reusability7/7 · Strong

Documented variables so the scaffold adapts to new inputs.

Robustness3/5 · Adequate

Quality bar, assumptions and behaviour when inputs are thin.

Observed performance1/5 · Thin

How much real usage the template has behind it.

support-success
support-general
energy-utilities
billing support
utilities
dispute resolution