The CreatorCon Call for Content is officially open! Get started here.

NLU Not working for OOB and Custom Topics

prathvi raj mis
Tera Contributor

Hi,

I am facing issue with NLU for my custom topics and OOB topics. I have created a NLU model With 2 intents and 14 utterances. The model trains and publishes successfully and works fine when an utterance is searched in the testing text box inside the NLU model Developer page. But when it is linked to a topic and published, the VA does not respond to any of the 14 utterances.

I have tried using the same steps and procedure in my PDI, there VA works fine.

For Example 

My intent is Account and utterances are 'My account' or 'I have an Issue with account' or 'account problem'. When it is tested with the built-in test option in the NLU model creator it works but when the Model is linked with a topic and is tested using Virtual Agent it doesn't work.

FYI- The VA does not work for OOB models and topics also.

Please respond,

Thanks

7 REPLIES 7

Brian Bakker
ServiceNow Employee
ServiceNow Employee

Hello Eric,

In the Default chat experience, you can change the existing Setup Topic linked to the Setup Topic type. I created a new custom chat experience, set it to active with the order set to 1 with just one Setup Topic linked to a new Greetings topic linked to a new Greetings intent and the VA Topic has an updated Greetings message and I got it working as expected, as per my screenshots -

find_real_file.png

 

find_real_file.png

 

find_real_file.png

If the issue persists, please raise a case with Global Technical Support via the Support web site.

Best regards,

Brian

Hi Brian, the link goes to the wrong page (many links in community point to the same page) which shows "

Analyze and optimize business processes"

It was pointing to Rome documentation, which no longer exists. Updated it to point to the Vancouver version - Setting up chat experiences for Virtual Agent users 

 

Not sure why, when it does not find the page, it does not search our documentation on the same title, as it has not changed. If it does point to the incorrect page, I suggest searching for the same title in our Documentation portal to find the referenced documentation. Apologies for the inconvenience.

 

Regards,

Brian