A line-by-line explanation works only if every line traces to the record that produced it. The agent walks the customer through each charge and credit in order, naming the period, the rate and the source. Where a line reflects a decision, such as a rate change or a penalty, it explains the line and passes the "why" to a person.
What is a line-by-line bill explanation, and who owns it?
Customers who ask "why is my bill so high?" often need more than a summary. They want to go through it: this line is your monthly charge, this one is usage above your allowance on these dates, this is interest on the balance carried from last month, this is a credit for the outage. The bill is a summary of many records, and the explanation unpacks it.
Billing operations owns the bill and its records. Pricing or product owns tariffs and rates. Credit risk owns decisions about limits and rates on credit products. Compliance, as the second line of defence, reviews the approved descriptions of each line type. The agent explains, within the limits our guide to the AI support agent that knows when to say no sets.
What does the agent prepare, and what does a person approve?
- Person, compliance and billing: approve a description for each line type. What a "late payment fee" or "usage above allowance" line means, in plain words. The agent fills in the specifics.
- Agent, depth 1: authenticates the customer and retrieves the bill.
- Agent, depth 1: traces each line to its source: the tariff entry, the usage records, the interest calculation, the payment received, the credit applied.
- Agent, depth 3: explains in order. For each line: what it is, the period, the quantity or rate, and how it was calculated, all from the source records. The customer can stop at any line and ask more.
- Agent, depth 3: compares with the previous bill and names what changed: a discount ending, higher usage, a new charge, a rate change.
- Agent, depth 1: recognises lines that reflect decisions. A change in credit limit, an interest rate increase, a penalty, a fee applied at someone's discretion.
- Agent, depth 3: explains the line, not the decision. "This line is interest at the new rate of the account, which changed on this date." Why the rate changed goes to the team that decided it.
- Agent, depth 2: drafts disputes or queries for any line the customer challenges, with the source records attached.
- Person, billing specialist or credit team: answers decision questions and decides disputes.
| Step | The agent does | Depth | Stays with a person |
|---|---|---|---|
| Descriptions | Nothing | none | Approving line descriptions |
| Retrieve | Pulls bill | 1 | Nothing |
| Trace | Links each line to source | 1 | Nothing |
| Explain | Walks through each line | 3 | Nothing |
| Compare | Names changes from last bill | 3 | Nothing |
| Decisions | Spots decision lines | 1 | Nothing |
| Explain line | States what the line is | 3 | Explaining the decision |
| Dispute | Drafts with records | 2 | Deciding the dispute |
Which controls matter, and what evidence does each leave?
No line without a source. If the agent cannot trace a line, it says so and raises a query rather than guessing. Evidence: source references for every line explained.
Approved descriptions. Line types are described the same way for every customer. Evidence: description version cited.
Decisions stay with their owners. Explaining why a credit limit was lowered strays into the decision itself; see AI agents and credit decisions: where the line sits. Evidence: routing records for decision questions.
Automated decisions are flagged. Where a line results from a decision made solely by automated means with significant effect, GDPR Article 22 gives the customer rights to human involvement, as automated decisions under GDPR: where agents cross the line explains. The agent routes such questions to a person. Evidence: routing and response records.
Compliance samples explanations. Evidence: review results, kept independent of the support team, in line with a second-line separation checklist for compliance agents.
What should you measure?
- Bills explained without transfer, and the lines that most often lead to transfer.
- Lines the agent could not trace. Each is a data problem in billing.
- Disputes raised after an explanation, and how many were upheld.
- Decision questions routed and how quickly the owning team answered.
- Repeat contacts about the same bill.
Where does it usually go wrong?
The agent recalculates. It multiplies usage by rate and gets a different figure from the bill, then tries to explain the difference. Use the billing system's calculation and raise a query if it looks wrong.
Rounding and pro-rating confuse. Part-month charges and rounding create small differences. Approved descriptions should explain them once, clearly.
Decision lines are justified. Asked why the interest rate rose, the agent offers a reason it inferred. Only the deciding team knows.
The explanation is too long. A twelve-line bill explained in full can bury the answer. Start with what changed, then offer to go through the rest.
Third-party charges are owned by nobody. Bills often include charges collected for someone else, such as premium services or partner subscriptions. The agent can say what the line is and who it is from, but disputes about the underlying service may belong to that third party. Your approved description should say how customers raise them.
Credits are promised. Walking through a line the customer dislikes leads to "I can remove that for you". The agent cannot.
Questions people ask
Can the agent explain a bill to someone who is not the account holder?
Only an authorised party under your rules. Bills reveal usage, location and spending; the wider position is in can an AI agent answer questions about a customer's bill?
What if the bill itself is wrong?
The agent raises a query with the source records showing the mismatch. Billing operations corrects bills; the agent tells the customer what happens next.
Should the explanation be sent in writing after a call?
It helps. A written summary of the lines discussed, generated from the same source records, lets the customer check later and reduces repeat contacts.