시작
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. How Tos
  4. Travel Planing Assistant
  5. Travel VA: Using Traits

Travel VA: Using Traits

In this How-To, we will explore a scenario in a Travel Planning Assistant, where traits can be used to steer the conversation flow in a more natural and predictable direction. For details on what Traits are and how they are implemented in the Kore.ai XO Platform, please refer here.

Problem Statement

Consider the cases where the user is trying to report an issue or ask a question pertaining to “Make a Booking”. The VA might trigger the “Make a Booking” intent as opposed to “Issue Resolution”. The problem that may arise in this scenario is that the user is presented with a response that is not relevant to their utterance.

In this document, we will show how Traits can be used to identify such situations and take appropriate action.

Prerequisites

To go through these configurations, you need to know at least the basics of building a Virtual Assistant. This is because your assistant needs to have been already built when you begin working on your forms.

In addition, your VA requires the following configurations:

  • Book a Flight Dialog Task – This task allows the user to make a flight booking via the assistant.

  • Issue Resolution Dialog Task – This task assists in any issues faced by the user. It displays a regret message and transfers the conversation to a Live Agent.

  • Knowledge Graph Booking FAQ – A Booking node with an FAQ for How do I make a Booking?

Implementation

Intent Detection using Traits

We will be using Trait to steer the conversation to “Issue Resolution” when the word “issue” is present in the User Utterance.

Steps:

  1. Select Build tab from the top menu
  2. From Natural Language -> Training select the Traits tab.
  3. Click Add New Trait. We will be using a trait to identify the existence of the word ‘issue’ in the user utterance.
    1. Add a Trait Type as Problem Statement, and Traits as issue. A given Trait Type can have multiple Traits grouped together logically.
    2. Optionally you can add utterances for Issues as ‘problem’, ‘unable to’, and ‘not working’. These are the alternate words that users might use to indicate an issue.
    3. Save & Add Rule 
  4. We will be defining the intent that needs to be triggered in the presence of this Issue trait.
    1. Select IntentIssue Resolution to be triggered in the presence of this trait.
    2. Add the Trait Rulesissue as the trait that should trigger the above selected intent.
    3. Save the Trait Mapping
  5. Train the Traits.
  6. Open the Issue Resolution Intent to see the Trait Rules under the NLP properties panel updated with the issue trait.
  7. Talk to the Bot and see the conversation flow. As you can see in the illustration below, rather than detect the Make a Booking intent, the VA uses the Issue Resolution task to transfer the conversation to an agent. This is despite the fact that the user utterance contains the full Make a Booking sentence. The VA picks up on the presence of an utterance which we have set up under the Issue trait – the word problem – and thus triggers the intent that we selected as the rule, rather than the other one. 

Knowledge Intent using Traits

Here we will see how to drive the query from the user to the appropriate FAQ instead of the dialog task.

Steps

  1. From Natural Language > Training open the Traits dialog.
  2. Click Add New Trait. We will be using a trait to identify the existence of questions in the user utterance.
    1. Add a Trait Type as Inquiry, and Traits as ask. A given Trait Type can have multiple Traits grouped together logically.
    2. Optionally you can add utterances for Issues as ‘wondering’,  and ‘want to know’. These are the alternate words that the user might use to indicate an inquiry.
    3. Save & Exit the Trait.
    4. Train the Trait.
  3. Associate the Trait to the FAQ
    1. Open the Knowledge Graph and hover over the node with the question pertaining to Booking.
    2. Click the Settings or gear icon.
    3. Under Traits type and select the ask trait.
    4. Train the Knowledge Graph.
  4. Talk to the bot and say I want to make a booking. You will see that the assistant is still detecting the Make a Booking intent.
  5. To understand the reason behind this:
    1. Open Testing > Utterance Testing.
    2. Type the utterance, you will see that the Trait has been identified.
    3. Select the Ranking and Resolver. You will see that both the intent and FAQ were identified but the intent got a higher score.

  6. To ensure that the intent is not selected, we will add a Negative Pattern to the Book Flight intent.
    1. Go to Build > Conversation Skills > Dialog Tasks and select the Book Flight task.
    2. Select the primary intent node and go to its NLP Properties
    3. Under Patterns click Add Pattern.
    4. Select the Negative Patterns tab. Add the words know, ask, any any other question identifiers.This will ensure that the ‘Book Flight’ intent is not identified when either of the negative patterns is present in the user utterance.

Check the Utterance Training and ensure that the Book Flight intent is rejected because of the negative pattern. Finally, Talk to the Bot and test the changes.

Travel VA: Using Traits

In this How-To, we will explore a scenario in a Travel Planning Assistant, where traits can be used to steer the conversation flow in a more natural and predictable direction. For details on what Traits are and how they are implemented in the Kore.ai XO Platform, please refer here.

Problem Statement

Consider the cases where the user is trying to report an issue or ask a question pertaining to “Make a Booking”. The VA might trigger the “Make a Booking” intent as opposed to “Issue Resolution”. The problem that may arise in this scenario is that the user is presented with a response that is not relevant to their utterance.

In this document, we will show how Traits can be used to identify such situations and take appropriate action.

Prerequisites

To go through these configurations, you need to know at least the basics of building a Virtual Assistant. This is because your assistant needs to have been already built when you begin working on your forms.

In addition, your VA requires the following configurations:

  • Book a Flight Dialog Task – This task allows the user to make a flight booking via the assistant.

  • Issue Resolution Dialog Task – This task assists in any issues faced by the user. It displays a regret message and transfers the conversation to a Live Agent.

  • Knowledge Graph Booking FAQ – A Booking node with an FAQ for How do I make a Booking?

Implementation

Intent Detection using Traits

We will be using Trait to steer the conversation to “Issue Resolution” when the word “issue” is present in the User Utterance.

Steps:

  1. Select Build tab from the top menu
  2. From Natural Language -> Training select the Traits tab.
  3. Click Add New Trait. We will be using a trait to identify the existence of the word ‘issue’ in the user utterance.
    1. Add a Trait Type as Problem Statement, and Traits as issue. A given Trait Type can have multiple Traits grouped together logically.
    2. Optionally you can add utterances for Issues as ‘problem’, ‘unable to’, and ‘not working’. These are the alternate words that users might use to indicate an issue.
    3. Save & Add Rule 
  4. We will be defining the intent that needs to be triggered in the presence of this Issue trait.
    1. Select IntentIssue Resolution to be triggered in the presence of this trait.
    2. Add the Trait Rulesissue as the trait that should trigger the above selected intent.
    3. Save the Trait Mapping
  5. Train the Traits.
  6. Open the Issue Resolution Intent to see the Trait Rules under the NLP properties panel updated with the issue trait.
  7. Talk to the Bot and see the conversation flow. As you can see in the illustration below, rather than detect the Make a Booking intent, the VA uses the Issue Resolution task to transfer the conversation to an agent. This is despite the fact that the user utterance contains the full Make a Booking sentence. The VA picks up on the presence of an utterance which we have set up under the Issue trait – the word problem – and thus triggers the intent that we selected as the rule, rather than the other one. 

Knowledge Intent using Traits

Here we will see how to drive the query from the user to the appropriate FAQ instead of the dialog task.

Steps

  1. From Natural Language > Training open the Traits dialog.
  2. Click Add New Trait. We will be using a trait to identify the existence of questions in the user utterance.
    1. Add a Trait Type as Inquiry, and Traits as ask. A given Trait Type can have multiple Traits grouped together logically.
    2. Optionally you can add utterances for Issues as ‘wondering’,  and ‘want to know’. These are the alternate words that the user might use to indicate an inquiry.
    3. Save & Exit the Trait.
    4. Train the Trait.
  3. Associate the Trait to the FAQ
    1. Open the Knowledge Graph and hover over the node with the question pertaining to Booking.
    2. Click the Settings or gear icon.
    3. Under Traits type and select the ask trait.
    4. Train the Knowledge Graph.
  4. Talk to the bot and say I want to make a booking. You will see that the assistant is still detecting the Make a Booking intent.
  5. To understand the reason behind this:
    1. Open Testing > Utterance Testing.
    2. Type the utterance, you will see that the Trait has been identified.
    3. Select the Ranking and Resolver. You will see that both the intent and FAQ were identified but the intent got a higher score.

  6. To ensure that the intent is not selected, we will add a Negative Pattern to the Book Flight intent.
    1. Go to Build > Conversation Skills > Dialog Tasks and select the Book Flight task.
    2. Select the primary intent node and go to its NLP Properties
    3. Under Patterns click Add Pattern.
    4. Select the Negative Patterns tab. Add the words know, ask, any any other question identifiers.This will ensure that the ‘Book Flight’ intent is not identified when either of the negative patterns is present in the user utterance.

Check the Utterance Training and ensure that the Book Flight intent is rejected because of the negative pattern. Finally, Talk to the Bot and test the changes.

메뉴