Skip to content
MirrorFirm

How can generated state represent a bill that is only partly eligible for follow-up?

A utility billing case separates a disputed charge from an undisputed balance, creating a task where contact eligibility must be assessed below account level.

A utility billing officer reviews account ACC-4726 after bill BILL-9083 passes its follow-up threshold. The bill contains a usage charge and an equipment charge. Dispute DISP-1654 concerns the equipment charge, while the usage charge remains unpaid and undisputed.

The generated policy applies a contact hold to disputed components. It permits a reminder about the undisputed balance, provided the message does not present the disputed amount as payable. The account summary shows the total balance, but line-level records identify the separate eligibility states.

The agent retrieves the dispute scope, calculates the eligible amount and prepares a reminder limited to that amount. It also records why the equipment charge was excluded. When a billing reviewer expands the dispute to cover the usage calculation, the eligible balance changes to zero and the pending reminder must be withdrawn.

MirrorFirm could generate the bill lines, dispute links, policy clauses, draft message and changing eligibility state. This teaches evaluation teams to test scope propagation: a restriction should follow the records it actually covers. The consequence is concrete because an account-level shortcut either demands a held amount or suppresses a permitted action.

Test whether agents apply restrictions to the correct charge components instead of treating an entire account as uniformly collectible.

Audience:
Evaluation teams
Content type:
Scenario
Buyer question:
What can be generated

Content release: r-a220eb6e099b243b

More on Overdue follow up