Can generated cases contain several requests that need different owners?

A retail support officer opens CASE-0724 containing two requests: replacement of a damaged appliance and correction of the tax invoice. Order ORD-3308 links the product, delivery and invoice. The returns team can authorise a replacement, while the billing team owns invoice corrections.

The generated environment begins with one unassigned intake record. The agent creates WORK-0811 for the damaged item and WORK-0812 for the invoice correction, linking both to CASE-0724 and ORD-3308. It assigns each work item to the team with the relevant authority.

The state changes from a single unresolved intake to two independently owned obligations. The parent case remains open until both obligations reach their defined completion states. Sending everything to returns would leave the invoice request without an accountable owner; duplicating the full request into both queues could trigger conflicting customer responses.

MirrorFirm could generate the incoming message, order relationships, permitted decomposition actions and parent completion rule. The case teaches evaluators to inspect whether an agent preserves every requested outcome without treating one customer's message as necessarily one indivisible task.