A customer writes: "My order arrived damaged, I was billed twice for it, and I need to update my shipping address." The agent resolves the damaged item thoroughly but never addresses the double charge or the address change. Which design best handles requests like this?

Answer: A — Split it into distinct items, investigate each in parallel with shared context, then synthesize one resolution

Multi-concern requests should be decomposed into distinct items, each investigated in parallel using shared context (the same customer and order), then synthesized into one unified resolution. Handling one issue (b) pushes work back to the customer, escalating everything (c) wastes the agent's capability, and unconnected conversations (d) lose the shared context that links the charge and the damaged order.