Classification
Use this node when your agent’s response is dependent on the user input, similar to "Conditions". However, here we classify into intents.
In most cases, it will be the “Classification” node that follows “Collect Input”. Once you collect an input, it needs to be classified into the right intent. Click on the module and choose the parameter (the one you used in “Collect Input”) and the intent/s relevant for the classification.
“Missed” - This tab will be triggered if the agent is unable to classify the user input. You can define the default behavior by connecting “Missed” to any other node.
The intent section is where you will create the knowledge and training for your agent, which later will be used to classify the user's intent. Each intent will encompass one use case, e.g. "I want to change my password" will be one intent and "
Your agent will use this list of utterances to classify user inputs. Every example you will enter should represent a sentence callers may use to attain a specific answer or action.
Add as many examples as possible to make sure your agent is trained and able to understand the different ways people are referring to one query.
Aside from the Tester, you can test your agent's accuracy with the "Train & Test" Feature.
Enter a user query you want to test and the feature will return the intent(s) it would classify the phrase into.
The test query does not need to already be part of the user expressions in the intent, feel free to choose new phrases. You can add any test sentence you tried matching it with an intent to the training set by clicking the "+" sign on the side.
The probability percentage shows you how accurately this phrase would be classified into an intent.
Don't get discouraged if the correct intent doesn't show 100% probability. It might show a few intents that get a very small percentage of probability as well. All intents the agent finds relevant for this query will get 100% probability together.
For very ambiguous intents, the probability might be below 70% and show yellow. You might want to have a look here at how to improve your training set or deal with ambiguous intents.
In case, the AI cannot match your query to any intent, it will give the intent "sys.default" as the highest score. Sys.default means that if tested, this query would go to the Missed tab.
Large classification nodes with a vast number of intents tends to lead to ambiguity between intents and therefore lots of misclassifications. Use the hierarchical system to classify when you have a large number of intents.
Here's how to do it:-
In the first classification node include all the general intents, after that add another classification node to further classify the action or sub intent related to that intent.
For example, the first node includes the general intents of Reservations and Facilities. In the next adjoining classifications node will include intents for change reservation, new reservation, cancel reservation connected to Reservations in the first node and gym, pool, club attached to Facilities from the first node.
Use classification node only when the entity type is sys.any, for other entity types, use the condition node.
Last modified 7mo ago