{"id":18052,"date":"2018-06-06T07:50:36","date_gmt":"2018-06-06T07:50:36","guid":{"rendered":"https:\/\/developer.kore.ai\/v9-3\/?post_type=docs&#038;p=14310"},"modified":"2022-10-06T07:13:45","modified_gmt":"2022-10-06T06:13:45","slug":"bot-analysis","status":"publish","type":"post","link":"https:\/\/developer.kore.ai\/v9-3\/docs\/bots\/analyzing-your-bot\/bot-analysis\/","title":{"rendered":"NLP Insights"},"content":{"rendered":"<p><span style=\"font-weight: 400\">The NLP Insights helps you gain in-depth insights into the analytics data and assess your virtual assistant\u2019s performance in identifying and executing tasks. You can improve your VA\u2019s performance based on the insights. The <\/span><b>Analyze &gt; NLP Insights<\/b><span style=\"font-weight: 400\"> page shows the specific information in the following sections:<\/span><\/p>\n<ul>\n<li style=\"font-weight: 400\"><span style=\"font-weight: 400\">\u00a0<\/span><a href=\"https:\/\/developer.kore.ai\/v9-3\/docs\/bots\/analyzing-your-bot\/bot-analysis\/#Intent_Found\"><span style=\"font-weight: 400\">Intent Found<\/span><\/a><span style=\"font-weight: 400\">: Number of identified intents<\/span><\/li>\n<li style=\"font-weight: 400\"><span style=\"font-weight: 400\">\u00a0<\/span><a href=\"https:\/\/developer.kore.ai\/v9-3\/docs\/bots\/analyzing-your-bot\/bot-analysis\/#Intent_Not_Found\"><span style=\"font-weight: 400\">Intent Not Found<\/span><\/a><span style=\"font-weight: 400\">: Number of unidentified intents<\/span><\/li>\n<li style=\"font-weight: 400\"><a href=\"https:\/\/developer.kore.ai\/v9-3\/docs\/bots\/analyzing-your-bot\/bot-analysis\/#Unhandled_Utterances\"><span style=\"font-weight: 400\">Unhandled Utterances<\/span><\/a><span style=\"font-weight: 400\">: Number of unhandled utterances<\/span><\/li>\n<li style=\"font-weight: 400\"><a href=\"https:\/\/developer.kore.ai\/v9-3\/docs\/bots\/analyzing-your-bot\/bot-analysis\/#Failed_Task\"><span style=\"font-weight: 400\">Failed Task<\/span><\/a><span style=\"font-weight: 400\">: Number of unsuccessful tasks<\/span><\/li>\n<li style=\"font-weight: 400\"><a href=\"https:\/\/developer.kore.ai\/v9-3\/docs\/bots\/analyzing-your-bot\/bot-analysis\/#Performance\"><span style=\"font-weight: 400\">Performance<\/span><\/a><span style=\"font-weight: 400\">: <\/span><span style=\"font-weight: 400\">Monitor all the scripts and API services and capture the number <\/span><span style=\"font-weight: 400\">of failed services or scripts during the interactions<\/span><\/li>\n<li style=\"font-weight: 400\"><a href=\"https:\/\/developer.kore.ai\/v9-3\/docs\/bots\/analyzing-your-bot\/bot-analysis\/#Pinned\"><span style=\"font-weight: 400\">Pinned<\/span><\/a><span style=\"font-weight: 400\">: Pinned NLP Insight records. Specific records are pinned to highlight them for easy access and viewing.<\/span><\/li>\n<li style=\"font-weight: 400\"><a href=\"https:\/\/developer.kore.ai\/v9-3\/docs\/bots\/analyzing-your-bot\/bot-analysis\/#Debug_Log\"><span>Debug Log<\/span><\/a><span>: Custom Debug logs include user conversations from across all channels, for analyzing your VA.<\/span><\/li>\n<\/ul>\n<p><a ref=\"magnificPopup\" href=\"https:\/\/kore-wordpress.s3.us-east-2.amazonaws.com\/developer.kore.ai\/v9-3\/wp-content\/uploads\/sites\/29\/20220818080831\/Analyze1.png\"><span style=\"font-weight: 400\"><img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/kore-wordpress.s3.us-east-2.amazonaws.com\/developer.kore.ai\/v9-3\/wp-content\/uploads\/sites\/29\/20220818080831\/Analyze1.png\" alt=\"\" width=\"640\" height=\"261\" class=\"alignnone size-large wp-image-44051\" srcset=\"https:\/\/kore-wordpress.s3.us-east-2.amazonaws.com\/developer.kore.ai\/v9-3\/wp-content\/uploads\/sites\/29\/20220818080831\/Analyze1.png 1896w, https:\/\/kore-wordpress.s3.us-east-2.amazonaws.com\/developer.kore.ai\/v9-3\/wp-content\/uploads\/sites\/29\/20220818080831\/Analyze1-300x122.png 300w, https:\/\/kore-wordpress.s3.us-east-2.amazonaws.com\/developer.kore.ai\/v9-3\/wp-content\/uploads\/sites\/29\/20220818080831\/Analyze1-1024x418.png 1024w\" sizes=\"auto, (max-width: 640px) 100vw, 640px\" \/><\/span><\/a><\/p>\n<h2><span class=\"ez-toc-section\" id=\"Intent_Found\">Intent Found<\/span><\/h2>\n<p><span style=\"font-weight: 400\">An intent refers to the goal the customer has in mind when typing in a question or comment. The\u00a0 phrases used to express the intent are called user utterances. The Intent Found tab includes all the user utterances identified by the platform.\u00a0<\/span><\/p>\n<div class=\"alert alert-info\"><b>Note:<\/b><span style=\"font-weight: 400\"> You need to check for false positives in scenarios where the utterance is wrongly identified for an int<\/span><span style=\"font-weight: 400\">ent<\/span><span style=\"font-weight: 400\">.<\/span><\/div>\n<div><\/div>\n<p><span style=\"font-weight: 400\">See the following table <\/span><span style=\"font-weight: 400\">and <\/span><a href=\"https:\/\/developer.kore.ai\/v9-3\/docs\/bots\/analyzing-your-bot\/bot-analysis\/#Features\"><span style=\"font-weight: 400\">Features<\/span><\/a> section <span style=\"font-weight: 400\">to know more.<\/span><\/p>\n<p><span style=\"font-weight: 400\"><a ref=\"magnificPopup\" href=\"https:\/\/kore-wordpress.s3.us-east-2.amazonaws.com\/developer.kore.ai\/v9-3\/wp-content\/uploads\/sites\/29\/20220818080950\/IntentFound-1.png\"><img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/kore-wordpress.s3.us-east-2.amazonaws.com\/developer.kore.ai\/v9-3\/wp-content\/uploads\/sites\/29\/20220818080950\/IntentFound-1.png\" alt=\"\" width=\"640\" height=\"181\" class=\"alignnone size-large wp-image-44055\" srcset=\"https:\/\/kore-wordpress.s3.us-east-2.amazonaws.com\/developer.kore.ai\/v9-3\/wp-content\/uploads\/sites\/29\/20220818080950\/IntentFound-1.png 1560w, https:\/\/kore-wordpress.s3.us-east-2.amazonaws.com\/developer.kore.ai\/v9-3\/wp-content\/uploads\/sites\/29\/20220818080950\/IntentFound-1-300x85.png 300w, https:\/\/kore-wordpress.s3.us-east-2.amazonaws.com\/developer.kore.ai\/v9-3\/wp-content\/uploads\/sites\/29\/20220818080950\/IntentFound-1-1024x290.png 1024w\" sizes=\"auto, (max-width: 640px) 100vw, 640px\" \/><\/a><\/span><\/p>\n<p><span style=\"font-weight: 400\">The following is an example of Intent Found:<\/span><\/p>\n<p><i><span style=\"font-weight: 400\">User: I want to know my order confirmation<\/span><\/i><\/p>\n<p><i><span style=\"font-weight: 400\">VA: Would you like to switch to Track Order<\/span><\/i><\/p>\n<p><i><span style=\"font-weight: 400\">User: Yes<\/span><\/i><\/p>\n<p><i><span style=\"font-weight: 400\">VA: Lets log you in.<\/span><\/i><i><span style=\"font-weight: 400\"><br \/><\/span><\/i><i><span style=\"font-weight: 400\">\u00a0 \u00a0 \u00a0 How would you like to go ahead &#8211; Log in or Guest?<\/span><\/i><\/p>\n<p><span style=\"font-weight: 400\">In the above conversation, the user utterance of <\/span><i><span style=\"font-weight: 400\">\u2018knowing the order confirmation status\u2019<\/span><\/i><span style=\"font-weight: 400\"> is recognized by the VA and successfully mapped to the Track Order intent.<\/span><\/p>\n<p><strong>Description of the Intent Found Fields<\/strong><\/p>\n<p><span style=\"font-weight: 400\">The following table lists the fields on the Intent Fount tab with descriptions:<\/span><\/p>\n<table>\n<thead>\n<tr>\n<th><b>Fields<\/b><\/th>\n<th><b>Description<\/b><\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td><span style=\"font-weight: 400\">Utterances<\/span><\/td>\n<td><span style=\"font-weight: 400\">The utterances that are identified by the VA. The details on the tab are grouped by utterances based on the similarity, by default. To turn off grouping by utterance, click the <\/span><b>Utterances <\/b><span style=\"font-weight: 400\">header and disable the <\/span><b>Group by Utterances<\/b><span style=\"font-weight: 400\"> option.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400\">Intent<\/span><\/td>\n<td><span style=\"font-weight: 400\">The intent\/task that is identified. The details on the tab can be grouped by intents. By default, the\u00a0 <\/span><b>Group by Intent <\/b><span style=\"font-weight: 400\">option is turned off. To turn it on, click the <\/span><b>Intent <\/b><span style=\"font-weight: 400\">header and enable the <\/span><b>Group by Intent <\/b><span style=\"font-weight: 400\">option.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400\">Traits<\/span><\/td>\n<td>\n<p><span style=\"font-weight: 400\">All the traits that are identified for the listed utterances. The details on the tab can be grouped by traits. By default, the\u00a0 <\/span><b>Group by Traits <\/b><span style=\"font-weight: 400\">option is turned off. To turn it on, click the <\/span><b>Traits <\/b><span style=\"font-weight: 400\">header and enable the <\/span><b>Group by Traits <\/b><span style=\"font-weight: 400\">option.<\/span><\/p>\n<p><span style=\"font-weight: 400\">This information is available for the data generated <\/span><span style=\"text-decoration: underline\"><span style=\"font-weight: 400\">after June 1, 2021<\/span><\/span><span style=\"font-weight: 400\">.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400\">UserID<\/span><\/td>\n<td>\n<p><span style=\"font-weight: 400\">The UserID of the end user related to the conversation. You can view the metrics based on either <\/span><b>Kore User id<\/b><span style=\"font-weight: 400\"> or <\/span><b>Channel User Id<\/b><span style=\"font-weight: 400\">.<\/span><\/p>\n<p><span style=\"font-weight: 400\">Channel-specific ids are shown only for the users who have interacted with the VA during the selected period.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400\">Language<\/span><\/td>\n<td><span style=\"font-weight: 400\">The language in which the conversation occurred.<\/span><span style=\"font-weight: 400\"><br \/><\/span><span style=\"font-weight: 400\"><br \/><\/span><span style=\"font-weight: 400\">If it is a multi-lingual VA, you can select specific languages to filter the conversation that occurred in those languages. The page shows the conversations that occurred in all enabled languages by default.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400\">Date &amp; Time<\/span><\/td>\n<td><span style=\"font-weight: 400\">The date and time of the chat. You can sort the data by either <\/span><b>Newest to Oldest <\/b><span style=\"font-weight: 400\">or <\/span><b>Oldest to Newest<\/b><span style=\"font-weight: 400\">.<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h2><span class=\"ez-toc-section\" id=\"Intent_Not_Found\">Intent Not Found<\/span><\/h2>\n<p><span style=\"font-weight: 400\">Intent Not Found includes all the user utterances that the platform is not able to identify with a dialog task or FAQ either due to <\/span><span style=\"font-weight: 400\">invalid training, less training data or the intent unavailability in the virtual assistant<\/span><span style=\"font-weight: 400\">.<\/span><\/p>\n<p><span style=\"font-weight: 400\">See\u00a0 the following table <\/span><span style=\"font-weight: 400\">and <\/span><a href=\"https:\/\/developer.kore.ai\/v9-3\/docs\/bots\/analyzing-your-bot\/bot-analysis\/#Features\"><span style=\"font-weight: 400\">Features<\/span><\/a> section <span style=\"font-weight: 400\">to know more.<\/span><\/p>\n<p><a ref=\"magnificPopup\" href=\"https:\/\/kore-wordpress.s3.us-east-2.amazonaws.com\/developer.kore.ai\/v9-3\/wp-content\/uploads\/sites\/29\/20220818081040\/IntentNotFound.png\"><span style=\"font-weight: 400\"><img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/kore-wordpress.s3.us-east-2.amazonaws.com\/developer.kore.ai\/v9-3\/wp-content\/uploads\/sites\/29\/20220818081040\/IntentNotFound.png\" alt=\"\" width=\"640\" height=\"228\" class=\"alignnone size-large wp-image-44058\" srcset=\"https:\/\/kore-wordpress.s3.us-east-2.amazonaws.com\/developer.kore.ai\/v9-3\/wp-content\/uploads\/sites\/29\/20220818081040\/IntentNotFound.png 1865w, https:\/\/kore-wordpress.s3.us-east-2.amazonaws.com\/developer.kore.ai\/v9-3\/wp-content\/uploads\/sites\/29\/20220818081040\/IntentNotFound-300x107.png 300w, https:\/\/kore-wordpress.s3.us-east-2.amazonaws.com\/developer.kore.ai\/v9-3\/wp-content\/uploads\/sites\/29\/20220818081040\/IntentNotFound-1024x365.png 1024w\" sizes=\"auto, (max-width: 640px) 100vw, 640px\" \/><\/span><\/a><\/p>\n<p><span style=\"font-weight: 400\">Example of Intent Not Found:\u00a0<\/span><\/p>\n<p><i><span style=\"font-weight: 400\">User: I want to know my account statement<\/span><\/i><\/p>\n<p><i><span style=\"font-weight: 400\">VA: <\/span><\/i><i><span style=\"font-weight: 400\">I\u2019 <\/span><\/i><i><span style=\"font-weight: 400\">m sorry, I did not recognize the value you have entered. Please select a value from the list.<\/span><\/i><\/p>\n<p><span style=\"font-weight: 400\">In the above conversation, the VA does not recognize the user utterance of <\/span><i><span style=\"font-weight: 400\">\u2018knowing the account statement\u2019<\/span><\/i><span style=\"font-weight: 400\">. It could be due to invalid training, less training, or unavailability of intents in the virtual assistant.<\/span><\/p>\n<p><strong>Description of Intent Not Found Fields<\/strong><\/p>\n<p><span style=\"font-weight: 400\">The following table lists the fields on the Intent Not Found tab with descriptions:<\/span><\/p>\n<table>\n<thead>\n<tr>\n<th><b>Fields<\/b><\/th>\n<th><b>Description<\/b><\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td><span style=\"font-weight: 400\">Utterances<\/span><\/td>\n<td><span style=\"font-weight: 400\">The utterances that are not identified by the VA. The details on the tab are grouped by utterances based on the similarity, by default. To turn off grouping by utterance, click the <\/span><b>Utterances <\/b><span style=\"font-weight: 400\">header and disable the <\/span><b>Group by Utterances<\/b><span style=\"font-weight: 400\"> option.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400\">Traits<\/span><\/td>\n<td>\n<p><span style=\"font-weight: 400\">All the traits that are identified for the listed utterances. The details on the tab can be grouped by traits. By default, the\u00a0 <\/span><b>Group by Traits <\/b><span style=\"font-weight: 400\">option is turned off. To turn it on, click the <\/span><b>Traits <\/b><span style=\"font-weight: 400\">header and enable the <\/span><b>Group by Traits <\/b><span style=\"font-weight: 400\">option.<\/span><\/p>\n<p><span style=\"font-weight: 400\">This information is available for data\u00a0 generated <\/span><span style=\"text-decoration: underline\"><span style=\"font-weight: 400\">after June 1, 2021<\/span><\/span><span style=\"font-weight: 400\">.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400\">UserID<\/span><\/td>\n<td>\n<p><span style=\"font-weight: 400\">The UserID of the end user related to the conversation. You can view the metrics based on either <\/span><b>Kore User id<\/b><span style=\"font-weight: 400\"> or <\/span><b>Channel User Id<\/b><span style=\"font-weight: 400\">.<\/span><\/p>\n<p><span style=\"font-weight: 400\">Channel-specific ids are shown only for the users who have interacted with the VA during the selected period.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400\">Language<\/span><\/td>\n<td><span style=\"font-weight: 400\">The language in which the conversation occurred.<\/span><span style=\"font-weight: 400\"><br \/><\/span><span style=\"font-weight: 400\"><br \/><\/span><span style=\"font-weight: 400\">If it is a multi-lingual VA, you can select specific languages to filter the conversation that occurred in those languages. The page shows the conversations that occurred in all enabled languages by default.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400\">Date &amp; Time<\/span><\/td>\n<td><span style=\"font-weight: 400\">The date and time of the chat. You can sort the data by either <\/span><b>Newest to Oldest<\/b><span style=\"font-weight: 400\">\u00a0or <\/span><b>Oldest to Newest<\/b><span style=\"font-weight: 400\">.<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h2><span class=\"ez-toc-section\" id=\"Unhandled_Utterances\">Unhandled Utterances<\/span><\/h2>\n<p><span style=\"font-weight: 400\">The Unhandled Utterances help analyze\u00a0 the unidentified inputs received from the users during a task execution at an <\/span><b>entity node, message node<\/b><span style=\"font-weight: 400\">,<\/span> <span style=\"font-weight: 400\">or <\/span><b>confirmation <\/b><span style=\"font-weight: 400\">node. These insights allow you to identify the need for additional training or new intents and enhance the existing NLU model of the VAs.<\/span><\/p>\n<p><span style=\"font-weight: 400\">In an unhandled utterance, the following new fields are available:<\/span><\/p>\n<ul>\n<li style=\"font-weight: 400\"><b>Prompt Type<\/b><span style=\"font-weight: 400\"> &#8211; A prompt type could be either an <\/span><b>Entity <\/b><span style=\"font-weight: 400\">node, <\/span><b>Message <\/b><span style=\"font-weight: 400\">node, or a <\/span><b>Confirmation <\/b><span style=\"font-weight: 400\">node.<\/span><\/li>\n<li style=\"font-weight: 400\"><b>Node Name <\/b><span style=\"font-weight: 400\">&#8211; Name of the node in which the utterance is not handled<\/span><\/li>\n<li style=\"font-weight: 400\"><b>Task Name<\/b><span style=\"font-weight: 400\"> &#8211; Name of the task in which the utterances are unidentified on an entity, message, or confirmation nodes.<\/span><\/li>\n<\/ul>\n<p><span style=\"font-weight: 400\"><a ref=\"magnificPopup\" href=\"https:\/\/kore-wordpress.s3.us-east-2.amazonaws.com\/developer.kore.ai\/v9-3\/wp-content\/uploads\/sites\/29\/20220818081203\/Unhandled2-1.png\"><img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/kore-wordpress.s3.us-east-2.amazonaws.com\/developer.kore.ai\/v9-3\/wp-content\/uploads\/sites\/29\/20220818081203\/Unhandled2-1.png\" alt=\"\" width=\"640\" height=\"216\" class=\"alignnone size-large wp-image-44061\" srcset=\"https:\/\/kore-wordpress.s3.us-east-2.amazonaws.com\/developer.kore.ai\/v9-3\/wp-content\/uploads\/sites\/29\/20220818081203\/Unhandled2-1.png 1507w, https:\/\/kore-wordpress.s3.us-east-2.amazonaws.com\/developer.kore.ai\/v9-3\/wp-content\/uploads\/sites\/29\/20220818081203\/Unhandled2-1-300x101.png 300w, https:\/\/kore-wordpress.s3.us-east-2.amazonaws.com\/developer.kore.ai\/v9-3\/wp-content\/uploads\/sites\/29\/20220818081203\/Unhandled2-1-1024x345.png 1024w\" sizes=\"auto, (max-width: 640px) 100vw, 640px\" \/><\/a><\/span><\/p>\n<ul>\n<li style=\"font-weight: 400\"><span style=\"font-weight: 400\">Group by functionality is available for<\/span> <b><i>Utterances, Traits, Prompt Type, Task Name, <\/i><\/b><i><span style=\"font-weight: 400\">and <\/span><\/i><b><i>Node Name<\/i><\/b><\/li>\n<\/ul>\n<div class=\"alert alert-info\"><b><i>Note:<\/i><\/b><i><span style=\"font-weight: 400\"> The unhandled utterances are available for all conversations with product version 9.3 or higher.<\/span><\/i><\/div>\n<p><span style=\"font-weight: 400\">See the following table <\/span><span style=\"font-weight: 400\">and <a href=\"https:\/\/developer.kore.ai\/v9-3\/docs\/bots\/analyzing-your-bot\/bot-analysis\/#Features\">Features<\/a> section to know more..<\/span><\/p>\n<p>Unhandled Utterance Examples<\/p>\n<p><span style=\"font-weight: 400\">The following examples show the conversations between the VA and user, with unhandled utterances captured at <\/span><b>Entity<\/b><span style=\"font-weight: 400\">, <\/span><b>Message<\/b><span style=\"font-weight: 400\">, and <\/span><b>Confirmation <\/b><span style=\"font-weight: 400\">nodes.<\/span><\/p>\n<p><b>At an Entity Node:<\/b><\/p>\n<p><span style=\"font-weight: 400\">For example, when the user provides an invalid input at entity or confirmation nodes as follows:<\/span><\/p>\n<p><i><span style=\"font-weight: 400\">User: I want my account statement<\/span><\/i><\/p>\n<p><i><span style=\"font-weight: 400\">VA: Please enter your Customer Id<\/span><\/i><\/p>\n<p><i><span style=\"font-weight: 400\">User: Where do I find it?<\/span><\/i><\/p>\n<p><i><span style=\"font-weight: 400\">VA: Sorry, that is an incorrect input. Please enter your Customer Id<\/span><\/i><\/p>\n<p><span style=\"font-weight: 400\">In the above conversation, if the VA doesn&#8217;t recognize <\/span><i><span style=\"font-weight: 400\">\u201cwhere to find customer id\u201d<\/span><\/i><span style=\"font-weight: 400\"> as an intent or entity, then this utterance is\u00a0 categorized under Unhandled Utterances.<\/span><\/p>\n<p><b>At a Message Node:<\/b><\/p>\n<p><span style=\"font-weight: 400\">For example, when the user provides an invalid input at a message node as follows:<\/span><\/p>\n<p><i><span style=\"font-weight: 400\">User: I want to book a flight for today<\/span><\/i><\/p>\n<p><i><span style=\"font-weight: 400\">VA: Enter the flight number<\/span><\/i><i><span style=\"font-weight: 400\"><br \/><\/span><\/i><i><span style=\"font-weight: 400\">\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 User: 12434<\/span><\/i><i><span style=\"font-weight: 400\"><br \/><\/span><\/i><i><span style=\"font-weight: 400\">\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 VA: Enter number of seats required<\/span><\/i><i><span style=\"font-weight: 400\"><br \/><\/span><\/i><i><span style=\"font-weight: 400\">\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 User: 3<\/span><\/i><i><span style=\"font-weight: 400\"><br \/><\/span><\/i><i><span style=\"font-weight: 400\">\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 VA: Your flight is booked. Would you like to:<\/span><\/i><i><span style=\"font-weight: 400\"><br \/><\/span><\/i><i><span style=\"font-weight: 400\">\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 1. Book a Hotel<\/span><\/i><i><span style=\"font-weight: 400\"><br \/><\/span><\/i><i><span style=\"font-weight: 400\">\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 2. Book a sightseeing tour<\/span><\/i><i><span style=\"font-weight: 400\"><br \/><\/span><\/i><i><span style=\"font-weight: 400\">\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 User: I want to Cancel the Flight<\/span><\/i><i><span style=\"font-weight: 400\"><br \/><\/span><\/i><i><span style=\"font-weight: 400\">\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 VA: I&#8217;m sorry, I don\u2019t understand. Please enter again.<\/span><\/i><\/p>\n<p><span style=\"font-weight: 400\">In the above conversation, if the VA doesn&#8217;t recognize the intent name \u201ccancel flight\u201d as an input at the message node. The intent identification fails and the utterance is categorized under Unhandled Utterances.<\/span><\/p>\n<p><b>At Confirmation Node:<\/b><\/p>\n<p><span style=\"font-weight: 400\">For example, when the user provides an invalid input at a confirmation node as follows:<\/span><\/p>\n<p><i><span style=\"font-weight: 400\">VA: How may I help you<\/span><\/i><\/p>\n<p><i><span style=\"font-weight: 400\">User: I want to book a flight<\/span><\/i><\/p>\n<p><i><span style=\"font-weight: 400\">VA: Enter the number of seats<\/span><\/i><\/p>\n<p><i><span style=\"font-weight: 400\">User: 2<\/span><\/i><\/p>\n<p><i><span style=\"font-weight: 400\">VA: Please confirm if you want two seats<\/span><\/i><\/p>\n<p><i><span style=\"font-weight: 400\">User: I want to hire a cab<\/span><\/i><\/p>\n<p><i><span style=\"font-weight: 400\">VA: I cannot understand it, can you rephrase it<\/span><\/i><\/p>\n<p><span style=\"font-weight: 400\">In the above conversation, when a user enters \u2018I want to hire a cab\u2019 at the confirmation node, it is not recognized and logged under Unhandled Utterances.<\/span><\/p>\n<p><strong>Description of Unhandled Utterances Fields<\/strong><\/p>\n<p><span style=\"font-weight: 400\">The following table lists the fields on the Unhandled Utterances tab with descriptions:<\/span><\/p>\n<table>\n<thead>\n<tr>\n<th><b>Fields<\/b><\/th>\n<th><b>Description<\/b><\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td><span style=\"font-weight: 400\">Utterances<\/span><\/td>\n<td><span style=\"font-weight: 400\">The unhandled utterances for which the inputs received are unidentified. The details in the tab are grouped by utterances based on the similarity, by default. To turn off grouping by utterance, click the <b>Utterances <\/b>header and disable the <b>Group by Utterances<\/b> option.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400\">Traits<\/span><\/td>\n<td>\n<p><span style=\"font-weight: 400\">All the traits that are identified for the listed utterances. The details in the tab can be grouped by traits. By default, the\u00a0 <\/span><b>Group by Traits <\/b><span style=\"font-weight: 400\">option is turned off. To turn it on, click the <\/span><b>Traits <\/b><span style=\"font-weight: 400\">header and enable the <\/span><b>Group by Traits <\/b><span style=\"font-weight: 400\">option.<\/span><\/p>\n<p><span style=\"font-weight: 400\">This information is available for analytics generated <\/span><span style=\"text-decoration: underline\"><span style=\"font-weight: 400\">after June 1, 2021<\/span><\/span><span style=\"font-weight: 400\">.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400\">Prompt Type<\/span><\/td>\n<td><span style=\"font-weight: 400\">A prompt type could be either an <\/span><b>Entity <\/b><span style=\"font-weight: 400\">node, <\/span><b>Message <\/b><span style=\"font-weight: 400\">node, or a <\/span><b>Confirmation <\/b><span style=\"font-weight: 400\">node. To <\/span><span style=\"font-weight: 400\">turn on grouping by Prompt Type, click the <\/span><b>Prompt Type <\/b><span style=\"font-weight: 400\">header and enable the <\/span><b>Group by Prompt Type <\/b><span style=\"font-weight: 400\">option.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400\">Task Name<\/span><\/td>\n<td><span style=\"font-weight: 400\">The task that is identified for the user utterance. To turn on grouping by task name, click the <\/span><b>Task Name <\/b><span style=\"font-weight: 400\">header and enable the <\/span><b>Group by Task <\/b><span style=\"font-weight: 400\">option.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400\">Node Name<\/span><\/td>\n<td><span style=\"font-weight: 400\">The name of the service or script or WebHook within the task that got executed in response to the user utterance. To turn on grouping by node names to which these scripts or services belong, click the <\/span><b>Node Name <\/b><span style=\"font-weight: 400\">header and turn on the <\/span><b>Group by NodeName <\/b><span style=\"font-weight: 400\">option.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400\">UserID<\/span><\/td>\n<td>\n<p><span style=\"font-weight: 400\">The UserID of the end user related to the conversation. You can view the metrics based on either <\/span><b>Kore User id<\/b><span style=\"font-weight: 400\"> or <\/span><b>Channel User Id<\/b><span style=\"font-weight: 400\">.<\/span><\/p>\n<p><span style=\"font-weight: 400\">Channel-specific ids are shown only for the users who have interacted with the VA during the selected period.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400\">Language<\/span><\/td>\n<td><span style=\"font-weight: 400\">The language in which the conversation occurred.<\/span><span style=\"font-weight: 400\"><br \/><\/span><span style=\"font-weight: 400\"><br \/><\/span><span style=\"font-weight: 400\">If it is a multi-lingual VA, you can select specific languages to filter the conversation that occurred in those languages. The page shows the conversations that occurred in all enabled languages by default.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400\">Date &amp; Time<\/span><\/td>\n<td><span style=\"font-weight: 400\">The date and time of the chat. You can sort the data by either <\/span><b>Newest to Oldest <\/b><span style=\"font-weight: 400\">or <\/span><b>Oldest to Newest<\/b><span style=\"font-weight: 400\">.<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h2><span class=\"ez-toc-section\" id=\"Failed_Task\"><span style=\"font-weight: 400\">Failed Task<\/span><\/span><\/h2>\n<p><span style=\"font-weight: 400\">In a scenario where all the user utterances are successfully mapped to an intent, but the task cannot be completed for some reason, then such utterances are listed under this tab. You can group them based on task and failure types to analyze and solve issues with the VA. <\/span><\/p>\n<p><span style=\"font-weight: 400\">See the following table<\/span><span style=\"font-weight: 400\">\u00a0and <\/span><a href=\"https:\/\/developer.kore.ai\/v9-3\/docs\/bots\/analyzing-your-bot\/bot-analysis\/#Features\"><span style=\"font-weight: 400\">Features<\/span><\/a> section <span style=\"font-weight: 400\">to know more.<\/span><\/p>\n<p><b><a ref=\"magnificPopup\" href=\"https:\/\/kore-wordpress.s3.us-east-2.amazonaws.com\/developer.kore.ai\/v9-3\/wp-content\/uploads\/sites\/29\/20220818081255\/FailedTask.png\"><img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/kore-wordpress.s3.us-east-2.amazonaws.com\/developer.kore.ai\/v9-3\/wp-content\/uploads\/sites\/29\/20220818081255\/FailedTask.png\" alt=\"\" width=\"640\" height=\"246\" class=\"alignnone size-large wp-image-44064\" srcset=\"https:\/\/kore-wordpress.s3.us-east-2.amazonaws.com\/developer.kore.ai\/v9-3\/wp-content\/uploads\/sites\/29\/20220818081255\/FailedTask.png 1548w, https:\/\/kore-wordpress.s3.us-east-2.amazonaws.com\/developer.kore.ai\/v9-3\/wp-content\/uploads\/sites\/29\/20220818081255\/FailedTask-300x116.png 300w, https:\/\/kore-wordpress.s3.us-east-2.amazonaws.com\/developer.kore.ai\/v9-3\/wp-content\/uploads\/sites\/29\/20220818081255\/FailedTask-1024x394.png 1024w\" sizes=\"auto, (max-width: 640px) 100vw, 640px\" \/><\/a><\/b><\/p>\n<h2><span class=\"ez-toc-section\" id=\"Failed_Task_Type_of_Issues\"><span style=\"font-weight: 400\">Failed Task &#8211; Type of Issues<\/span><\/span><\/h2>\n<p><span style=\"font-weight: 400\">Different types of issues that occur during a <\/span><a href=\"https:\/\/developer.kore.ai\/v9-3\/docs\/bots\/analyzing-your-bot\/bot-analysis\/#Failed_Task\"><span style=\"font-weight: 400\">Failed Task<\/span><\/a><span style=\"font-weight: 400\"> are listed as follows:<\/span><\/p>\n<ul>\n<li style=\"font-weight: 400\"><span style=\"font-weight: 400\">Task aborted by user<\/span><\/li>\n<li style=\"font-weight: 400\"><span style=\"font-weight: 400\">Alternate task initiated<\/span><\/li>\n<li style=\"font-weight: 400\"><span style=\"font-weight: 400\">Chat Interface refreshed<\/span><\/li>\n<li style=\"font-weight: 400\"><span style=\"font-weight: 400\">Human agent transfer<\/span><\/li>\n<li style=\"font-weight: 400\"><span style=\"font-weight: 400\">Authorization attempt failure \u2013 Max attempts reached<\/span><\/li>\n<li style=\"font-weight: 400\"><span style=\"font-weight: 400\">Incorrect entity failure \u2013 Max attempts reached<\/span><\/li>\n<li style=\"font-weight: 400\"><span style=\"font-weight: 400\">Script failure<\/span><\/li>\n<li style=\"font-weight: 400\"><span style=\"font-weight: 400\">Service failure<\/span><\/li>\n<li style=\"font-weight: 400\"><span style=\"font-weight: 400\">Inactivity or External Events (from ver8.0) \u2013 when the conversation session and as a result, the in-progress task is closed due to inactivity or external events.<\/span><\/li>\n<\/ul>\n<p><strong>Description of Failed Task Fields<\/strong><\/p>\n<p><span style=\"font-weight: 400\">The following table lists the fields on the Failed Task tab with descriptions:<\/span><\/p>\n<table>\n<thead>\n<tr>\n<th><b>Fields<\/b><\/th>\n<th><b>Description<\/b><\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td><span style=\"font-weight: 400\">Utterances<\/span><\/td>\n<td><span style=\"font-weight: 400\">The utterances that are successfully mapped to an intent, but still the task failed due to some issue. See <\/span><a href=\"https:\/\/developer.kore.ai\/v9-3\/docs\/bots\/analyzing-your-bot\/bot-analysis\/#Failed_Task_-_Type_of_Issues\"><span style=\"font-weight: 400\">Failed Task &#8211; Type of Issues<\/span><\/a><span style=\"font-weight: 400\"> for more details. The details in the tab are grouped by utterances based on the similarity, by default. To turn off grouping by utterance, click the <\/span><b>Utterances <\/b><span style=\"font-weight: 400\">header and turn off the <\/span><b>Group by Utterances<\/b><span style=\"font-weight: 400\"> option.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400\">Task Name<\/span><\/td>\n<td><span style=\"font-weight: 400\">The task that is identified for the user utterance. To turn on grouping by task name, click the <\/span><b>Task Name <\/b><span style=\"font-weight: 400\">header and enable the <\/span><b>Group by Task <\/b><span style=\"font-weight: 400\">option.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400\">Failure Point<\/span><\/td>\n<td><span style=\"font-weight: 400\">Nodes or points in the task execution journey where the failure occurred resulting in the task cancellation or user drop. Click an entry to view the complete conversation for that session with markers to identify the intent detection utterance and the failure\/drop-out point. Depending on the task type, clicking Failure Point shows more details.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400\">Type of Issue<\/span><\/td>\n<td>\n<p><span style=\"font-weight: 400\">Shows the reason for failure in case of Task Failure records.<\/span><\/p>\n<p><span style=\"font-weight: 400\">To know the usual type of issues, see <\/span><a href=\"https:\/\/docs.google.com\/document\/d\/1r4NmtMZs4RIHGM3a0gHXm_opHimr29w3RrUnlfBi5v8\/edit#heading=h.edo45rtnd0rs\"><span style=\"font-weight: 400\">Failed Task &#8211; Type of Issues.<\/span><\/a><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400\">UserID<\/span><\/td>\n<td>\n<p><span style=\"font-weight: 400\">The UserID of the end user related to the conversation. You can view the metrics based on either <\/span><b>Kore User id<\/b><span style=\"font-weight: 400\"> or <\/span><b>Channel User Id<\/b><span style=\"font-weight: 400\">.<\/span><\/p>\n<p><span style=\"font-weight: 400\">Channel-specific ids are shown only for the users who have interacted with the VA during the selected period.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400\">Language<\/span><\/td>\n<td><span style=\"font-weight: 400\">The language in which the conversation occurred.<\/span><span style=\"font-weight: 400\"><br \/><\/span><span style=\"font-weight: 400\"><br \/><\/span><span style=\"font-weight: 400\">If it is a multi-lingual VA, you can select specific languages to filter the conversation that occurred in those languages. The page shows the conversations that occurred in all enabled languages by default.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400\">Date &amp; Time<\/span><\/td>\n<td><span style=\"font-weight: 400\">The date and time of the chat. You can sort the data by either <\/span><b>Newest to Oldest<\/b><span style=\"font-weight: 400\">\u00a0or <\/span><b>Oldest to Newest<\/b><span style=\"font-weight: 400\">.<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h2><span class=\"ez-toc-section\" id=\"Performance\"><span style=\"font-weight: 400\">Performance<\/span><\/span><\/h2>\n<p><span style=\"font-weight: 400\">Developers can monitor all the scripts and API services across the VA\u2019s tasks from a single window. The performance tab displays information<\/span><span style=\"font-weight: 400\"> related to the backend performance of the VA. <\/span><span style=\"font-weight: 400\">The platform stores the following meta-information:<\/span><\/p>\n<ul>\n<li style=\"font-weight: 400\"><span style=\"font-weight: 400\">Node name, type, and task name<\/span><\/li>\n<li style=\"font-weight: 400\"><span style=\"font-weight: 400\">Total number of runs<\/span><\/li>\n<li style=\"font-weight: 400\"><span style=\"font-weight: 400\">Success %<\/span><\/li>\n<li style=\"font-weight: 400\"><span style=\"font-weight: 400\">The total number of calls with 200 responses and the total number of calls with a non-200 response. You can view the\u00a0 actual response code from the details page that\u00a0 opens when you click the service row<\/span><\/li>\n<li style=\"font-weight: 400\"><span style=\"font-weight: 400\">Average Response times<\/span><\/li>\n<li style=\"font-weight: 400\"><span style=\"font-weight: 400\">Appropriate alerts if a script or a service is failing consecutively<\/span><\/li>\n<\/ul>\n<p><strong>Description of Performance Fields<\/strong><\/p>\n<p><span style=\"font-weight: 400\">The following table lists the fields on the Performance tab with descriptions:<\/span><\/p>\n<table>\n<thead>\n<tr>\n<th><b>Fields<\/b><\/th>\n<th><b>Description<\/b><\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td><span style=\"font-weight: 400\">Node Name<\/span><\/td>\n<td><span style=\"font-weight: 400\">The name of the service or script or Webhook within the task that got executed in response to the user utterance. To turn on grouping by components to which these scripts or services belong, click the <\/span><b>Node Name <\/b><span style=\"font-weight: 400\">header and turn on the <\/span><b>Group by NodeName <\/b><span style=\"font-weight: 400\">option.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400\">Type<\/span><\/td>\n<td>\n<p><span style=\"font-weight: 400\">Shows whether it is a script or service or Webhook.<\/span><\/p>\n<p><span style=\"font-weight: 400\">Webhook details are included from ver 7.0.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400\">Task Name<\/span><\/td>\n<td><span style=\"font-weight: 400\">The task that is identified for the user utterance. To turn on grouping by task name, click the <\/span><b>Task Name <\/b><span style=\"font-weight: 400\">header and enable the <\/span><b>Group by Task <\/b><span style=\"font-weight: 400\">option.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400\">Total Runs<\/span><\/td>\n<td><span style=\"font-weight: 400\">The total number of times within the date period that the script or service is run for any user utterances.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400\">Success%<\/span><\/td>\n<td><span style=\"font-weight: 400\">The percentage of the service or script runs that got executed successfully.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400\">2XX Responses<\/span><\/td>\n<td><span style=\"font-weight: 400\">The percentage of the service or script runs that returned a 2xx response.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400\">Non 2XX Responses<\/span><\/td>\n<td><span style=\"font-weight: 400\">The percentage of the service or script runs that returned a non-2xx response.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400\">Avg Response Time<\/span><\/td>\n<td>\n<p><span style=\"font-weight: 400\">The average response time of the script or service in the total number of runs.<\/span><\/p>\n<p><span style=\"font-weight: 400\">This can be sorted from <\/span><b>High to Low<\/b><span style=\"font-weight: 400\"> or<\/span><b> Low to High<\/b><span style=\"font-weight: 400\"> under the <\/span><b>Performance <\/b><span style=\"font-weight: 400\">tab.<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h2><span class=\"ez-toc-section\" id=\"Pinned\"><span style=\"font-weight: 400\">Pinned<\/span><\/span><\/h2>\n<p><span style=\"font-weight: 400\">Any records from Identified and Unidentified Intents, Unhandled Utterances, or Failed Tasks tabs that are pinned are displayed in the Pinned tab.\u00a0<\/span><\/p>\n<p><strong>Description of Pinned Fields<\/strong><\/p>\n<p><span style=\"font-weight: 400\">The following table lists the fields on the Pinned tab with descriptions:<\/span><\/p>\n<table>\n<thead>\n<tr>\n<th><b>Fields<\/b><\/th>\n<th><b>Description<\/b><\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td><span style=\"font-weight: 400\">Utterances<\/span><\/td>\n<td><span style=\"font-weight: 400\">The pinned utterances are displayed here. The details in the tab are grouped by utterances based on the similarity, by default. To turn off grouping by utterance, click the <\/span><b>Utterances <\/b><span style=\"font-weight: 400\">header and disable the <\/span><b>Group by Utterances<\/b><span style=\"font-weight: 400\"> option.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400\">Intent<\/span><\/td>\n<td><span style=\"font-weight: 400\">The intent associated with the pinned utterance. The details in the tab can be grouped by Intents. By default, the\u00a0 <\/span><b>Group by Intent <\/b><span style=\"font-weight: 400\">option is turned off. To turn it on, click the <\/span><b>Intent <\/b><span style=\"font-weight: 400\">header and enable the <\/span><b>Group by Intent <\/b><span style=\"font-weight: 400\">option.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400\">Type of Issue<\/span><\/td>\n<td>\n<p><span style=\"font-weight: 400\">Shows the reason for failure in case of Task Failure records.<\/span><\/p>\n<p><span style=\"font-weight: 400\">To know the usual type of issues, see <\/span><a href=\"https:\/\/developer.kore.ai\/v9-3\/docs\/bots\/analyzing-your-bot\/bot-analysis\/#Failed_Task_-_Type_of_Issues\"><span style=\"font-weight: 400\">Failed Task &#8211; Type of Issues<\/span><\/a><span style=\"font-weight: 400\">.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400\">UserID<\/span><\/td>\n<td>\n<p><span style=\"font-weight: 400\">The UserID of the end user related to the conversation. You can view the metrics based on either <\/span><b>Kore User id<\/b><span style=\"font-weight: 400\"> or <\/span><b>Channel User Id<\/b><span style=\"font-weight: 400\">.<\/span><\/p>\n<p><span style=\"font-weight: 400\">Channel-specific ids are shown only for the users who have interacted with the VA during the selected period.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400\">Language<\/span><\/td>\n<td><span style=\"font-weight: 400\">The language in which the conversation occurred.<\/span><span style=\"font-weight: 400\"><br \/><\/span><span style=\"font-weight: 400\"><br \/><\/span><span style=\"font-weight: 400\">If it is a multi-lingual VA, you can select specific languages to filter the conversation that occurred in those languages. The page shows the conversations that occurred in all enabled languages by default.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400\">Date &amp; Time<\/span><\/td>\n<td><span style=\"font-weight: 400\">The date and time of the chat. You can sort the data by either <\/span><b>Newest to Oldest <\/b><span style=\"font-weight: 400\">or <\/span><b>Oldest to Newest<\/b><span style=\"font-weight: 400\">.<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h2><span class=\"ez-toc-section\" id=\"Debug_Log\"><span style=\"font-weight: 400\">Debug Log<\/span><\/span><\/h2>\n<p><span style=\"font-weight: 400\">Any custom debug statements that you entered in the Script node using the script <\/span><span style=\"font-weight: 400\"><code>koreDebugger.log(\"&lt;debug statement&gt;\")<\/code><\/span><span style=\"font-weight: 400\">are displayed on this tab. Debug statements should be in a string format. See the following table <\/span><span style=\"font-weight: 400\">to know more.<\/span><\/p>\n<p><span style=\"font-weight: 400\">The logs include the user conversation from across all channels. You can use them for bot analysis especially in case of failures during user interaction.<\/span><\/p>\n<p><span style=\"font-weight: 400\">The details include:<\/span><\/p>\n<ul>\n<li style=\"font-weight: 400\"><span style=\"font-weight: 400\">The actual statement that you have defined at the time of Bot definition.<\/span><\/li>\n<li style=\"font-weight: 400\"><span style=\"font-weight: 400\">Date and time of logging<\/span><\/li>\n<li style=\"font-weight: 400\"><span style=\"font-weight: 400\">Channel<\/span><\/li>\n<li style=\"font-weight: 400\"><span style=\"font-weight: 400\">User ID (along with channel-specific id)<\/span><\/li>\n<li style=\"font-weight: 400\"><span style=\"font-weight: 400\">Language of interaction<\/span><\/li>\n<li style=\"font-weight: 400\"><span style=\"font-weight: 400\">Task name if available<\/span><\/li>\n<\/ul>\n<p><span style=\"font-weight: 400\">You can also view the details of the chat history associated with the session. To view more details, follow the below steps:<\/span><\/p>\n<ol>\n<li style=\"font-weight: 400\"><span style=\"font-weight: 400\">Click a logged record.<\/span><\/li>\n<li style=\"font-weight: 400\"><span style=\"font-weight: 400\">On the corresponding window, you can find the <\/span><b>Details<\/b><span style=\"font-weight: 400\"> and <\/span><b>Chat History<\/b><span style=\"font-weight: 400\"> tabs.<\/span><\/li>\n<li style=\"font-weight: 400\"><span style=\"font-weight: 400\">Under the Details tab, you can find the <\/span><i><span style=\"font-weight: 400\">task name<\/span><\/i><span style=\"font-weight: 400\">, <\/span><i><span style=\"font-weight: 400\">channel<\/span><\/i><span style=\"font-weight: 400\">, <\/span><i><span style=\"font-weight: 400\">language<\/span><\/i><span style=\"font-weight: 400\">, and <\/span><i><span style=\"font-weight: 400\">flow<\/span><\/i><span style=\"font-weight: 400\">.<\/span><\/li>\n<li style=\"font-weight: 400\"><span style=\"font-weight: 400\">Click the <\/span><b>Chat History<\/b><span style=\"font-weight: 400\"> tab. You can find the chat transcript where the log is recorded.<\/span>\n<ul>\n<li style=\"font-weight: 400\"><span style=\"font-weight: 400\">If the debug log is generated from a VA message, you are navigated to that specific message in the chat transcript.<\/span><\/li>\n<li style=\"font-weight: 400\"><span style=\"font-weight: 400\">If the debug log is not part of the VA message, you are navigated to the latest message added before the debug statement.<\/span><\/li>\n<\/ul>\n<\/li>\n<\/ol>\n<p><span style=\"font-weight: 400\">For universal VAs, the debug statements from the universal and linked assistants are included in the logs. The debug logs also include the error messages related to BotKit, for example, when the platform could not reach the BotKit or when the BotKit did not acknowledge the message sent by the platform. The message includes details like the<\/span> <code><i><span style=\"font-weight: 400\">&lt;endpoint&gt;<\/span><\/i><span style=\"font-weight: 400\">, <\/span><i><span style=\"font-weight: 400\">&lt;error code&gt;<\/span><\/i><span style=\"font-weight: 400\">,<\/span><\/code> and <code><i><span style=\"font-weight: 400\">&lt;response time&gt;<\/span><\/i><i><span style=\"font-weight: 400\">.<\/span><\/i><\/code><\/p>\n<p><strong>Description of Debug Log Fields<\/strong><\/p>\n<p><span style=\"font-weight: 400\">The following table lists the fields on the Debug Log tab with descriptions:<\/span><\/p>\n<table>\n<thead>\n<tr>\n<th><b>Fields<\/b><\/th>\n<th><b>Description<\/b><\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td><span style=\"font-weight: 400\">Log<\/span><\/td>\n<td><span style=\"font-weight: 400\">Description of the debug log. For example, <\/span><span style=\"font-weight: 400\">getIndex is not defined.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400\">Task Name<\/span><\/td>\n<td><span style=\"font-weight: 400\">The task that is identified for the user utterance. To turn on grouping by task name, click the <\/span><b>Task Name <\/b><span style=\"font-weight: 400\">header and enable the <\/span><b>Group by Task <\/b><span style=\"font-weight: 400\">option.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400\">Debug Point\u00a0<\/span><\/td>\n<td><span style=\"font-weight: 400\">The point or a node in the conversation where the error is identified. <\/span><span style=\"font-weight: 400\">For example, <\/span><span style=\"font-weight: 400\">buildDataForCarousel<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400\">Channel<\/span><\/td>\n<td><span style=\"font-weight: 400\">Specific channel where the conversation occurred.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400\">Language<\/span><\/td>\n<td><span style=\"font-weight: 400\">The language in which the conversation occurred.<\/span><span style=\"font-weight: 400\"><br \/><\/span><span style=\"font-weight: 400\"><br \/><\/span><span style=\"font-weight: 400\">If it is a multi-lingual VA, you can select specific languages to filter the conversation that occurred in those languages. The page shows the conversations that occurred in all enabled languages by default.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400\">UserID<\/span><\/td>\n<td>\n<p><span style=\"font-weight: 400\">The UserID of the end user related to the conversation. You can view the metrics based on either <\/span><b>Kore User id<\/b><span style=\"font-weight: 400\"> or <\/span><b>Channel User Id<\/b><span style=\"font-weight: 400\">.<\/span><\/p>\n<p><span style=\"font-weight: 400\">Channel-specific ids are shown only for the users who have interacted with the VA during the selected period.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400\">Date &amp; Time<\/span><\/td>\n<td><span style=\"font-weight: 400\">The date and time of the chat. You can sort the data by either <\/span><b>Newest to Oldest<\/b><span style=\"font-weight: 400\">\u00a0or <\/span><b>Oldest to Newest<\/b><span style=\"font-weight: 400\">.<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h2><span class=\"ez-toc-section\" id=\"Storage_Limitations\"><span style=\"font-weight: 400\">Storage Limitations<\/span><\/span><\/h2>\n<p><span style=\"font-weight: 400\">The platform imposes restrictions on the number of log statements retained per VA. The limit is a combination of volume and period:<\/span><\/p>\n<ul>\n<li style=\"font-weight: 400\"><span style=\"font-weight: 400\">Only the latest 700 statements per VA are stored.<\/span><\/li>\n<li style=\"font-weight: 400\"><span style=\"font-weight: 400\">Statements older than 7 days are removed.<\/span><\/li>\n<\/ul>\n<h1><span class=\"ez-toc-section\" id=\"NLP_Insights_Analysis\">NLP Insights Analysis<\/span><\/h1>\n<p>The following sections describe more about the options available on NLP Insights page and the analysis of the records captured here.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"Features\"><span style=\"font-weight: 400\">Features<\/span><\/span><\/h2>\n<p><span style=\"font-weight: 400\">The following list details the features available in NLP Insights for <\/span><a href=\"https:\/\/developer.kore.ai\/v9-3\/docs\/bots\/analyzing-your-bot\/bot-analysis\/#Intent_Found\"><span style=\"font-weight: 400\">Intent Found<\/span><\/a><span style=\"font-weight: 400\">, <\/span><a href=\"https:\/\/developer.kore.ai\/v9-3\/docs\/bots\/analyzing-your-bot\/bot-analysis\/#Intent_Not_Found\"><span style=\"font-weight: 400\">Intent Not Found<\/span><\/a><span style=\"font-weight: 400\">, <\/span><a href=\"https:\/\/developer.kore.ai\/v9-3\/docs\/bots\/analyzing-your-bot\/bot-analysis\/#Unhandled_Utterances\"><span style=\"font-weight: 400\">Unhandled Utterances<\/span><\/a><span style=\"font-weight: 400\">, and <\/span><a href=\"https:\/\/developer.kore.ai\/v9-3\/docs\/bots\/analyzing-your-bot\/bot-analysis\/#Failed_Task\"><span style=\"font-weight: 400\">Failed Task<\/span><\/a><span style=\"font-weight: 400\">.<\/span><\/p>\n<ul>\n<li style=\"font-weight: 400\"><span style=\"font-weight: 400\">You can filter the information based on various criteria such as User Utterances, Intent, user id (Kore user id or channel-specific unique id), date-period, the channel of use, language, etc. You can also filter records based on multiple custom tags. See <\/span><a href=\"https:\/\/developer.kore.ai\/v9-3\/docs\/bots\/analyzing-your-bot\/bot-analysis\/#Filter_Criteria\"><span style=\"font-weight: 400\">Filter Criteria<\/span><\/a><span style=\"font-weight: 400\"> to know more.<\/span><\/li>\n<li style=\"font-weight: 400\"><span style=\"font-weight: 400\">Complete meta information is stored for later analysis, including the original user utterance, the channel of communication, entities extracted (if any), custom tags applied, detailed NLP analysis with scores returned from each engine, and the ranking and resolver scores.<\/span><\/li>\n<li style=\"font-weight: 400\"><span style=\"font-weight: 400\">Ability to view the chat transcript to the point of the user utterance. This also gives the option to view the user profile and the details for that user\u2019s conversation sessions.<\/span><\/li>\n<li style=\"font-weight: 400\"><span style=\"font-weight: 400\">You have an option to train the utterance.\u00a0 The utterance will be marked once trained.<\/span><\/li>\n<li style=\"font-weight: 400\"><span style=\"font-weight: 400\">Any important record you want to mark, track later, or both can be pinned. They l appear on\u00a0 the <\/span><b>Pinned<\/b><span style=\"font-weight: 400\"> tab.<\/span><\/li>\n<li style=\"font-weight: 400\"><span style=\"font-weight: 400\">Sorting feature is available for Date and Time (Oldest to Newest, Newest to Oldest). You can export the insights data as a CSV file.<\/span><\/li>\n<\/ul>\n<p><a ref=\"magnificPopup\" href=\"https:\/\/kore-wordpress.s3.us-east-2.amazonaws.com\/developer.kore.ai\/v9-3\/wp-content\/uploads\/sites\/29\/20220819072645\/Date-2.png\"><img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/kore-wordpress.s3.us-east-2.amazonaws.com\/developer.kore.ai\/v9-3\/wp-content\/uploads\/sites\/29\/20220819072645\/Date-2.png\" alt=\"\" width=\"640\" height=\"335\" class=\"alignnone size-large wp-image-44107\" srcset=\"https:\/\/kore-wordpress.s3.us-east-2.amazonaws.com\/developer.kore.ai\/v9-3\/wp-content\/uploads\/sites\/29\/20220819072645\/Date-2.png 1629w, https:\/\/kore-wordpress.s3.us-east-2.amazonaws.com\/developer.kore.ai\/v9-3\/wp-content\/uploads\/sites\/29\/20220819072645\/Date-2-300x157.png 300w, https:\/\/kore-wordpress.s3.us-east-2.amazonaws.com\/developer.kore.ai\/v9-3\/wp-content\/uploads\/sites\/29\/20220819072645\/Date-2-1024x536.png 1024w\" sizes=\"auto, (max-width: 640px) 100vw, 640px\" \/><\/a><\/p>\n<div class=\"alert alert-info\"><b>Note:<\/b> <span style=\"font-weight: 400\">The NLP Insights page shows the conversations from the last 24 hours by default. You can filter the insights for a selected period \u2013 use the Date drop-down to select 24 hours, last 7 days, or a custom period.<\/span><\/div>\n<h2><span class=\"ez-toc-section\" id=\"Fields_Matrix\"><span style=\"font-weight: 400\">Fields Matrix<\/span><\/span><\/h2>\n<p><span style=\"font-weight: 400\">The following matrix shows the availability of fields on each tab of NLP Insights:<\/span><\/p>\n<table>\n<thead>\n<tr>\n<th><b>Fields<\/b><\/th>\n<th><b>Intent Found<\/b><\/th>\n<th><b>Intent Not Found<\/b><\/th>\n<th><b>Unhandled Utterances<\/b><\/th>\n<th><b>Failed Tasks<\/b><\/th>\n<th><b>Performance<\/b><\/th>\n<th><b>Pinned<\/b><\/th>\n<th><b>Debug Log<\/b><\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td><span style=\"font-weight: 400\">Utterances<\/span><\/td>\n<td><span style=\"font-weight: 400\">\u2714<\/span><\/td>\n<td><span style=\"font-weight: 400\">\u2714<\/span><\/td>\n<td><span style=\"font-weight: 400\">\u2714<\/span><\/td>\n<td><span style=\"font-weight: 400\">\u2714<\/span><\/td>\n<td><span style=\"font-weight: 400\">X<\/span><\/td>\n<td><span style=\"font-weight: 400\">\u2714<\/span><\/td>\n<td><span style=\"font-weight: 400\">X<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400\">Intent<\/span><\/td>\n<td><span style=\"font-weight: 400\">\u2714<\/span><\/td>\n<td><span style=\"font-weight: 400\">X<\/span><\/td>\n<td><span style=\"font-weight: 400\">X<\/span><\/td>\n<td><span style=\"font-weight: 400\">X<\/span><\/td>\n<td><span style=\"font-weight: 400\">X<\/span><\/td>\n<td><span style=\"font-weight: 400\">\u2714<\/span><\/td>\n<td><span style=\"font-weight: 400\">X<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400\">Traits<\/span><\/td>\n<td><span style=\"font-weight: 400\">\u2714<\/span><\/td>\n<td><span style=\"font-weight: 400\">\u2714<\/span><\/td>\n<td><span style=\"font-weight: 400\">\u2714<\/span><\/td>\n<td><span style=\"font-weight: 400\">X<\/span><\/td>\n<td><span style=\"font-weight: 400\">X<\/span><\/td>\n<td><span style=\"font-weight: 400\">X<\/span><\/td>\n<td><span style=\"font-weight: 400\">X<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400\">UserID<\/span><\/td>\n<td><span style=\"font-weight: 400\">\u2714<\/span><\/td>\n<td><span style=\"font-weight: 400\">\u2714<\/span><\/td>\n<td><span style=\"font-weight: 400\">\u2714<\/span><\/td>\n<td><span style=\"font-weight: 400\">\u2714<\/span><\/td>\n<td><span style=\"font-weight: 400\">X<\/span><\/td>\n<td><span style=\"font-weight: 400\">\u2714<\/span><\/td>\n<td><span style=\"font-weight: 400\">\u2714<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400\">Language<\/span><\/td>\n<td><span style=\"font-weight: 400\">\u2714<\/span><\/td>\n<td><span style=\"font-weight: 400\">\u2714<\/span><\/td>\n<td><span style=\"font-weight: 400\">\u2714<\/span><\/td>\n<td><span style=\"font-weight: 400\">\u2714<\/span><\/td>\n<td><span style=\"font-weight: 400\">X<\/span><\/td>\n<td><span style=\"font-weight: 400\">\u2714<\/span><\/td>\n<td><span style=\"font-weight: 400\">\u2714<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400\">Date &amp; Time<\/span><\/td>\n<td><span style=\"font-weight: 400\">\u2714<\/span><\/td>\n<td><span style=\"font-weight: 400\">\u2714<\/span><\/td>\n<td><span style=\"font-weight: 400\">\u2714<\/span><\/td>\n<td><span style=\"font-weight: 400\">\u2714<\/span><\/td>\n<td><span style=\"font-weight: 400\">X<\/span><\/td>\n<td><span style=\"font-weight: 400\">\u2714<\/span><\/td>\n<td><span style=\"font-weight: 400\">\u2714<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400\">Prompt Type<\/span><\/td>\n<td><span style=\"font-weight: 400\">X<\/span><\/td>\n<td><span style=\"font-weight: 400\">X<\/span><\/td>\n<td><span style=\"font-weight: 400\">\u2714<\/span><\/td>\n<td><span style=\"font-weight: 400\">X<\/span><\/td>\n<td><span style=\"font-weight: 400\">X<\/span><\/td>\n<td><span style=\"font-weight: 400\">X<\/span><\/td>\n<td><span style=\"font-weight: 400\">X<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400\">Task Name<\/span><\/td>\n<td><span style=\"font-weight: 400\">X<\/span><\/td>\n<td><span style=\"font-weight: 400\">X<\/span><\/td>\n<td><span style=\"font-weight: 400\">\u2714<\/span><\/td>\n<td><span style=\"font-weight: 400\">\u2714<\/span><\/td>\n<td><span style=\"font-weight: 400\">\u2714<\/span><\/td>\n<td><span style=\"font-weight: 400\">X<\/span><\/td>\n<td><span style=\"font-weight: 400\">\u2714<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400\">Node Name<\/span><\/td>\n<td><span style=\"font-weight: 400\">X<\/span><\/td>\n<td><span style=\"font-weight: 400\">X<\/span><\/td>\n<td><span style=\"font-weight: 400\">\u2714<\/span><\/td>\n<td><span style=\"font-weight: 400\">X<\/span><\/td>\n<td><span style=\"font-weight: 400\">\u2714<\/span><\/td>\n<td><span style=\"font-weight: 400\">X<\/span><\/td>\n<td><span style=\"font-weight: 400\">X<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400\">Failure Point<\/span><\/td>\n<td><span style=\"font-weight: 400\">X<\/span><\/td>\n<td><span style=\"font-weight: 400\">X<\/span><\/td>\n<td><span style=\"font-weight: 400\">X<\/span><\/td>\n<td><span style=\"font-weight: 400\">\u2714<\/span><\/td>\n<td><span style=\"font-weight: 400\">X<\/span><\/td>\n<td><span style=\"font-weight: 400\">X<\/span><\/td>\n<td><span style=\"font-weight: 400\">X<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400\">Type of Issue<\/span><\/td>\n<td><span style=\"font-weight: 400\">X<\/span><\/td>\n<td><span style=\"font-weight: 400\">X<\/span><\/td>\n<td><span style=\"font-weight: 400\">X<\/span><\/td>\n<td><span style=\"font-weight: 400\">\u2714<\/span><\/td>\n<td><span style=\"font-weight: 400\">X<\/span><\/td>\n<td><span style=\"font-weight: 400\">\u2714<\/span><\/td>\n<td><span style=\"font-weight: 400\">X<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400\">Type<\/span><\/td>\n<td><span style=\"font-weight: 400\">X<\/span><\/td>\n<td><span style=\"font-weight: 400\">X<\/span><\/td>\n<td><span style=\"font-weight: 400\">X<\/span><\/td>\n<td><span style=\"font-weight: 400\">X<\/span><\/td>\n<td><span style=\"font-weight: 400\">\u2714<\/span><\/td>\n<td><span style=\"font-weight: 400\">X<\/span><\/td>\n<td><span style=\"font-weight: 400\">X<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400\">Total Runs<\/span><\/td>\n<td><span style=\"font-weight: 400\">X<\/span><\/td>\n<td><span style=\"font-weight: 400\">X<\/span><\/td>\n<td><span style=\"font-weight: 400\">X<\/span><\/td>\n<td><span style=\"font-weight: 400\">X<\/span><\/td>\n<td><span style=\"font-weight: 400\">\u2714<\/span><\/td>\n<td><span style=\"font-weight: 400\">X<\/span><\/td>\n<td><span style=\"font-weight: 400\">X<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400\">Success%<\/span><\/td>\n<td><span style=\"font-weight: 400\">X<\/span><\/td>\n<td><span style=\"font-weight: 400\">X<\/span><\/td>\n<td><span style=\"font-weight: 400\">X<\/span><\/td>\n<td><span style=\"font-weight: 400\">X<\/span><\/td>\n<td><span style=\"font-weight: 400\">\u2714<\/span><\/td>\n<td><span style=\"font-weight: 400\">X<\/span><\/td>\n<td><span style=\"font-weight: 400\">X<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400\">2XX Responses<\/span><\/td>\n<td><span style=\"font-weight: 400\">X<\/span><\/td>\n<td><span style=\"font-weight: 400\">X<\/span><\/td>\n<td><span style=\"font-weight: 400\">X<\/span><\/td>\n<td><span style=\"font-weight: 400\">X<\/span><\/td>\n<td><span style=\"font-weight: 400\">\u2714<\/span><\/td>\n<td><span style=\"font-weight: 400\">X<\/span><\/td>\n<td><span style=\"font-weight: 400\">X<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400\">Non 2XX Responses<\/span><\/td>\n<td><span style=\"font-weight: 400\">X<\/span><\/td>\n<td><span style=\"font-weight: 400\">X<\/span><\/td>\n<td><span style=\"font-weight: 400\">X<\/span><\/td>\n<td><span style=\"font-weight: 400\">X<\/span><\/td>\n<td><span style=\"font-weight: 400\">\u2714<\/span><\/td>\n<td><span style=\"font-weight: 400\">X<\/span><\/td>\n<td><span style=\"font-weight: 400\">X<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400\">Avg Response Time<\/span><\/td>\n<td><span style=\"font-weight: 400\">X<\/span><\/td>\n<td><span style=\"font-weight: 400\">X<\/span><\/td>\n<td><span style=\"font-weight: 400\">X<\/span><\/td>\n<td><span style=\"font-weight: 400\">X<\/span><\/td>\n<td><span style=\"font-weight: 400\">\u2714<\/span><\/td>\n<td><span style=\"font-weight: 400\">X<\/span><\/td>\n<td><span style=\"font-weight: 400\">X<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400\">Log<\/span><\/td>\n<td><span style=\"font-weight: 400\">X<\/span><\/td>\n<td><span style=\"font-weight: 400\">X<\/span><\/td>\n<td><span style=\"font-weight: 400\">X<\/span><\/td>\n<td><span style=\"font-weight: 400\">X<\/span><\/td>\n<td><span style=\"font-weight: 400\">X<\/span><\/td>\n<td><span style=\"font-weight: 400\">X<\/span><\/td>\n<td><span style=\"font-weight: 400\">\u2714<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400\">Debug Point<\/span><\/td>\n<td><span style=\"font-weight: 400\">X<\/span><\/td>\n<td><span style=\"font-weight: 400\">X<\/span><\/td>\n<td><span style=\"font-weight: 400\">X<\/span><\/td>\n<td><span style=\"font-weight: 400\">X<\/span><\/td>\n<td><span style=\"font-weight: 400\">X<\/span><\/td>\n<td><span style=\"font-weight: 400\">X<\/span><\/td>\n<td><span style=\"font-weight: 400\">\u2714<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400\">Channel<\/span><\/td>\n<td><span style=\"font-weight: 400\">X<\/span><\/td>\n<td><span style=\"font-weight: 400\">X<\/span><\/td>\n<td><span style=\"font-weight: 400\">X<\/span><\/td>\n<td><span style=\"font-weight: 400\">X<\/span><\/td>\n<td><span style=\"font-weight: 400\">X<\/span><\/td>\n<td><span style=\"font-weight: 400\">X<\/span><\/td>\n<td><span style=\"font-weight: 400\">\u2714<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h2><span class=\"ez-toc-section\" id=\"Filter_Criteria\"><span style=\"font-size: 32px\">Filter Criteria<\/span><\/span><\/h2>\n<p><span style=\"font-weight: 400\">You can filter the information on the Insights page using various filters. You can save the entered filter criteria and set it as the default filter using <\/span><b>Save as Default Filter<\/b><span style=\"font-weight: 400\">.<\/span><\/p>\n<p><span style=\"font-weight: 400\">The filter criteria differ slightly between different tabs. The relevant filters are applied when you switch between the tabs on the Insights Page. See <\/span><a href=\"https:\/\/developer.kore.ai\/v9-3\/docs\/bots\/analyzing-your-bot\/dashboard-filter-criteria\/\"><span style=\"font-weight: 400\">Dashboard Filter Criteria<\/span><\/a><span style=\"font-weight: 400\"> to know more details.<\/span><\/p>\n<h2><span class=\"ez-toc-section\" id=\"Detailed_View\"><span style=\"font-weight: 400\">Detailed View<\/span><\/span><\/h2>\n<p><span style=\"font-weight: 400\">For all the user utterances listed on\u00a0 the various tabs such as Intent Found, Intent Not Found, Unhandled Utterances, etc., you can open more details of the user session by clicking the respective record. The record shows the information on the following sub-tabs: Details, NLP Analysis, and Chat History.<\/span><\/p>\n<h3><span class=\"ez-toc-section\" id=\"Details\"><span style=\"font-weight: 400\">Details<\/span><\/span><\/h3>\n<p><span style=\"font-weight: 400\">The Details tab shows the basic details of the session along with a JSON file that includes the NLP analysis for the conversation.<\/span><\/p>\n<p><span style=\"font-weight: 400\"><a ref=\"magnificPopup\" href=\"https:\/\/kore-wordpress.s3.us-east-2.amazonaws.com\/developer.kore.ai\/v9-3\/wp-content\/uploads\/sites\/29\/20220901080909\/Details-1.png\"><img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/kore-wordpress.s3.us-east-2.amazonaws.com\/developer.kore.ai\/v9-3\/wp-content\/uploads\/sites\/29\/20220901080909\/Details-1.png\" alt=\"\" width=\"740\" height=\"286\" class=\"alignnone size-medium wp-image-44204\" \/><\/a><\/span><\/p>\n<h3><span class=\"ez-toc-section\" id=\"NLP_Analysis\"><span style=\"font-weight: 400\">NLP Analysis<\/span><\/span><\/h3>\n<p><span style=\"font-weight: 400\">This tab provides a visual representation of the NLP Analysis, including intent scoring and selection.\u00a0 See <a href=\"https:\/\/developer.kore.ai\/v9-3\/docs\/bots\/test-your-bot\/testing-your-bot-with-nlp\/\">Testing and Training a Virtual Assistant<\/a> and <a href=\"https:\/\/developer.kore.ai\/v9-3\/docs\/bots\/nlp\/nlp-detection\/\">Ranking and Resolver<\/a> for more information.<br \/><\/span><\/p>\n<h3><span style=\"font-weight: 400\"><a ref=\"magnificPopup\" href=\"https:\/\/kore-wordpress.s3.us-east-2.amazonaws.com\/developer.kore.ai\/v9-3\/wp-content\/uploads\/sites\/29\/20220901082250\/NLP-Analysis-2.png\"><img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/kore-wordpress.s3.us-east-2.amazonaws.com\/developer.kore.ai\/v9-3\/wp-content\/uploads\/sites\/29\/20220901082250\/NLP-Analysis-2.png\" alt=\"\" width=\"400\" height=\"300\" class=\"alignnone size-medium wp-image-44208\" \/><\/a><\/span><\/h3>\n<h3><span class=\"ez-toc-section\" id=\"Chat_History\"><span style=\"font-weight: 400\">Chat History<\/span><\/span><\/h3>\n<p><span style=\"font-weight: 400\">On the Chat History tab, you can access the exact message or conversation for which the record is logged. It shows the entire chat history of the user session.<\/span><\/p>\n<p><span style=\"font-weight: 400\"><a ref=\"magnificPopup\" href=\"https:\/\/kore-wordpress.s3.us-east-2.amazonaws.com\/developer.kore.ai\/v9-3\/wp-content\/uploads\/sites\/29\/20220901082527\/ChatHist.png\"><img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/kore-wordpress.s3.us-east-2.amazonaws.com\/developer.kore.ai\/v9-3\/wp-content\/uploads\/sites\/29\/20220901082527\/ChatHist.png\" alt=\"\" width=\"456\" height=\"300\" class=\"alignnone size-medium wp-image-44211\" \/><\/a><\/span><\/p>\n<p><span style=\"font-weight: 400\">Chat History provides visibility into the user information by capturing the following details:<\/span><\/p>\n<ul>\n<li style=\"font-weight: 400\"><b>User Profile<\/b><span style=\"font-weight: 400\">: Provides a 360-degree view of the user and their usage metrics.<\/span><\/li>\n<li style=\"font-weight: 400\"><b>User Conversation Sessions<\/b><span style=\"font-weight: 400\">: Lists all the sessions of the user in the given period with the selected utterance section expanded.<\/span><\/li>\n<li style=\"font-weight: 400\"><b>Go to Selected Utterance<\/b><span style=\"font-weight: 400\">: When you click this icon, the selected utterance is highlighted in orange (see the preceding screenshot).<\/span><\/li>\n<\/ul>\n<p><span style=\"font-weight: 400\">The following user information details are displayed on the<\/span><b> Chat History <\/b><span style=\"font-weight: 400\">tab:<\/span><\/p>\n<table>\n<tbody>\n<tr>\n<th><b>Functionality<\/b><\/th>\n<th><b>Attribute<\/b><\/th>\n<th><b>Description<\/b><\/th>\n<\/tr>\n<tr>\n<td rowspan=\"14\"><span style=\"font-weight: 400\">User Profile<\/span><\/td>\n<td><span style=\"font-weight: 400\">Kore User ID<\/span><\/td>\n<td><span style=\"font-weight: 400\">User id assigned by the platform<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400\">Channel Data<\/span><\/td>\n<td><span style=\"font-weight: 400\">Data received from the channel, that is the information available in the User Context.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400\">User Meta Tags<\/span><\/td>\n<td><span style=\"font-weight: 400\">The total number of meta tags associated with the user and key-value pairs for the most recent ones.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400\">Latest Interaction<\/span><\/td>\n<td><span style=\"font-weight: 400\">Last time the user interacted with the VA.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400\">Total Conversation Sessions<\/span><\/td>\n<td><span style=\"font-weight: 400\">The total number of interactive and non-interactive sessions registered by the user from the beginning of time.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400\">Total Conversation Sessions in the Last 30 Days<\/span><\/td>\n<td><span style=\"font-weight: 400\">The total number of interactive and non-interactive sessions registered by the user in the last 30 days.<\/span><\/td>\n<\/tr>\n<tr>\n<td colspan=\"2\"><b>*The next few attributes are not displayed if there is no interaction by the user in the last 30 days<\/b><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400\">Last 30 Days\u2019 Intent Detection Rate<\/span><\/td>\n<td><span style=\"font-weight: 400\">(Total identified intents \/ (Total identified intents + unidentified utterances)) * 100 for the utterances over the last 30 days<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400\">Intents Requested<\/span><\/td>\n<td><span style=\"font-weight: 400\">Total identified intents + unidentified utterances<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400\">Intents Identified<\/span><\/td>\n<td><span style=\"font-weight: 400\">Total intents identified<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400\">Last 30 Days Goal Completion Rate<\/span><\/td>\n<td><span style=\"font-weight: 400\">(Tasks success tasks \/ (Total success tasks + total failed tasks) ) * 100 for the tasks over the last 30 days<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400\">Tasks Initiated<\/span><\/td>\n<td><span style=\"font-weight: 400\">Total success tasks + total failed tasks<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400\">Tasks Completed<\/span><\/td>\n<td><span style=\"font-weight: 400\">Tasks successfully completed<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400\">Recent Conversation Flows<\/span><\/td>\n<td><span style=\"font-weight: 400\">Top 10 popular conversation flows executed by the user in the last 30 days. Popular flows are determined by the number of instances, for which the conversation flow is executed.<\/span><\/td>\n<\/tr>\n<tr>\n<td rowspan=\"16\"><span style=\"font-weight: 400\">User Conversation Sessions<\/span><\/td>\n<td colspan=\"2\"><b>Session Attributes<\/b><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400\">Session Start<\/span><\/td>\n<td><span style=\"font-weight: 400\">Session start date and time.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400\">Session End<\/span><\/td>\n<td><span style=\"font-weight: 400\">Session end date and time.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400\">Channel<\/span><\/td>\n<td><span style=\"font-weight: 400\">Channel in which the session is initiated.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400\">Agent Transfer Tag<\/span><\/td>\n<td><span style=\"font-weight: 400\">The session where the user is transferred to an agent. Sessions should be considered even if the user returns to the VA.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400\">Drop Off Tag<\/span><\/td>\n<td><span style=\"font-weight: 400\">The session where the user dropped off.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400\">Total Success Tasks<\/span><\/td>\n<td><span style=\"font-weight: 400\">Count of tasks successfully completed in the session.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400\">Total Failed Tasks<\/span><\/td>\n<td><span style=\"font-weight: 400\">Count of tasks failed in the session.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400\">Intents Identified<\/span><\/td>\n<td><span style=\"font-weight: 400\">Count of intents successfully identified in the session.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400\">Intents Unidentified<\/span><\/td>\n<td><span style=\"font-weight: 400\">Count of intents unidentified in the session and list of unidentified intents.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400\">Conversation Path<\/span><\/td>\n<td><span style=\"font-weight: 400\">The series of tasks initiated by the user in the session.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400\">Session Meta Tags<\/span><\/td>\n<td><span style=\"font-weight: 400\">Count of the session meta tags used with the details of the most recent custom meta tags displayed.<\/span><\/td>\n<\/tr>\n<tr>\n<td colspan=\"2\"><b>Conversation Transcript<\/b><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400\">Message Meta Tags<\/span><\/td>\n<td><span style=\"font-weight: 400\">The chat transcript is annotated with message tags for messages with meta-tags associated with them.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400\">Agent Transfer<\/span><\/td>\n<td><span style=\"font-weight: 400\">Indicates the point of agent transfer at the last message before transfer.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400\">Drop Off<\/span><\/td>\n<td><span style=\"font-weight: 400\">Indicate the point of drop off at the last message before dropping off.<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p><strong>Advanced Performance Details<\/strong><\/p>\n<p><span style=\"font-weight: 400\">Clicking a service or script or WebHook name opens the advanced details dialog for the service, which lists each instance of its run along with separate tabs for successful and failed runs. Analyzing the average response time of different runs gives you insights into any aberrations in the service or script execution. Click any row to open the JSON response associated with the service or script run.<\/span><\/p>\n<h2><span class=\"ez-toc-section\" id=\"Train_the_Virtual_Assistant\"><span style=\"font-weight: 400\">Train the Virtual Assistant<\/span><\/span><\/h2>\n<p><span style=\"font-weight: 400\">You can train the specific intents and utterances from the Intent Found, Intent Not Found, and Unhandled Utterances tabs. To do so, hover over a row in any of these tabs, and click the <\/span><b>Train <\/b><span style=\"font-weight: 400\">icon. It opens the Test &amp; Train page, where you can train the Virtual Assistant. For more information, see\u00a0 <\/span><a href=\"https:\/\/developer.kore.ai\/v9-3\/docs\/bots\/test-your-bot\/testing-your-bot-with-nlp\/\"><span style=\"font-weight: 400\">Testing and Training a Virtual Assistant<\/span><\/a><span style=\"font-weight: 400\">.<\/span><\/p>\n<h2><span class=\"ez-toc-section\" id=\"Data_Export\"><span style=\"font-weight: 400\">Data Export<\/span><\/span><\/h2>\n<p><span style=\"font-weight: 400\">You can export the data present on the NLP Insights page to a CSV file, by clicking the Export icon on the top right corner of the page.<\/span><\/p>\n<p><a ref=\"magnificPopup\" href=\"https:\/\/kore-wordpress.s3.us-east-2.amazonaws.com\/developer.kore.ai\/v9-3\/wp-content\/uploads\/sites\/29\/20220818081855\/Export-2.png\"><span style=\"font-weight: 400\"><\/span><img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/kore-wordpress.s3.us-east-2.amazonaws.com\/developer.kore.ai\/v9-3\/wp-content\/uploads\/sites\/29\/20220818081855\/Export-2.png\" alt=\"\" width=\"640\" height=\"219\" class=\"alignnone size-large wp-image-44085\" srcset=\"https:\/\/kore-wordpress.s3.us-east-2.amazonaws.com\/developer.kore.ai\/v9-3\/wp-content\/uploads\/sites\/29\/20220818081855\/Export-2.png 1578w, https:\/\/kore-wordpress.s3.us-east-2.amazonaws.com\/developer.kore.ai\/v9-3\/wp-content\/uploads\/sites\/29\/20220818081855\/Export-2-300x103.png 300w, https:\/\/kore-wordpress.s3.us-east-2.amazonaws.com\/developer.kore.ai\/v9-3\/wp-content\/uploads\/sites\/29\/20220818081855\/Export-2-1024x350.png 1024w\" sizes=\"auto, (max-width: 640px) 100vw, 640px\" \/><\/a><\/p>\n<p><span style=\"font-weight: 400\">Once you click the icon, the export process starts, and you can see the progress in the Status Tracker dock. The export file is downloaded to your local <\/span><b>Downloads<\/b><span style=\"font-weight: 400\"> folder. The downloaded file has the information specific to the selected tab and the detailed analysis based on the selected filters.<\/span><\/p>\n<p><span style=\"font-weight: 400\">These records also include the Meta Tag information.<\/span><\/p>\n<div class=\"w-separator size_small with_line width_default thick_1 style_solid color_border align_center\"><div class=\"w-separator-h\"><\/div><\/div>\n<section class=\"l-section wpb_row height_auto\"><div class=\"l-section-h i-cf\"><div class=\"g-cols vc_row type_default valign_top\"><div class=\"vc_col-sm-12 wpb_column vc_column_container\"><div class=\"vc_column-inner\"><div class=\"wpb_wrapper\">[vc_raw_html]JTNDZGl2JTIwY2xhc3MlM0QlMjJ3LXBvc3QtZWxtJTIwcG9zdF9uYXZpZ2F0aW9uJTIwbGF5b3V0X3NpbXBsZSUyMGludl9mYWxzZSUyMiUzRSUwQSUwOSUzQ2ElMjBjbGFzcyUzRCUyMnBvc3RfbmF2aWdhdGlvbi1pdGVtJTIwb3JkZXJfZmlyc3QlMjB0b19wcmV2JTIyJTIwaHJlZiUzRCUyMiUyRmRvY3MlMkZib3RzJTJGYW5hbHl6aW5nLXlvdXItYm90JTJGY3VzdG9tLWRhc2hib2FyZCUyRiUyMiUzRSUzQyUyRnAlM0UlMEElM0NkaXYlMjBjbGFzcyUzRCUyMnBvc3RfbmF2aWdhdGlvbi1pdGVtLWFycm93JTIyJTNFJTNDJTJGZGl2JTNFJTBBJTNDZGl2JTIwY2xhc3MlM0QlMjJwb3N0X25hdmlnYXRpb24taXRlbS1tZXRhJTIyJTNFUHJldmlvdXMlM0MlMkZkaXYlM0UlMEElM0NkaXYlMjBjbGFzcyUzRCUyMnBvc3RfbmF2aWdhdGlvbi1pdGVtLXRpdGxlJTIyJTNFJTNDc3BhbiUzRUN1c3RvbSUyMERhc2hib2FyZCUzQyUyRnNwYW4lM0UlM0MlMkZkaXYlM0UlMEElM0NwJTNFJTNDJTJGYSUzRSUzQ2JyJTIwJTJGJTNFJTBBJTNDYSUyMGNsYXNzJTNEJTIycG9zdF9uYXZpZ2F0aW9uLWl0ZW0lMjBvcmRlcl9zZWNvbmQlMjB0b19uZXh0JTIyJTIwaHJlZiUzRCUyMiUyRmRvY3MlMkZib3RzJTJGYW5hbHl6aW5nLXlvdXItYm90JTJGY29udmVyc2F0aW9uLWhpc3RvcnktZGFzaGJvYXJkJTJGJTIyJTNFJTNDJTJGcCUzRSUwQSUzQ2RpdiUyMGNsYXNzJTNEJTIycG9zdF9uYXZpZ2F0aW9uLWl0ZW0tYXJyb3clMjIlM0UlM0MlMkZkaXYlM0UlMEElM0NkaXYlMjBjbGFzcyUzRCUyMnBvc3RfbmF2aWdhdGlvbi1pdGVtLW1ldGElMjIlM0VOZXh0JTNDJTJGZGl2JTNFJTBBJTNDZGl2JTIwY2xhc3MlM0QlMjJwb3N0X25hdmlnYXRpb24taXRlbS10aXRsZSUyMiUzRSUzQ3NwYW4lM0VDb252ZXJzYXRpb25zJTIwSGlzdG9yeSUzQyUyRnNwYW4lM0UlM0MlMkZkaXYlM0UlMEElM0NwJTNFJTNDJTJGYSUzRSUzQyUyRmRpdiUzRQ==[\/vc_raw_html]<\/div><\/div><\/div><\/div><\/div><\/section>\n","protected":false},"excerpt":{"rendered":"<p>The NLP Insights helps you gain in-depth insights into the analytics data and assess your virtual assistant\u2019s performance in identifying and executing tasks. You can improve your VA\u2019s performance based on the insights. The Analyze &gt; NLP Insights page shows the specific information in the following sections: \u00a0Intent Found: Number of identified intents \u00a0Intent Not&#8230;<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[45],"tags":[],"class_list":["post-18052","post","type-post","status-publish","format-standard","hentry","category-analyzing-your-bot"],"_links":{"self":[{"href":"https:\/\/developer.kore.ai\/v9-3\/wp-json\/wp\/v2\/posts\/18052","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/developer.kore.ai\/v9-3\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/developer.kore.ai\/v9-3\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/developer.kore.ai\/v9-3\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/developer.kore.ai\/v9-3\/wp-json\/wp\/v2\/comments?post=18052"}],"version-history":[{"count":79,"href":"https:\/\/developer.kore.ai\/v9-3\/wp-json\/wp\/v2\/posts\/18052\/revisions"}],"predecessor-version":[{"id":48295,"href":"https:\/\/developer.kore.ai\/v9-3\/wp-json\/wp\/v2\/posts\/18052\/revisions\/48295"}],"wp:attachment":[{"href":"https:\/\/developer.kore.ai\/v9-3\/wp-json\/wp\/v2\/media?parent=18052"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/developer.kore.ai\/v9-3\/wp-json\/wp\/v2\/categories?post=18052"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/developer.kore.ai\/v9-3\/wp-json\/wp\/v2\/tags?post=18052"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}