はじめに
対話型AIプラットフォーム
チャットボットの概要
自然言語処理(NLP)
ボットの概念と用語
クイックスタートガイド
プラットフォームへのアクセス
ボットビルダーの操作
リリースノート
最新バージョン(英語)
以前のバージョン(英語)
コンセプト
設計
ストーリーボード
ダイアログタスク
ダイアログタスクとは
ダイアログビルダー
ノードタイプ
インテントノード
ダイアログノード
エンティティノード
フォームノード
確認ノード
ロジックノード
ボットアクションノード
サービスノード
Webhookノード
スクリプトノード
グループノード
エージェント転送ノード
ユーザープロンプト
音声通話プロパティ
イベント ハンドラー
ナレッジグラフ
ナレッジグラフの抽出
ナレッジグラフの構築
ボットにナレッジグラフを追加
グラフの作成
ナレッジグラフの構築
既存のソースからFAQを構築
通知タスク
スモールトーク
デジタルスキル
デジタルフォーム
デジタルビュー
デジタルビューとは
パネル
ウィジェット
トレーニング
トレーニングとは
機械学習
機械学習とは
モデル検証
ファンダメンタルミーニング
ナレッジグラフ
示唆
ランキングおよび解決
NLPの詳細設定
NLPのガイドライン
インテリジェンス
インテリジェンスとは
コンテキスト
コンテキストインテント
割り込み
複数インテントの検出
エンティティの変更
デフォルトの会話
センチメント管理
トーン分析
テストとデバッグ
ボットと会話
発話テスト
バッチテスト
会話テスト
デプロイ
チャネル
公開
LLM and Generative AI
Introduction
LLM Integration
Kore.ai XO GPT Module
Prompts & Requests Library
Co-Pilot Features
Dynamic Conversations Features
分析
ボットの分析
NLPメトリクス
会話フロー
Usage Metrics
封じ込め測定
カスタムダッシュボード
カスタムダッシュボードとは
メタタグ
カスタムダッシュボードとウィジェット
ユニバーサルボット
ユニバーサルボットとは
ユニバーサルボットの定義
ユニバーサルボットの作成
ユニバーサルボットのトレーニング
ユニバーサルボットのカスタマイズ
他言語の有効化
ストア
プラントと使用
Overview
Usage Plans
Support Plans
Invoices
管理
ボット認証
複数言語対応ボット
個人を特定できる情報の編集
ボット変数の使用
IVRのシステム連携
一般設定
ボット管理
ハウツー
Integrations
Actions
Actions Overview
Asana
Configure
Templates
Azure OpenAI
Configure
Templates
BambooHR
Configure
Templates
Bitly
Configure
Templates
Confluence
Configure
Templates
DHL
Configure
Templates
Freshdesk
Configure
Templates
Freshservice
Configure
Templates
Google Maps
Configure
Templates
Here
Configure
Templates
HubSpot
Configure
Templates
JIRA
Configure
Templates
Microsoft Graph
Configure
Templates
Open AI
Configure
Templates
Salesforce
Configure
Templates
ServiceNow
Configure
Templates
Stripe
Configure
Templates
Shopify
Configure
Templates
Twilio
Configure
Templates
Zendesk
Configure
Templates
Agents
Agent Transfer Overview
Custom (BotKit)
Drift
Genesys
Intercom
NiceInContact
NiceInContact(User Hub)
Salesforce
ServiceNow
Configure Tokyo and Lower versions
Configure Utah and Higher versions
Unblu
External NLU Adapters
Overview
Dialogflow Engine
Test and Debug
会話スキルの設計
バンキングボットを作成
バンキングボット – 資金の振り替え
バンキングボット – 残高を更新
ナレッジグラフを構築
スマートアラートの予約方法
デジタルスキルの設計
デジタルフォームの設定方法
デジタルビューの設定方法
データテーブルのデータの追加方法
データテーブルのデータの更新方法
Add Data from Digital Forms
ボットのトレーニング
示唆の使用方法
インテントとエンティティのパターンの使用方法
コンテキスト切り替えの管理方法
ボットのデプロイ
エージェント転送の設定方法
ボット関数の使用方法
コンテンツ変数の使用方法
グローバル変数の使用方法
ボットの分析
カスタムダッシュボードの作成方法
カスタムタグを使ってフィルタリング
Data
Overview
Data Table
Table Views
App Definitions
Data as Service
Build a Travel Planning Assistant
Travel Assistant Overview
Create a Travel Virtual Assistant
Design Conversation Skills
Create an ‘Update Booking’ Task
Create a Change Flight Task
Build a Knowledge Graph
Schedule a Smart Alert
Design Digital Skills
Configure Digital Forms
Configure Digital Views
Train the Assistant
Use Traits
Use Patterns
Manage Context Switching
Deploy the Assistant
Use Bot Functions
Use Content Variables
Use Global Variables
Use Web SDK
Build a Banking Assistant
Migrate External Bots
Google Dialogflow Bot
APIs & SDKs
API Reference
API Introduction
Rate Limits
API List
koreUtil Libraries
SDK Reference
SDK Introduction
Web SDK
How the Web SDK Works
SDK Security
SDK Registration
Web Socket Connect and RTM
Tutorials
Widget SDK Tutorial
Web SDK Tutorial
BotKit SDK
BotKit SDK Deployment Guide
Installing the BotKit SDK
Using the BotKit SDK
SDK Events
SDK Functions
Tutorials
BotKit - Blue Prism
BotKit - Flight Search Sample VA
BotKit - Agent Transfer
  1. ホーム
  2. Docs
  3. Virtual Assistants
  4. Analyzing Your Bot
  5. Dashboard Filters

Dashboard Filters

The dashboard filters are used to filter and view the analytics data for virtual assistants (VAs) on the following dashboards in the ANALYZE section based on the user’s selection(s):

To understand the filter criteria availability on different dashboards, see the Filter Criteria Matrix.

Note: By default, the VA dashboard displays data for the past 24 hours.

Filter Criteria Descriptions

The following table describes all the filter criteria available on the Kore.ai XO platform:

Filter Description
Date

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.
Conversation Type

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.

Conversation Status

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.
UserID

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.

Languages

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.

Channels When the VA is published in multiple channels, select this filter to view the data for various channels enabled for the VA.

The conversations that occurred in all enabled channels are displayed by default.
Task/Intent Select specific tasks or intents to filter the conversation related to those tasks or intents. The page shows the conversations related to all tasks or intents by default.

This criterion is not available for the Intent Not Found tab of NLP Insights.
Utterance Type

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.

Utterance Status The dashboard data is filtered based on the utterance status, Reviewed or Yet to be Reviewed.
Intent Type The dashboard data is filtered based on the conversation skill – Dialog Tasks, FAQs, or Small Talks.
Dialog Tasks The dashboard data is filtered based on the selection of available Dialog Tasks in the Dialog Tasks drop-down.
Ambiguous

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.

Developer Interactions

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.

Custom Tags

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”)
Note: To see the filter criteria from UserID till Custom Tags listed in the preceding table, click the More Filters drop-down.

Filter Criteria Matrix

The following matrix shows the availability of filter criteria on different dashboards and their default values:

Filter Type Overview
Dashboard
Conversation
Dashboard
Users
Dashboard
Performance
Dashboard
Conversations History Dashboard NLP Insights Conversational Insights Default
value
Date Period 24 Hours
Conversation Type Interactive
Conversation Status Closed
Channels ALL
Custom Tags None
Language ALL
UserID X X X X X X None
Task / Intent X X X X X None
Utterance Type X X X X X X Both
Developer Interactions X X X X X X Checked
Utterance Status X X X X X X Both
Intent Type X X X X X X Dialog Tasks

 

Dashboard Filters

The dashboard filters are used to filter and view the analytics data for virtual assistants (VAs) on the following dashboards in the ANALYZE section based on the user’s selection(s):

To understand the filter criteria availability on different dashboards, see the Filter Criteria Matrix.

Note: By default, the VA dashboard displays data for the past 24 hours.

Filter Criteria Descriptions

The following table describes all the filter criteria available on the Kore.ai XO platform:

Filter Description
Date

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.
Conversation Type

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.

Conversation Status

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.
UserID

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.

Languages

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.

Channels When the VA is published in multiple channels, select this filter to view the data for various channels enabled for the VA.

The conversations that occurred in all enabled channels are displayed by default.
Task/Intent Select specific tasks or intents to filter the conversation related to those tasks or intents. The page shows the conversations related to all tasks or intents by default.

This criterion is not available for the Intent Not Found tab of NLP Insights.
Utterance Type

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.

Utterance Status The dashboard data is filtered based on the utterance status, Reviewed or Yet to be Reviewed.
Intent Type The dashboard data is filtered based on the conversation skill – Dialog Tasks, FAQs, or Small Talks.
Dialog Tasks The dashboard data is filtered based on the selection of available Dialog Tasks in the Dialog Tasks drop-down.
Ambiguous

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.

Developer Interactions

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.

Custom Tags

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”)
Note: To see the filter criteria from UserID till Custom Tags listed in the preceding table, click the More Filters drop-down.

Filter Criteria Matrix

The following matrix shows the availability of filter criteria on different dashboards and their default values:

Filter Type Overview
Dashboard
Conversation
Dashboard
Users
Dashboard
Performance
Dashboard
Conversations History Dashboard NLP Insights Conversational Insights Default
value
Date Period 24 Hours
Conversation Type Interactive
Conversation Status Closed
Channels ALL
Custom Tags None
Language ALL
UserID X X X X X X None
Task / Intent X X X X X None
Utterance Type X X X X X X Both
Developer Interactions X X X X X X Checked
Utterance Status X X X X X X Both
Intent Type X X X X X X Dialog Tasks

 

メニュー