NLU - Intents vs. Vocabulary sources and entities

Martalena
Tera Contributor

Dear Community, 

 

In my company, we are currently setting up VA (Vancouver release) and encountered a few obstacles in the process. 

 

NLU setup: Our Service Catalog contains multiple entries with similar names (e.g., “external account”, “technical account” etc,). The entries belong to different categories. Not sure then how to respond to users’ query related to just “account”. Creating one intent #Account and having it linked to the Catalog table seems a no-go option - There is no common denominator (one synonym) for all accounts entries.  

Should we create separate intents followed by a vocabulary list for each account type?  

 

Entities: If we stick to a vocabulary source, should we map entities like in the example: “I want to order @CatalogItem” = “I want to order a guest account” with a “guest account” an entity”?  

How about extending @CatalogItem for all items of the catalog table (not only the accounts)? How can we define a synonym for the vocabulary source? 

 

If rather a vocabulary list, is a simple entity recommended?  

 

Thank you in advance for your feedback 

 

0 REPLIES 0