How to name your intents properly

A must-have to get the best out of your analytics

A good practice when designing your Agent is to name your intents in the most descriptive way possible. An intent name should be as self-explanatory as possible.

At EVO Dynamics, we follow the most common practices, also adopted by Google and Microsoft as guidelines that work as follows:

Intention.expected action.details

For example. When a user says “- hello, how are you?” you want to capture that as a Small Talk type of question, the user intention here is to establish small talk; + greetings which is the action the user performed, they are saying Hi.

So a recommended name for this intent will be:

smalltalk.greetings.hello

Another example could be when a user say “- where is my order?”
We can identify that as a Sales type of question, the user is asking a question related to a purchase; + delivery status is the expected information the user is seeking.

So a recommended name for this intent will be:

sales.delivery status

EVO Dynamics uses this naming convention to identify Topics, grouped by the user intent themes, such as Sales, SmallTalk, Complaints, Business Info, etc.

A few more examples of the intent names could be:

business.opening hours
business.location
business.website

membership.cancel
membership.card levels – info
membership.card level – gold

sales.delivery status
sales.order cancelation
sales.discount get

Hope this helped! If you have any questions please ping us at support@evodynamics.io

Happy analyzing!