In complex complaints with multiple parties (an insurance case involving a third party, a marketplace dispute, a complaint that crosses internal departments), AI is the case manager rather than the resolver. It coordinates the parties, schedules the steps, keeps the customer updated, and escalates to humans for the judgement calls. The single-conversation pattern AI is good at does not match the multi-party shape; the AI has to operate differently.

A customer complains that a delivery driver damaged their property on the way out. The case involves the customer, the delivery company, the retailer, and (depending on jurisdiction) an insurer. Before AI, a senior agent owned the case, made the calls, sent the emails, and pushed it to resolution over weeks. The AI version is not faster at resolving it; the AI version keeps it from being dropped.

What people in the field are saying

Service Matters covers the orchestration side of complex cases in "Demystifying orchestration: the key...", arguing that multi-party coordination is exactly where most AI deployments stop being autonomous and start being supervisory.

Why does AI struggle with multi-party cases?

Three reasons. The AI's natural unit is one customer and one conversation; multi-party cases have several customers (or non-customers) involved. The judgement calls (who is at fault, what the policy applies to, what level of compensation is fair) require reading context the AI does not have access to. The timing depends on the slowest party, which the AI cannot speed up by being polite.

What does the AI do well in these cases?

Tracking the state. Knowing who has responded and who has not. Sending the right update to the customer at the agreed cadence. Chasing the internal owner when their step is due. Capturing what each party said in the audit trail. All the mechanical case-management work that humans used to do badly because there was always something more urgent to attend to.

What does the AI not do?

The decisions. Whether to side with the customer over the marketplace seller. Whether to issue a goodwill credit while the third party is determined. Whether to escalate to legal. Each of these is a human call, and the AI's value is in making sure the human gets the call clearly and on time, not in trying to make it.

What does the customer experience?

A case that does not lose its memory. Updates at the cadence they agreed at intake. A clear point of contact (a human, named, who owns the decisions) plus the AI handling the coordination between updates. The complaint takes the same number of weeks; the customer chases less, because the case chases itself.

What is the practical first step?

Pick one complex case type (delivery damage, refund involving a third party, a complaint crossing two departments). Define the parties, the steps, the SLAs, the human decision points. Let the AI run the calendar and the updates; let the human handle the decisions. Measure customer-initiated chase rate before and after. The reduction is the value.

Related: use case 14: managing a complaint that takes weeks, use case 9: routing across multiple AI agents, and use case 8: handling a first notice of loss.