Select a specific time period to display all the conversations that occurred during the period. The date format is MM-DD-YYYY. Following filter criteria are available for the date filter:

• 24 Hours – Data aggregated immediately preceding 24 hours is displayed. This is the default setting.
• 7 Days – Data aggregated over the past seven days is displayed. The start date is the day you select from which this filter is applied. By default, the current day is set as the start date, which you can change.
• Custom – You can choose a custom date range to filter the records. Choose the start date and end date in the calendar and click the Select button to filter the records. The Platform stores only the latest six months of data, and you can apply the date filter only for this date range.

The data on the relevant dashboard is displayed based on the interactive or non-interactive conversation type. Learn more.

The Developer Interactions are not included in the Conversation Type filter.

The dashboard data is displayed based on the following conversation statuses:

• Active Conversations: These are the ongoing conversations where the users are interacting with the VA.
• Closed Conversations: These are the conversations where an active session between the VA and the customer has ended. Learn more.

The UserID of the end-user related to the conversation. The following filter options are available:

• Kore User Id – This User Id is generated by the platform when the user registers; or
• Channel User Id – Email address of the user as received from the channels. Developer interactions are available under Channel User Id.
  For ‘Enterprise Bots’, the email address (kore registered email address) is available under Channel Id.

You can select the user id from the drop-down that’s populated after you enter the first three alphabets of the user id.

You can choose to either Include or Exclude the selected user id.

Channel-specific ids are shown only for the users who have interacted with the VA during the selected period.

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.

This criterion is not available for the Performance tab of NLP Insights.

Select the Trained option to filter the conversations that only contain trained utterances to the VA.

To view the conversations that contain untrained utterances, click Not Trained. By default, this filter shows the conversations’ data related to both Trained and Not Trained utterances.

This criterion is available only for the Intent Found tab of NLP Insights.

Select the Show Ambiguous option to filter the conversations that identify multiple tasks or intents and the user is asked to choose from the presented options.

This criterion is available only for the Intent Not Found tab of NLP Insights.

Select ‘Include Developer Interactions’, to include developer interactions in the results. By default, the developer interactions aren’t included. 

Developers include both the VA owners and shared developers.

Select the specific custom tags to filter the records based on the meta-information, session data, and filter criteria. You can add these tags at three levels:

• User Level: These tags can be added to the user information.
• Message Level: These tags can be added to the message of the current node. If the current node is not associated with a message, then the tag gets added to the immediate previous node that has a message associated with it.
• Session Level: These tags can be added at the current session of the user.

You can set the criterion as either Contain or Does Not Contain the specified value.

This criterion is not available for the Debug Logs tab of NLP Insights.

You can define Tags as key-value pairs from Script written anywhere in the application like Script node, Message, Entity, Confirmation prompts, Error prompts, Knowledge Graph responses, BotKit SDK, etc.

The following script can be used for adding meta tags:

• To add a User level tag:
  tags.addUserLevelTag(“tagname”,”tagvalue”)
• To add a Session level tag:
  tags.addSessionLevelTag(“tagname”,”tagvalue”)
• To add the Message level tag:
  tags.addMessageLevelTag(“tagname”,”tagvalue”)