시작
Kore.ai 대화형 플랫폼
챗봇 개요
자연어 처리(NLP)
봇 개념 및 용어들
빠른 시작 가이드
봇 빌더 접근 방법
사용 고지 사항 (영어)
Kore.ai 봇 빌더로 작업하기
봇 구축 시작하기
릴리스 정보
현재 버전 (영어)
이전 버전 (영어)

개념
디자인
스토리보드
대화 작업
개요
Using the Dialog Builder Tool
노드 유형
사용자 의도 노드
대화 노드
엔티티 노드
양식 노드
확인 노드
서비스 노드
봇 조치 노드
Service Node
WebHook 노드
스크립트 노드
노드 그룹화하기
Agent Transfer Node
사용자 프롬프트
음성 통화 속성
대화 관리
노드 및 전환
구성 요소 전환
컨텍스트 개체
이벤트 기반 봇 조치
지식 그래프
소개
지식 추출
지식 그래프 생성
봇에 지식 그래프 추가
그래프 생성
지식 그래프 작성
FAQ 추가
작업 실행
기존 소스에서 FAQ 구축
특성, 동의어 및 불용어
변수 네임스페이스 관리
수정
용어 편집 및 삭제
용어 편집 및 삭제
질문과 응답 편집
Knowledge Graph Training
지식 그래프 분석
봇 온톨로지 가져오기 및 내보내기
지식 그래프 가져오기
지식 그래프 내보내기
지식 그래프 생성
CSV 파일에서
JSON 파일
지식 그래프 생성
경고 작업
스몰 토크
Digital Skills
디지털 양식
Views
Digital Views
Panels
Widgets
기차
봇 성능 향상 – NLP 최적화
기계 학습
소개
모델 검증
기초 의미
지식 그래프 학습
특성
순위 및 해결
고급 NLP 설정
NLP 설정 및 지침
봇 인텔리전스
소개
컨텍스트 관리
컨텍스트 관리
대화 관리
다중 – 의도 탐지
엔티티 수정
기본 대화
정서 관리
어조 분석
Test & Debug
봇과 대화
발화 테스트
배치 테스트하기
대화 테스트
배포
채널 활성화
봇 게시
분석
봇 분석하기
Conversations Dashboard
Performance Dashboard
사용자 정의 대시보드
소개
맞춤형 메타 태그
사용자 정의 대시보드 생성 방법
Conversation Flows
NLP 지표
Containment Metrics
사용량 지표
스마트 봇
소개
범용 봇
소개
범용 봇 정의
범용 봇 생성
범용 봇 학습
범용 봇 커스터마이징
범용 봇용 추가 언어 활성화
스토어
Manage Assistant
플랜 및 사용량
Overview
Usage Plans
Support Plans
플랜 관리
봇 인증
다국어 봇
개인 식별 정보 삭제하기
봇 변수 사용
IVR 통합
일반 설정
봇 관리

방법
간단한 봇 생성하기
Design Conversation Skills
뱅킹 봇 생성
뱅킹 봇 – 자금 이체
뱅킹 봇 – 잔액 업데이트
Knowledge Graph (KG) 구축
스마트 경고를 예약하는 방법
Design Digital Skills
디지털 양식 설정 방법
디지털 보기 설정 방법
데이터 테이블에 데이터를 추가하는 방법
데이터 테이블 내 데이터 업데이트 방법
UI 양식에서 데이터 테이블에 데이터를 추가하는 방법
Train the Assistant
특성 사용 방법
의도와 엔티티에 대한 패턴 사용 방법
컨텍스트 전환 관리 방법
Deploy the Assistant
상담사 전환을 설정하는 방법
봇 기능 사용 방법
콘텐츠 변수 사용 방법
전역 변수 사용 방법
Kore.ai 웹 SDK 튜토리얼
Kore.ai 위젯 SDK 튜토리얼
Analyze the Assistant
사용자 정의 대시보드 생성 방법
사용자 지정 태그를 사용하여 봇 메트릭을 필터링하는 방법

API 및 SDK
API 참조
Kore.ai API 사용
API 목록
API 컬렉션
koreUtil Libraries
SDK 참조
상담사 전환을 설정하는 방법
봇 기능 사용 방법
콘텐츠 변수 사용 방법
전역 변수 사용 방법
소개
Kore.ai 웹 SDK 튜토리얼
Kore.ai 위젯 SDK 튜토리얼

관리
소개
봇 관리자 콘솔
대시보드
사용자 관리
사용자 관리
그룹 관리
역할 관리
봇 관리 모듈
등록
사용자 초대
사용자 등록을 위한 대량 초대 보내기
사용자 및 사용자 데이터 가져오기
Active Directory에서 사용자 동기화
보안 및 준수
싱글 사인 온 사용
보안 설정
Kore.ai 커넥터
봇 관리자용 분석
Billing (지원하지 않음)
  1. Docs
  2. Virtual Assistants
  3. Analyzing Your Bot
  4. Conversations History

Conversations History

The Conversation History module allows you to review the transcripts of past conversations and label certain conversations for follow-up or further action.

The Advanced Conversation Analytics feature provides a more detailed view of the conversation, including events and custom tags, which can help you better understand the interaction between the customer and the virtual assistant. Custom Tags can be reused across conversations for training purposes and for identifying areas where the virtual assistant could improve.

Note: The Conversations History Dashboard is available only post the 9.3 release, i.e. post-July 24, 2022.

Navigating to the Conversation History Dashboard

To access the Conversation History Dashboard, follow these steps:

  1. Sign in to the Kore.ai Platform and select the required Virtual Assistant.
  2. Click the Analyze tab on the top menu.
  3. Click Conversation History on the left navigation menu as shown below.

Filter Views Page

The Filter Views page is the preface or landing page displayed when you click the Conversations History left menu item. You can create and view prebuilt and custom filters, filter configurations, and descriptions on this page in addition to the following:

  • View the available conversation filters and their configurations.
  • Create a custom filter to view only the required data.
  • Access the Conversations History Dashboard for the selected preset.

Prebuilt Filters for Conversations History

As an analyst, you may need a customized view of the conversation’s history data based on specific conditional filters. This helps analyze conversations based on priority/criticality.

The Platform now supports Prebuilt Filters or Presets for the most common use case scenarios. Presets reduce the developer’s efforts in skimming through each conversation to understand and tag them for a specific use case.

How it works

  1. The system checks the configuration parameters and the filter conditions for a conversation session.
  2. The conversation session is mapped to the respective filter automatically.
  3. Based on the date range selected on the Conversations History Dashboard, the system fetches and displays the conversations that meet the Prebuilt Filters’ criteria.

Types of Prebuilt Filters

The following table displays each preset’s filter name, predefined configuration parameters, and description. For more information on the configuration parameters, please click here.

Filter Name Configuration Description
All Conversations (default)
  • Conversation Status: CLOSED
  • Containment Type: SELF-SERVICE
  • Is Developer: INCLUDE
  • Session Type: INTERACTIVE
Shows all the conversations made during the specified dates irrespective of the filter criteria selected on the dashboard.

Note: The user cannot edit the “All Conversations” view.

Conversations with Multiple Intent Identification Failures
  • Conversation Status: CLOSED
  • Containment Type: SELF-SERVICE
  • isDeveloper: EXCLUDE
  • Session Type: INTERACTIVE
  • Events: Greater than equals to 2 intent identification failures.
Shows all the conversations with intents unidentified in a given date range.
Conversations with Multiple Entity Retries
  • Conversation Status: CLOSED
  • Containment Type: SELF-SERVICE
  • isDeveloper: EXCLUDE
  • Session Type: INTERACTIVE
  • Events: Greater than equals to 2 entity retries.
Shows all the conversations with entity retries in a given date range.
Conversations with Multiple Confirmation Retries
  • Conversation Status: CLOSED
  • Containment Type: SELF-SERVICE
  • isDeveloper: EXCLUDE
  • Session Type: INTERACTIVE
  • Events: Greater than equals to 2 confirmation retries.
Shows all the conversations with confirmation retries in a given date range.
Short Conversations resulting in User-Drop off
  • Conversation Status: CLOSED
  • Containment Type: USER DROP-OFF
  • isDeveloper: EXCLUDE
  • Session Type: INTERACTIVE
  • Events: Greater than or equals to 2 confirmation retries.
  • Conversation Duration: Less than 30.
Shows all the conversations where users got dropped off and conversations that are less than 30 seconds.

Feedback Prebuilt Filter

The Platform supports the Feedback filter on the Filter Views panel to create custom feedback filters. Based on the filter criteria, the system groups and displays the conversations for the following parameters:

  • Feedback Survey Template Type: Indicates if the selected type is NPS, CSAT, or Thumbs-up / Thumbs-down. Learn more.
  • Operator: The conditional/logical operator that applies to the Feedback filter evaluation which includes one of the following:
    • Equals to
    • Less than or equals to
    • Greater than equals to
    • Greater than
    • Less than
  • Value: The feedback survey score used for the conditional logic evaluation.

Note: The conversations with different survey types can be grouped using the OR operator to satisfy multiple conditions.

View Prebuilt Filters

To view the prebuilt filters, follow the steps below:

  1. Navigate to AnalyzeConversations History on the left menu.
  2. The prebuilt filters are categorized and listed on the Filter Views page.
  3. Click Read More to see the configuration details of each conversation filter type.
  4. Click any prebuilt filter name to access the Conversations History panel where relevant data is displayed.

Create a Custom Conversation Filter

A Conversation Filter helps group and display selective conversations history data based on a specific criterion on the dashboard. To add a custom filter, follow the steps below:

    1. Click Analyze on the top menu.
    2. Click Conversations History on the left menu.
    3. On the Conversations History page, click + Create Filter.
    4. On the Create Conversation Filter panel, provide inputs for the following fields:
      ld Configuration Description
      View Name N/A Enter the name of the filter that will be displayed on the dashboard.
      Description N/A Enter the description for the filter that will be displayed on the dashboard.
      Conversation Status The available options include:

      • All
      • Active
      • Closed
      Select All to view all conversations, Active to view ongoing conversations, and Closed to view conversations that have ended.
      Containment Type The available options include:

      • Self-service
      • User Drop-off
      • Agent Transfer
      Select one of the following:

      • Self-service to view only customer self-service conversations
      • User Drop-off to view only conversations where the user dropped off.
      • Agent Transfer to filter conversations with the agent transfer flow.
      Channels The available selection options include:

      • All Channels
      • Web/Mobile Client
      • Webhook
      • Other configured channels.
      Filters conversations using the enabled channels.
      Languages The available selection options include:

      • All Languages
      • English (default)
      • Other configured languages
      Filters conversations using the enabled languages.
      Session Type The available selection options include:

      • All
      • Interactive
      • Non-interactive
      Filters conversations for conversations across all channels, only interactive channels, or only non-interactive channels based on the selected option.
      User ID The available selection options include:

      • Include
      • Exclude
      Filters conversations using the Platform user identities based on the inclusion or exclusion list.
      Channel ID / Kore ID selection Toggle between the options. Filters conversations using either the Channel ID or Kore ID.
      Task / Intent Select either all intents or specific configured intents. Filters conversations using all intents/tasks or specific tasks/intents identified during the conversation sessions.
      Developer Interactions (IsDeveloper) The available selection options include:

      • Include
      • Exclude
      Filters conversations by including or excluding developer interactions based on the selected condition.
      Time Zone Select from different global time zones. Filters conversations based on the time zone of the conversation session.
      Conversation Duration The Conditional Filter options include:

      • Less than
      • Less than Equals to
      • Greater than
      • Greater than equals to
      • Equals to

      The Time units options include:

      • Seconds
      • Minutes
      Filters conversations based on the conditional filters set for the conversation session duration in seconds/minutes.
      Events The Conditional Filter options include:

      • Less than
      • Less than Equals to
      • Greater than
      • Greater than equals to
      • Equals to

      The Event Name options include:

      • Intent Identified
      • Intent not Identified
      • Success Task
      • Fail Task
      • Sentiment Event
      • User Sentiment Type
      • Entity Retry
      • Confirmation Retry
      • On Connect
      • End of Conversation
      • Debug Log
      • Welcome
      • Welcome Telegram
      • Welcome Facebook
      • Welcome Telephone
      • Standard Response Interruption
      • Message Node Interruption
      • Optional Entity
      • Script Node Failure
      • Service Node Failure
      • Agent Transfer
      Filters conversations based on the conditional filters set for the conversation session duration and the selected event.
      Feedback The Feedback Type options include:

      • NPS
      • CSAT
      • Thumbs-up/Down

      The Conditional Filter options include:

      • Less than
      • Less than Equals to
      • Greater than
      • Greater than equals to
      • Equals to

      The options for Score include:

      • NPS: Select a value between 0 and 10.
      • CSAT: Select a value between 0 and 5.
      • Thumbs-up/Down: Select either 0 or 1.
      Filters conversations based on the feedback type, conditional filter, and feedback score selection.
      Labels Select either all conversation labels or a specific configured label. Filters conversations based on the selected label(s).
      Custom Tags Select the key and type the value for the key to define the custom tag selection. You can combine multiple key-value pairs to define the custom tag selection. Filters conversations using custom tags added to the conversation for a key-value pair and the AND logical operator.
    5. Click Save.

The new custom filter is listed on the Filter Views page. The conversations are grouped and displayed Conversations History Dashboard based on the inputs provided on the Filter Views page.

Edit a Conversation Filter

You can edit one or more fields for an existing conversation filter. To edit a conversation filter, follow the steps below:

  1. Click the custom filter on the Filter Views page.
  2. Click the More Filters dropdown list on the Conversations History panel.
  3. Modify the required fields on the Edit Conversation Filter window.
  4. Click Apply.

Filter Criteria

You can customize the Conversations History data view by selecting the Filter Criteria on the dashboard. Please click here to view the available filters.

Conversations History Dashboard

The Conversations History Dashboard displays the following information for each conversation session that meets the defined filter condition(s) for the selected date range.

Containment Type

The following containment types affect the conversation flow and are displayed on top of individual Conversations History details panel:

  • Self-service: Indicates that the conversation (initiated by the user) with a VA was successfully completed.
  • Agent Transfer: Indicates that the conversation was transferred to a live agent using the Agent Transfer node in the Dialog Flow.
  • User Drop-off: Indicates that the user stopped participating in the conversation before it was completed, either due to an error in the flow or some other reason.

Label

A custom label helps identify conversations that require follow-up or indicate an action item for an analyst during review.

Add a Custom Label

To add a custom label in addition to the default label for a conversation, follow the steps below:

  1. Click the + Label button on the Conversations History panel for the required conversation session.
  2. In the Labels window, scroll down and click + Add.
  3. Enter the label name, and click the confirm icon.
    Note: You can select a different label color by clicking the color icon and using the color palette.
  4. Click Save.

Manage a Custom Label

Edit

You can edit or delete an existing custom label while adding a new label.

To edit a label, follow the steps below:

  1. Click the + Label button on the Conversations History panel for the required conversation session.
  2. In the Labels window, click the edit icon for the label you want to modify.
  3. Make the changes and click the confirm icon.
  4. Click Save.

Delete

To delete a label, follow the steps below:

  1. Click the + Label button on the Conversations History panel for the required conversation session.
  2. In the Labels window, click the delete icon for the label you want to remove.
  3. Click Save.

Other Conversation Parameters

The Channel, Language, Date, and conversation duration are displayed at the top of the Conversation History analytics panel.

Conversation Summary

  • User Messages: The number of messages sent by the user to the virtual assistant.
  • Bot Messages: The number of messages sent by the bot/virtual assistant to the user.
  • Intents Identified: The number of user intents identified by the virtual assistant during the conversation.
  • Intent Unidentified: The number of utterances that did not result in any intent identification during the conversation.
  • Tasks Completed: The number of tasks successfully completed by the virtual assistant.
  • Failed Tasks: The number of tasks that failed during the conversation.

Conversation Events

Conversation Events indicate the sequence of occurrences during a conversation triggered by customer inputs and responses while interacting with a bot. Each event can be categorized into regular and error-based occurrences. When analyzing a conversation flow, the user can identify the event type based on the following icons that are displayed for the relevant event.

The list of events triggered during a conversation are displayed below.

Intent Found: Triggered when the virtual assistant understands the user’s intent. The intent name identified is displayed.

Event Description
Intent Not Found Triggered when the virtual assistant is unable to understand the user’s intent.
Agent Transfer Triggered when a live agent transfer is initiated during the conversation.
Entity Retry Triggered when the input provided by the user is not identified by the virtual assistant and a input retry request to the customer.
Confirmation Retry Triggered when a confirmation request for a query or selection is generated from the virtual assistant to the customer.
On Connect Triggered every time a customer invokes Web/Mobile SDK (a conversation is initiated on the channel).
Sentiment Event Triggered when a customer’s sentiment is identified during the conversation. The user sentiment type identified is displayed.
Welcome Triggered on receiving a message from user when channel specific event is not configured.
Welcome Event Telegram Triggered on receiving a welcome event from Telegram.
Welcome Event Facebook Triggered on receiving a welcome event from Facebook Messenger.
Welcome Event Telephone Triggered on receiving a Telephone Call from any voice channel.
End Triggered on the closing of a conversation.
Debug Log Triggered when a debug log script runs for a script failure or service failure event.
Script Failure Triggered when a Script node failure occurs.
Service Failure Triggered when a service node failure occurs.
RCS Opt In Triggered on receiving Opt-In from the user for Rich Communication Services.
RCS Opt Out Triggered on receiving Opt-out from the user for Rich Communication Services.
User Message Triggered when a customer sends a message to the virtual assistant on the channel.

Enriched Chat Transcript

The Enriched Chat Transcript feature provides a more detailed view of the conversation, with all the events associated with each message displayed in the chat transcript slider. This can be useful for understanding the conversation at a granular level and identifying any issues that may have arisen. It can also help train the virtual assistant and improve its performance.

To view the Enriched Chat Transcript, enable the Show Events option (default setting) in the Chat History panel.

Note: Disabling the Show Events option will display only the chat transcript without the events.

The Event labels that appear under Conversation Events are displayed against each chat text in the chat transcript slider. Click here to learn more about Conversational Events.

 

Feedback User Type Label

For conversations with the customer response to a feedback survey, the feedback user type label is added automatically based on the analytics data. This label indicates if a customer is a promoter or a detractor.

Hovering the mouse on the label displays the following data:

  • Number of feedback responses collected.
  • Type of feedback survey.
  • Customer type (result generated internally after the feedback is submitted).
  • Feedback score.

User Details

To view the details of the agent that handled a conversation session, follow the steps below:

  1. Click either Conversation Summary or Conversation Event on the dashboard.
  2. On the landing page, click the User Details tab to view the following information:
    • User ID: The unique ID assigned to the agent.
    • Channel Data: The conversational channel where the interaction occurred.
    • Total Conversation Sessions: The total number of conversations the agent has handled for the selected period.
    • Sessions in the Last 30 Days: The number of conversations the agent handled in the date period that the used has selected within the last 30 days.
    • Last Interaction Date: The date of the agent’s most recent customer interaction.
    • User Meta tags: Used to identify important keywords in the conversation.

Chat History

The chat conversation flow between the virtual assistant and the customer is displayed in the Chat History panel, including events, actions, input requests, queries, and intent-based responses. Any failed tasks or exceptions that occurred during the conversation will also be displayed here.

The Enriched Chat Transcript is visible on the Chat History panel.

To view Chat History, follow these steps:

  • Click an entry under Conversation Summary or an event under Conversation Events on the Conversation History dashboard.

The Chat History window displays the conversation flow. In addition, the following information is displayed on the side pane:

  • Date Filter dropdown to select the period of Chat History.

Date-wise information summary on the following:

  • Conversation channel.
  • Chat initiation event.
  • Chat Duration
  • Chat Start time and End time.
  • Conversation summary of the following metrics:
    • User messages
    • Bot messages
    • Intents identified
    • Intents Unidentified
    • Tasks completed
    • Failed Tasks
  • Language (of interaction)
  • Event labels tagged to the conversation history.
  • Trace ID – A unique ID assigned to each incoming message. The Id is also included in all the logs maintained by the Platform. When you hover over the message, the info icon appears. Click the Info icon to view the Message Id associated with the message.
  • Click the Message Id to view the Trace ID associated with a message in the Chat History.
    Note: The Trace ID is retained in the logs for 30 days. Once the Trace ID is expired, you see a tooltip message as ‘Trace Id: Trace records for this message are not available‘.
  • You can see the “payload value” of the performed template action (e.g.: Button Click) in the individual message bubble and the “title” (e.g.: the selected button title) as a tag to the message bubble in the chat transcript. This is applicable only for WebSDK templates.
    Conversation with the Bot

    Conversation History

Define Alternate Text for JavaScript Messages

The Platform uses the{} JavaScript tag in the Chat History for bot messages and templates written using JavaScript. However, bot designers can now add a context-specific Alternate Text to JavaScript messages/templates they define and explain the purpose more clearly. The added Alternate Text is displayed alongside the JavaScript message tag in the Chat History for developers to get a better understanding of the message’s intent. 

The Conversation History API response includes a parameter messages.tags.altText which captures the Alternate Text value(s) configured in the JavaScript message or Web SDK template payload through the predefined function discussed below.

How It Works

  1. Developer uses a predefined function in the syntax tags.addAlternateText(“value”) to add the Alternative Text to a JavaScript message or Web SDK template on any channel, including a Webhook.
  2. The Alternate text indicating the JavaScript message/template’s purpose should be provided for the value parameter. For example, tags.addAlternateText(“Accounts Selection Message”).

Usage Example

For a bank account creation task, the Platform renders a template in the end channel to prompt the user for account type selection. This requires the developer to define a JavaScript message specific to the channel.

The developer can generate an Alternate text like “Accounts Selection Message,” in the template code to indicate that the JavaScript message is for account type selection.

After the end user selects an account type, the Alternate message appears in the Chat History above the {} JavaScript tag.

Important Considerations

  • You can define static and dynamic values for the alternate text.
  • Alternate text can be defined for JavaScript messages in user prompts, error prompts, Small Talk, standard responses, FAQs, and events.
  • The Platform assigns the latest to a message when you add multiple Alternate text values.
  • In the Chat History window, the Platform substitutes the payload label with an alternative text tag for all channel templates, excluding the SDK Template.

Message Tags

Message Tags help identify and categorize messages in the chat transcript. They add clarity and context to the conversation and can be reused across related conversations. System-defined message tags are provided by default, but users can create custom tags by defining a key-value pair. The key is used as an identifier for the specific message, and the value is the expected customer response to that message.

Important:

  • You cannot add the same key to a message again.
  • A custom message tag can only be added and detached from a message and not edited.

To add a custom message tag, follow the steps below:

  1. Hover over the message transcript in the conversation where you wish to add the message tag.
  2. Click +Message Tag.
  3. In the Add Message Tag window, enter the Key and Value in their respective text fields.
  4. Click Save. The new message tag is displayed below the message in the transcript slider.

Note: The custom message tag you create is available in the Custom Tags Filters section as one of the filtering criteria.

The Feedback Survey feature allows customers to provide feedback on their conversations with the virtual assistant.

If enabled, the customer’s response to the survey will be displayed in the chat transcript under Chat History.

The system captures and displays a feedback event label “End of Conversation: Survey Type” on the chat transcript, indicating the end of the conversation and the survey type.

The response will be mapped to a key-value pair for the conversation timeline, which can be useful for analyzing the conversation and customer experience at a granular level. This information is useful to improve the virtual assistant’s performance and enhance the customer experience.

The Conversation Summary displays the following information on the Feedback event:

  1. The Start Time and End Time, along with the real-time counts for the following:
  • User Messages
  • Bot Messages
  • Intents Identified
  • Intents Unidentified
  • Tasks Completed
  • Failed Tasks
  1. The Feedback Event is based on the event timeline with Key and Value.
  2. The total number of feedback responses collected for the session and the following:
  • Type of Feedback
  • Feedback response
  • Score

 

Conversations History

The Conversation History module allows you to review the transcripts of past conversations and label certain conversations for follow-up or further action.

The Advanced Conversation Analytics feature provides a more detailed view of the conversation, including events and custom tags, which can help you better understand the interaction between the customer and the virtual assistant. Custom Tags can be reused across conversations for training purposes and for identifying areas where the virtual assistant could improve.

Note: The Conversations History Dashboard is available only post the 9.3 release, i.e. post-July 24, 2022.

Navigating to the Conversation History Dashboard

To access the Conversation History Dashboard, follow these steps:

  1. Sign in to the Kore.ai Platform and select the required Virtual Assistant.
  2. Click the Analyze tab on the top menu.
  3. Click Conversation History on the left navigation menu as shown below.

Filter Views Page

The Filter Views page is the preface or landing page displayed when you click the Conversations History left menu item. You can create and view prebuilt and custom filters, filter configurations, and descriptions on this page in addition to the following:

  • View the available conversation filters and their configurations.
  • Create a custom filter to view only the required data.
  • Access the Conversations History Dashboard for the selected preset.

Prebuilt Filters for Conversations History

As an analyst, you may need a customized view of the conversation’s history data based on specific conditional filters. This helps analyze conversations based on priority/criticality.

The Platform now supports Prebuilt Filters or Presets for the most common use case scenarios. Presets reduce the developer’s efforts in skimming through each conversation to understand and tag them for a specific use case.

How it works

  1. The system checks the configuration parameters and the filter conditions for a conversation session.
  2. The conversation session is mapped to the respective filter automatically.
  3. Based on the date range selected on the Conversations History Dashboard, the system fetches and displays the conversations that meet the Prebuilt Filters’ criteria.

Types of Prebuilt Filters

The following table displays each preset’s filter name, predefined configuration parameters, and description. For more information on the configuration parameters, please click here.

Filter Name Configuration Description
All Conversations (default)
  • Conversation Status: CLOSED
  • Containment Type: SELF-SERVICE
  • Is Developer: INCLUDE
  • Session Type: INTERACTIVE
Shows all the conversations made during the specified dates irrespective of the filter criteria selected on the dashboard.

Note: The user cannot edit the “All Conversations” view.

Conversations with Multiple Intent Identification Failures
  • Conversation Status: CLOSED
  • Containment Type: SELF-SERVICE
  • isDeveloper: EXCLUDE
  • Session Type: INTERACTIVE
  • Events: Greater than equals to 2 intent identification failures.
Shows all the conversations with intents unidentified in a given date range.
Conversations with Multiple Entity Retries
  • Conversation Status: CLOSED
  • Containment Type: SELF-SERVICE
  • isDeveloper: EXCLUDE
  • Session Type: INTERACTIVE
  • Events: Greater than equals to 2 entity retries.
Shows all the conversations with entity retries in a given date range.
Conversations with Multiple Confirmation Retries
  • Conversation Status: CLOSED
  • Containment Type: SELF-SERVICE
  • isDeveloper: EXCLUDE
  • Session Type: INTERACTIVE
  • Events: Greater than equals to 2 confirmation retries.
Shows all the conversations with confirmation retries in a given date range.
Short Conversations resulting in User-Drop off
  • Conversation Status: CLOSED
  • Containment Type: USER DROP-OFF
  • isDeveloper: EXCLUDE
  • Session Type: INTERACTIVE
  • Events: Greater than or equals to 2 confirmation retries.
  • Conversation Duration: Less than 30.
Shows all the conversations where users got dropped off and conversations that are less than 30 seconds.

Feedback Prebuilt Filter

The Platform supports the Feedback filter on the Filter Views panel to create custom feedback filters. Based on the filter criteria, the system groups and displays the conversations for the following parameters:

  • Feedback Survey Template Type: Indicates if the selected type is NPS, CSAT, or Thumbs-up / Thumbs-down. Learn more.
  • Operator: The conditional/logical operator that applies to the Feedback filter evaluation which includes one of the following:
    • Equals to
    • Less than or equals to
    • Greater than equals to
    • Greater than
    • Less than
  • Value: The feedback survey score used for the conditional logic evaluation.

Note: The conversations with different survey types can be grouped using the OR operator to satisfy multiple conditions.

View Prebuilt Filters

To view the prebuilt filters, follow the steps below:

  1. Navigate to AnalyzeConversations History on the left menu.
  2. The prebuilt filters are categorized and listed on the Filter Views page.
  3. Click Read More to see the configuration details of each conversation filter type.
  4. Click any prebuilt filter name to access the Conversations History panel where relevant data is displayed.

Create a Custom Conversation Filter

A Conversation Filter helps group and display selective conversations history data based on a specific criterion on the dashboard. To add a custom filter, follow the steps below:

    1. Click Analyze on the top menu.
    2. Click Conversations History on the left menu.
    3. On the Conversations History page, click + Create Filter.
    4. On the Create Conversation Filter panel, provide inputs for the following fields:
      ld Configuration Description
      View Name N/A Enter the name of the filter that will be displayed on the dashboard.
      Description N/A Enter the description for the filter that will be displayed on the dashboard.
      Conversation Status The available options include:

      • All
      • Active
      • Closed
      Select All to view all conversations, Active to view ongoing conversations, and Closed to view conversations that have ended.
      Containment Type The available options include:

      • Self-service
      • User Drop-off
      • Agent Transfer
      Select one of the following:

      • Self-service to view only customer self-service conversations
      • User Drop-off to view only conversations where the user dropped off.
      • Agent Transfer to filter conversations with the agent transfer flow.
      Channels The available selection options include:

      • All Channels
      • Web/Mobile Client
      • Webhook
      • Other configured channels.
      Filters conversations using the enabled channels.
      Languages The available selection options include:

      • All Languages
      • English (default)
      • Other configured languages
      Filters conversations using the enabled languages.
      Session Type The available selection options include:

      • All
      • Interactive
      • Non-interactive
      Filters conversations for conversations across all channels, only interactive channels, or only non-interactive channels based on the selected option.
      User ID The available selection options include:

      • Include
      • Exclude
      Filters conversations using the Platform user identities based on the inclusion or exclusion list.
      Channel ID / Kore ID selection Toggle between the options. Filters conversations using either the Channel ID or Kore ID.
      Task / Intent Select either all intents or specific configured intents. Filters conversations using all intents/tasks or specific tasks/intents identified during the conversation sessions.
      Developer Interactions (IsDeveloper) The available selection options include:

      • Include
      • Exclude
      Filters conversations by including or excluding developer interactions based on the selected condition.
      Time Zone Select from different global time zones. Filters conversations based on the time zone of the conversation session.
      Conversation Duration The Conditional Filter options include:

      • Less than
      • Less than Equals to
      • Greater than
      • Greater than equals to
      • Equals to

      The Time units options include:

      • Seconds
      • Minutes
      Filters conversations based on the conditional filters set for the conversation session duration in seconds/minutes.
      Events The Conditional Filter options include:

      • Less than
      • Less than Equals to
      • Greater than
      • Greater than equals to
      • Equals to

      The Event Name options include:

      • Intent Identified
      • Intent not Identified
      • Success Task
      • Fail Task
      • Sentiment Event
      • User Sentiment Type
      • Entity Retry
      • Confirmation Retry
      • On Connect
      • End of Conversation
      • Debug Log
      • Welcome
      • Welcome Telegram
      • Welcome Facebook
      • Welcome Telephone
      • Standard Response Interruption
      • Message Node Interruption
      • Optional Entity
      • Script Node Failure
      • Service Node Failure
      • Agent Transfer
      Filters conversations based on the conditional filters set for the conversation session duration and the selected event.
      Feedback The Feedback Type options include:

      • NPS
      • CSAT
      • Thumbs-up/Down

      The Conditional Filter options include:

      • Less than
      • Less than Equals to
      • Greater than
      • Greater than equals to
      • Equals to

      The options for Score include:

      • NPS: Select a value between 0 and 10.
      • CSAT: Select a value between 0 and 5.
      • Thumbs-up/Down: Select either 0 or 1.
      Filters conversations based on the feedback type, conditional filter, and feedback score selection.
      Labels Select either all conversation labels or a specific configured label. Filters conversations based on the selected label(s).
      Custom Tags Select the key and type the value for the key to define the custom tag selection. You can combine multiple key-value pairs to define the custom tag selection. Filters conversations using custom tags added to the conversation for a key-value pair and the AND logical operator.
    5. Click Save.

The new custom filter is listed on the Filter Views page. The conversations are grouped and displayed Conversations History Dashboard based on the inputs provided on the Filter Views page.

Edit a Conversation Filter

You can edit one or more fields for an existing conversation filter. To edit a conversation filter, follow the steps below:

  1. Click the custom filter on the Filter Views page.
  2. Click the More Filters dropdown list on the Conversations History panel.
  3. Modify the required fields on the Edit Conversation Filter window.
  4. Click Apply.

Filter Criteria

You can customize the Conversations History data view by selecting the Filter Criteria on the dashboard. Please click here to view the available filters.

Conversations History Dashboard

The Conversations History Dashboard displays the following information for each conversation session that meets the defined filter condition(s) for the selected date range.

Containment Type

The following containment types affect the conversation flow and are displayed on top of individual Conversations History details panel:

  • Self-service: Indicates that the conversation (initiated by the user) with a VA was successfully completed.
  • Agent Transfer: Indicates that the conversation was transferred to a live agent using the Agent Transfer node in the Dialog Flow.
  • User Drop-off: Indicates that the user stopped participating in the conversation before it was completed, either due to an error in the flow or some other reason.

Label

A custom label helps identify conversations that require follow-up or indicate an action item for an analyst during review.

Add a Custom Label

To add a custom label in addition to the default label for a conversation, follow the steps below:

  1. Click the + Label button on the Conversations History panel for the required conversation session.
  2. In the Labels window, scroll down and click + Add.
  3. Enter the label name, and click the confirm icon.
    Note: You can select a different label color by clicking the color icon and using the color palette.
  4. Click Save.

Manage a Custom Label

Edit

You can edit or delete an existing custom label while adding a new label.

To edit a label, follow the steps below:

  1. Click the + Label button on the Conversations History panel for the required conversation session.
  2. In the Labels window, click the edit icon for the label you want to modify.
  3. Make the changes and click the confirm icon.
  4. Click Save.

Delete

To delete a label, follow the steps below:

  1. Click the + Label button on the Conversations History panel for the required conversation session.
  2. In the Labels window, click the delete icon for the label you want to remove.
  3. Click Save.

Other Conversation Parameters

The Channel, Language, Date, and conversation duration are displayed at the top of the Conversation History analytics panel.

Conversation Summary

  • User Messages: The number of messages sent by the user to the virtual assistant.
  • Bot Messages: The number of messages sent by the bot/virtual assistant to the user.
  • Intents Identified: The number of user intents identified by the virtual assistant during the conversation.
  • Intent Unidentified: The number of utterances that did not result in any intent identification during the conversation.
  • Tasks Completed: The number of tasks successfully completed by the virtual assistant.
  • Failed Tasks: The number of tasks that failed during the conversation.

Conversation Events

Conversation Events indicate the sequence of occurrences during a conversation triggered by customer inputs and responses while interacting with a bot. Each event can be categorized into regular and error-based occurrences. When analyzing a conversation flow, the user can identify the event type based on the following icons that are displayed for the relevant event.

The list of events triggered during a conversation are displayed below.

Intent Found: Triggered when the virtual assistant understands the user’s intent. The intent name identified is displayed.

Event Description
Intent Not Found Triggered when the virtual assistant is unable to understand the user’s intent.
Agent Transfer Triggered when a live agent transfer is initiated during the conversation.
Entity Retry Triggered when the input provided by the user is not identified by the virtual assistant and a input retry request to the customer.
Confirmation Retry Triggered when a confirmation request for a query or selection is generated from the virtual assistant to the customer.
On Connect Triggered every time a customer invokes Web/Mobile SDK (a conversation is initiated on the channel).
Sentiment Event Triggered when a customer’s sentiment is identified during the conversation. The user sentiment type identified is displayed.
Welcome Triggered on receiving a message from user when channel specific event is not configured.
Welcome Event Telegram Triggered on receiving a welcome event from Telegram.
Welcome Event Facebook Triggered on receiving a welcome event from Facebook Messenger.
Welcome Event Telephone Triggered on receiving a Telephone Call from any voice channel.
End Triggered on the closing of a conversation.
Debug Log Triggered when a debug log script runs for a script failure or service failure event.
Script Failure Triggered when a Script node failure occurs.
Service Failure Triggered when a service node failure occurs.
RCS Opt In Triggered on receiving Opt-In from the user for Rich Communication Services.
RCS Opt Out Triggered on receiving Opt-out from the user for Rich Communication Services.
User Message Triggered when a customer sends a message to the virtual assistant on the channel.

Enriched Chat Transcript

The Enriched Chat Transcript feature provides a more detailed view of the conversation, with all the events associated with each message displayed in the chat transcript slider. This can be useful for understanding the conversation at a granular level and identifying any issues that may have arisen. It can also help train the virtual assistant and improve its performance.

To view the Enriched Chat Transcript, enable the Show Events option (default setting) in the Chat History panel.

Note: Disabling the Show Events option will display only the chat transcript without the events.

The Event labels that appear under Conversation Events are displayed against each chat text in the chat transcript slider. Click here to learn more about Conversational Events.

 

Feedback User Type Label

For conversations with the customer response to a feedback survey, the feedback user type label is added automatically based on the analytics data. This label indicates if a customer is a promoter or a detractor.

Hovering the mouse on the label displays the following data:

  • Number of feedback responses collected.
  • Type of feedback survey.
  • Customer type (result generated internally after the feedback is submitted).
  • Feedback score.

User Details

To view the details of the agent that handled a conversation session, follow the steps below:

  1. Click either Conversation Summary or Conversation Event on the dashboard.
  2. On the landing page, click the User Details tab to view the following information:
    • User ID: The unique ID assigned to the agent.
    • Channel Data: The conversational channel where the interaction occurred.
    • Total Conversation Sessions: The total number of conversations the agent has handled for the selected period.
    • Sessions in the Last 30 Days: The number of conversations the agent handled in the date period that the used has selected within the last 30 days.
    • Last Interaction Date: The date of the agent’s most recent customer interaction.
    • User Meta tags: Used to identify important keywords in the conversation.

Chat History

The chat conversation flow between the virtual assistant and the customer is displayed in the Chat History panel, including events, actions, input requests, queries, and intent-based responses. Any failed tasks or exceptions that occurred during the conversation will also be displayed here.

The Enriched Chat Transcript is visible on the Chat History panel.

To view Chat History, follow these steps:

  • Click an entry under Conversation Summary or an event under Conversation Events on the Conversation History dashboard.

The Chat History window displays the conversation flow. In addition, the following information is displayed on the side pane:

  • Date Filter dropdown to select the period of Chat History.

Date-wise information summary on the following:

  • Conversation channel.
  • Chat initiation event.
  • Chat Duration
  • Chat Start time and End time.
  • Conversation summary of the following metrics:
    • User messages
    • Bot messages
    • Intents identified
    • Intents Unidentified
    • Tasks completed
    • Failed Tasks
  • Language (of interaction)
  • Event labels tagged to the conversation history.
  • Trace ID – A unique ID assigned to each incoming message. The Id is also included in all the logs maintained by the Platform. When you hover over the message, the info icon appears. Click the Info icon to view the Message Id associated with the message.
  • Click the Message Id to view the Trace ID associated with a message in the Chat History.
    Note: The Trace ID is retained in the logs for 30 days. Once the Trace ID is expired, you see a tooltip message as ‘Trace Id: Trace records for this message are not available‘.
  • You can see the “payload value” of the performed template action (e.g.: Button Click) in the individual message bubble and the “title” (e.g.: the selected button title) as a tag to the message bubble in the chat transcript. This is applicable only for WebSDK templates.
    Conversation with the Bot

    Conversation History

Define Alternate Text for JavaScript Messages

The Platform uses the{} JavaScript tag in the Chat History for bot messages and templates written using JavaScript. However, bot designers can now add a context-specific Alternate Text to JavaScript messages/templates they define and explain the purpose more clearly. The added Alternate Text is displayed alongside the JavaScript message tag in the Chat History for developers to get a better understanding of the message’s intent. 

The Conversation History API response includes a parameter messages.tags.altText which captures the Alternate Text value(s) configured in the JavaScript message or Web SDK template payload through the predefined function discussed below.

How It Works

  1. Developer uses a predefined function in the syntax tags.addAlternateText(“value”) to add the Alternative Text to a JavaScript message or Web SDK template on any channel, including a Webhook.
  2. The Alternate text indicating the JavaScript message/template’s purpose should be provided for the value parameter. For example, tags.addAlternateText(“Accounts Selection Message”).

Usage Example

For a bank account creation task, the Platform renders a template in the end channel to prompt the user for account type selection. This requires the developer to define a JavaScript message specific to the channel.

The developer can generate an Alternate text like “Accounts Selection Message,” in the template code to indicate that the JavaScript message is for account type selection.

After the end user selects an account type, the Alternate message appears in the Chat History above the {} JavaScript tag.

Important Considerations

  • You can define static and dynamic values for the alternate text.
  • Alternate text can be defined for JavaScript messages in user prompts, error prompts, Small Talk, standard responses, FAQs, and events.
  • The Platform assigns the latest to a message when you add multiple Alternate text values.
  • In the Chat History window, the Platform substitutes the payload label with an alternative text tag for all channel templates, excluding the SDK Template.

Message Tags

Message Tags help identify and categorize messages in the chat transcript. They add clarity and context to the conversation and can be reused across related conversations. System-defined message tags are provided by default, but users can create custom tags by defining a key-value pair. The key is used as an identifier for the specific message, and the value is the expected customer response to that message.

Important:

  • You cannot add the same key to a message again.
  • A custom message tag can only be added and detached from a message and not edited.

To add a custom message tag, follow the steps below:

  1. Hover over the message transcript in the conversation where you wish to add the message tag.
  2. Click +Message Tag.
  3. In the Add Message Tag window, enter the Key and Value in their respective text fields.
  4. Click Save. The new message tag is displayed below the message in the transcript slider.

Note: The custom message tag you create is available in the Custom Tags Filters section as one of the filtering criteria.

The Feedback Survey feature allows customers to provide feedback on their conversations with the virtual assistant.

If enabled, the customer’s response to the survey will be displayed in the chat transcript under Chat History.

The system captures and displays a feedback event label “End of Conversation: Survey Type” on the chat transcript, indicating the end of the conversation and the survey type.

The response will be mapped to a key-value pair for the conversation timeline, which can be useful for analyzing the conversation and customer experience at a granular level. This information is useful to improve the virtual assistant’s performance and enhance the customer experience.

The Conversation Summary displays the following information on the Feedback event:

  1. The Start Time and End Time, along with the real-time counts for the following:
  • User Messages
  • Bot Messages
  • Intents Identified
  • Intents Unidentified
  • Tasks Completed
  • Failed Tasks
  1. The Feedback Event is based on the event timeline with Key and Value.
  2. The total number of feedback responses collected for the session and the following:
  • Type of Feedback
  • Feedback response
  • Score

 

메뉴