What does a difficult handover teach an agent?

A billing officer acknowledges CASE-0412 after a customer disputes a meter adjustment. The complaint record links to invoice INV-2187 and meter event MTR-0631. The billing officer requests an investigation from the meter operations team because the adjustment depends on a disputed reading.

The meter operations team rejects the transfer: it can verify the reading, but the billing team remains responsible for the complaint. The case now contains a rejected assignment request, an outstanding evidence request and an approaching escalation threshold. Its owner has not changed.

The agent must distinguish those records. It keeps the billing officer accountable, requests the specific reading evidence and escalates the unresolved dependency through the configured route. Marking the case as transferred would leave the complaint unattended while its deadline continues to approach.

The consequence is operational: the next responsible role either receives an actionable escalation or finds a case that everyone assumes belongs elsewhere. This teaches that handover is an agreement represented in state, not a sentence in a case note. MirrorFirm could generate this branching interaction as an environment task with accepted and rejected transfer outcomes.