Universal Containers’ Agentforce Service Agent has been live for four weeks. Agent Optimization in Agentforce Observability shows the main support intent cluster scoring low quality, with score reasons citing ambiguous subagent match. The Session Trace confirms the reasoning engine is consistently selecting the wrong subagent on most turns.
What is the most viable solution to resolve the issue?
Submit