QuestionQ75

VerifiedAgents and Workflows

A new agent built by your team handles customer support tickets, but it routinely becomes confused when one ticket spans billing, shipping, and product issues. The agent often loses track of which sub-issues it has already addressed and returns to the same one. The team is considering architectural changes.

What architectural change would you recommend?

Explanation

An orchestrator can divide a cross-domain ticket into sub-issues, delegate each to a specialist, and coordinate the results. Explicitly tracking each sub-issue’s status helps prevent duplicate work; delegation alone does not guarantee that tracking. This approach also allows the handling sequence to adapt to the ticket. (learn.microsoft.com)

Learn more

Community Discussion

No comments yet. Be the first to start the discussion!