




When should I fine-tune Agent intents? For most use cases involving general Q&A, fine-tuning intents is not necessary. Our own internal tests have shown that AI-generated intents are typically sufficient for good Agent routing. Allowing bot makers to control intent classification at a granular level empowers them to enhance chatbot performance in situations where many AI Agents are involved, or where the chatbot requires a high degree of precision. When designing a multi-agent setup, we recommend keeping to a “MECE” approach. “MECE” refers to - Mutually Exclusive, Collectively Exhaustive. In other words, no gaps, no overlaps. Ideally, you want the situation where:User-facing Agent A handles:- intent class 1
- intent class 2
- intent class 3
- etc.
User-facing Agent B handles:- intent class 10and there is minimal overlap in intents among Agents. All your Agents combined should cover all possible intents your users might have. But since you can’t ever account for all intents in the universe, and given the fact that intents are presented in natural language which can have multiple permutations to express the same meaning, there is no deterministic way to get 100% consistency. But you can get pretty close with an optimized setup. During your chatbot’s operations, it is important to monitor incoming conversations and identify instances where the wrong Agent was chosen to handle a user’s query. In these situations, we recommend that you make use of our “Debug mode”. In this mode, if you have multiple user-facing Agents set up, you will see “Intent” and “Active Agent” show up alongside every user query that underwent Agent routing.
- intent class 11
- intent class 12
- etc.

title: Fine Tuning Agent Intents
When your chatbot has multiple user-facing Agents, Chatwize’s AI Supervisor automatically assigns the most appropriate user-facing Agent to handle the user’s input queries. It does so by considering the most recent chat history to determine the user’s intent, then looks for the most suitable Agent by looking at each Agent’s name, description and prompt. In our article Multi-Agent Chatbot, we covered some best practices on Agent description writing and provided a number of examples. However, as comprehensive as the AI Supervisor tries to be, there will still be scenarios where Agent descriptions do not effectively cover all practical use case scenarios. When user-facing Agents are created or modified, we automatically generate a number of intents along with example user queries to serve as reference for the AI Supervisor. These intents can be reviewed, customized, or deleted through the AI Supervisor Settings interface. The AI Supervisor makes use of these intents directly when evaluating each Agent’s relevance in handling the user’s input query, so they are crucial to the core routing algorithm. To fine-tune Agent intents, go to AI Supervisor Settings -> Intents:


Note: AI-Generated Intents will be overwritten each time you edit the Agent name, description, or prompt.
On the other hand, Fixed Intents are permanent and only deleted if you manually do so.
When should I fine-tune Agent intents?
For most use cases involving general Q&A, fine-tuning intents is not necessary. Our own internal tests have shown that AI-generated intents are typically sufficient for effective Agent routing. Allowing bot makers to control intent classification at a granular level empowers them to enhance chatbot performance in situations where many user-facing Agents are involved, or where the chatbot requires a high degree of precision. When designing a multi-agent setup, we recommend keeping to a “MECE” approach. “MECE” refers to - Mutually Exclusive, Collectively Exhaustive. In other words, no gaps, no overlaps. Ideally, you want the situation where:User-facing Agent A handles:- intent class 1
- intent class 2
- intent class 3
- etc.
User-facing Agent B handles:- intent class 10and there is minimal overlap in intents among Agents. All your Agents combined should cover all possible intents your users might have. But since you can’t ever account for all intents in the universe, and given the fact that intents are presented in natural language which can have multiple permutations to express the same meaning, there is no deterministic way to get 100% consistency. This is true for all chatbots that rely on “intent classification” workflows, regardless of whether they are LLM-powered or take a traditional “flowchart” approach. During your chatbot’s operations, it is important to monitor incoming conversations and identify instances where the wrong Agent was chosen to handle a user’s query. In these situations, we recommend that you make use of our “Debug mode”. In this mode, if you have multiple user-facing Agents set up, you will see “Intent” and “Active Agent”show up alongside every user query that underwent Agent routing.
- intent class 11
- intent class 12
- etc.
