Should an agent resolve a billing dispute before offering a support referral?

**Should the agent finish the dispute first?**

The environment's policy should answer that question explicitly. A useful configuration allows a billing investigation and a support referral to proceed together when their prerequisites are satisfied. The customer may dispute part of a charge while being unable to pay the undisputed amount.

**What makes this difficult for an agent?**

Single-label workflows encourage premature classification. If an agent must choose either billing dispute or payment difficulty, it may discard relevant information to fit the interface. That can produce a tidy case record while leaving a customer's stated need unaddressed.

**How should builders represent the interaction?**

Use separate linked cases with their own owners, evidence and completion conditions. A correction to the disputed charge can update the account balance without automatically cancelling the support referral. Equally, accepting a referral should not imply acceptance of the disputed charge.

**What could MirrorFirm generate?**

A task pack could contain conversations, linked case histories and policy rules that distinguish the two processes. Builders can then examine whether agents preserve both concerns, explain their relationship clearly and avoid making one team's decision on behalf of another.