Regulatory fee and surcharge questions
How do we answer a customer's question about a tax, fee or surcharge on the bill with the line-item explanation, and route any correction for approval?
Explain each line from its definition and correct only by rule. When a customer questions a tax, fee or surcharge, Callvu classifies the line (a government-imposed tax, a government-mandated fee the carrier collects such as the 911 fee, a carrier cost recovery charge such as the federal universal service charge or a regulatory recovery fee, or a carrier-chosen fee), prefills the line's definition, the rate, the jurisdiction and the basis for this customer's lines and address, presents the explanation in plain words with the distinction between what is required and what the carrier chooses, checks the amount against the rate and the address, and where the check finds an error (a wrong jurisdiction, a rate change not applied, an exemption on file not applied) routes the correction to the billing or tax desk in the Decision Desk with only the allowed outcomes.
In scopeSimpleCallvu moves: classify, decide
Last updated November 7, 2026.
The problem today
The agent called the universal service charge a tax, the customer repeated it to the commission, and the complaint was about the explanation.
A telecom bill carries a dozen taxes, fees and surcharges with similar names and different natures: taxes imposed by governments, fees the government requires the carrier to collect, charges the carrier recovers its own costs through, and fees the carrier simply chooses. Customers ask what they are; agents guess; the truth-in-billing rules require the bill and the explanation to be clear and not misleading about which is which.
Each line has a definition, a rate, a jurisdiction and a basis (a per-line amount, a percentage of certain charges, an address-based rate). The explanation can be generated from them for the customer's own bill. The amount can be checked against the rate and the service address, and a real error (a rate change not applied, a wrong jurisdiction, an exemption on file not applied) is a correction with an approver, not a courtesy credit.
The right explanation ends most of these calls; the right check ends the rest.
How it runs
From the requestto the system of record.
A customer questions a tax, fee or surcharge line in the app, by chat, with an agent or through an AI assistant. Callvu opens the question against the bill line.
- Customer
- Selects the line and reads the explanation.
- Agent
- Sees the same explanation on a call and does not guess.
- Billing or tax desk
- Decides corrections in the Decision Desk.
- Callvu
- Classifies, prefills the definition and basis, explains, checks and routes.
Classify the line
The questioned line is classified by its nature: a government-imposed tax (sales, communications, utility user), a government-mandated fee the carrier collects and remits (the state or local 911 fee, a telecommunications relay service fee), a carrier cost recovery charge (the federal universal service charge at the quarterly contribution factor, a regulatory cost recovery fee, an administrative fee), or a carrier-chosen fee; the classification sets the explanation's wording and whether an exemption can apply.
Prefill and explain
The line's definition, the rate or the factor in effect for the bill period, the jurisdiction from the service address, the basis (per line, per account, a percentage of which charges) and the amount on this customer's bill are prefilled from the billing and tax engines, and the explanation is presented in plain words with the required distinction between what the carrier must collect and what it chooses to charge.
Check and decide
The amount is checked against the rate, the basis and the service address and any exemption on file; a correct line ends with the explanation; a discrepancy (a rate change not applied, a wrong jurisdiction from an outdated address, an exemption not applied, a fee charged on a line type it does not apply to) becomes a proposed correction that goes to the billing or tax desk in the Decision Desk with the check and only the allowed outcomes (correct and credit, correct going forward, or confirm as billed with the reason).
Record
The question, the explanation given and any correction with its approver are recorded on the account in the billing system, the customer receives the explanation in writing where they ask, and the pattern of questions by line feeds the bill design and the agent guidance.
Where it ends: The customer received the right explanation of the line from its definition, the amount was checked, and a real error was corrected with an approver rather than credited to end the call. The Decision Trace shows the classification, the check and any decision; the Audit Trace shows the question, the explanation and the correction with time.
Runtime enforcement
What is enforcedwhile the work runs.
The regulations preloaded in Callvu Studio and the bank's own policies, applied as steps that run, not lines in a binder. A step that breaks a rule does not run, so a completed run was compliant.
The handoff
Between the front doorand the back office.
The front door
The app's bill view, chat, an agent on a call or an AI assistant; the explanation comes from the same record in every channel.
The back office
The billing or tax desk decides only real corrections; the bill design team sees the question pattern.
The Decision Desk
- A checked discrepancy goes to the billing or tax desk in the Decision Desk with the check and only correct and credit, correct going forward, or confirm as billed with the reason.
Proof
In scope.Proof at scale, not one process at a time.
The kind of process Callvu runs in production for customers in this industry. Ask for a reference on this exact process. The results below are the industry's published proof; each claim code links to its record on agents.callvu.com.
More than 1,000 processes are live across Callvu customers.
Across Callvu customers
AT&T runs close to 100 processes on Callvu, used by 55,000 agents.
Questions
What buyers ask next,answered plainly.
Is the universal service charge a tax?
No. It is the carrier's recovery of its contribution to the federal universal service fund at the FCC's quarterly factor, and the rules require it to be described that way, not as a tax.
When is a line corrected?
When the check against the rate, the basis, the service address and any exemption on file finds an error, and the billing or tax desk approves the correction with the reason.
Can the customer get the explanation in writing?
Yes, from the same record, in any channel.
Related processes
Bring this process, or the one that costs you most.
We build it against your policies and your systems, train your team and stay with you through launch. You are live in weeks.