This document describes how to configure Contact Center Enterprise (CCE) Agent Answers and Transcripts integrated with Google Contact Center Artificial Intelligence (CCAI).
Contributed by Ramiro Amaya Cisco TAC Engineer and Adithya Udupa, and Raghu Guvvala, Cisco Engineers.
Cisco recommends that you have knowledge of these topics:
- Cisco Unified Contact Center Enterprise (UCCE) Release 12.6
- Cisco Package Contact Center Enterprise (PCCE) Release 12.6
- Customer Voice Portal (CVP)
- Cisco Finesse 12.6
- Cisco Unified Border Element (CUBE) or Voice Gateway (GW)
- Google Dialogflow
- Control Hub
The information in this document is based on these software versions:
- UCCE Release 12.6
- CVP 12.6 ES6
- Cisco Finesse 12.6 ES 1
- Google Dialogflow
- Control Hub
- VCUBE - Cisco IOS XE Bengaluru 17.4
The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, ensure that you understand the potential impact of any command.
CCE 12.6 introduces the Agent Answers feature, in which an agent is provided with relevant suggestions and recommendations in real time for the agent to consider. The suggestions and recommendations are based on the conversation between the caller and the agent.
More often, agents lack the depth of knowledge about the products and services of the business they serve. Agent Answers enhances your experience because the timely suggestions improve the ability of the agent to respond. Businesses can cut down on training costs and time.
In addition CCE 12.6 also introduces Call Transcripts services that assist the agents by the use of Artificial Intelligence (AI) and Natural Language Understanding (NLU). These services are available for the agents in the Cisco Finesse desktop gadgets. The Call Transcript gadget dynamically converts the ongoing conversation to text and presents the text to an agent for real-time viewing and reference.
Note: In this release only Google Natural Language Processing (NLP) is supported.
Note: This feature is only supported in VCUBE, and CVP 12.6 ES6 is required in order to support of Agent Answers conference and Transfer.
Google Dialogflow agent needs to be created and the Knowledge base needs to be added before you start Agent Answers configuration. You require a Google service account, a Google project and a Dialogflow virtual agent. Then, you can add the knowledge base to the Dialogflow virtual agent.
What is a Dialogflow?
Google Dialogflow, is a conversational User Experience (UX) platform which enables brand-unique, natural language interactions for devices, applications, and services. In other words, Dialogflow is a framework which provides NLP / NLU (Natural Language Understanding) services. Cisco integrates with Google Dialogflow for Cisco Virtual Agent and for Agent Answers and Transcript .
What does this mean for you? Well, it means you can basically create a virtual agent on Dialogflow and then integrate it with Cisco Contact Center Enterprise.
if you need information on how to create a virtual agent or Dialogflow project, visit: Configure CVP CVA
These are the steps to add the Knowledge base to the Virtual Assistant Voice (VAV) known also as Cisco Virtual Agent (CVA).
Step 1. Log in to Dialoglfow Console, select the agent and click Knowledge: Dialogflow Console
Step 2. On the Knowledge Bases page, click CREATE KNOWLEDGE BASE, name the Knowledge base and click Save.
Step 3. Add a document or link to the knowledge base just created. Click Create the first one.
Step 4. On the Creation page, type the document name, select the Knowledge type, the Mime type and the Data Source.
Step 5. Click CREATE.
Step 6. Create a Google AI Profile.
1. Once the KB or FAQs are updated for Dialogflow agent, log in to Google Agent Assist and choose the project which is used for the KB/FAQs.
2. Select the Conversation profiles and click Create new as shown in the image.
3. Update these details while you create the conversation profile and click create.
- Display name – Give any name to identify the profile.
- Suggestion types – Based on what you have selected in the Knowledge Bases (KB) tab in Dialogflow User Interface (DF UI), click on that. It must be either FAQ or Articles.
- Once you do this, all the KBs created in DF UI page, appears here automatically. Select the correct one.
- Updated some of the other mandatory fields like Sentiment Analysis or update the default values based on the requirement like confidence threshold or maximum suggestions, and so on.
- Now the conversation profile appears on Agent Assist url.
- Copy the Integration ID. Click Copy to Clipboard. This is used later in the Control Hub configuration.
Note: There is no Dialogflow configuration required for Call Transcripts
Webex Control Hub Configuration
Create a CCAI configuration in Cisco Webex Control Hub at Control Hub . A CCAI configuration leverages CCAI Connectors to invoke the CCAI services. For details, visit the Configure Contact Center AI article at Webex Help Center
Step 1. Ensure that the Cloud Connect publisher and subscriber are installed. For more information, visit the Install Cloud Connect section in Cisco Unified Contact Center Enterprise Installation and Upgrade Guide.
Step 2. Log in to Webex Control Hub. Navigate to Contact Center and click Cloud Connect.
Step 3. On Cloud Connect window enter the name and the Fully Qualified Domain Name (FQDN) of Primary Cloud connect.
Step 4. On Cloud Connect window enter the name and the FQDN of Primary Cloud connect and click Register.
Step 5. Add a Connector. On the Contact Center window select the Connectors tab.
Step 6. If a connector is already added and you need to add one more, click on Add More. Sign in with Google and continue with the instructions.
Step 7. Now add the features. On the Contact Center page, click Features and click New.
Step 8. You are now in the Create a New Contact Center Feature page. Click Contact Center AI Config.
Step 9. Provides the feature information, select the connector already added and the Google Profile created.
Step 1. On UCCE AW, open Cisco Web Administration tool and navigate to Inventory. Click New.
Step 2. Add Cloud Connect and provide the FQDN and credentials.
Note: Refer to these documents for PCCE certificate exchange: Self-Signed Certificates in a PCCE Solutions and Manage PCCE Components Certificate for SPOG. For UCCE refer to Self-Signed Certificate Exchanged on UCCE.
Step 3. Configure Cloud Connect in the CVP Operations Console (OAMP). For details visit the section Configure CVP Devices for Cloud Connect in the Administration Guide for Cisco Unified Customer Voice Portal.
Note: This is for UCCE only. This step is not required for PCCE.
Step 4. Import the Cloud Connect certificate to the CVP server. For details, visit the section Import Cloud Connect Certificate to Unified CVP Keystore in the Configuration Guide for Cisco Unified Customer Voice Portal.
Step 5. In the Unified CCE Administration console, do the this to associate the CCAI configuration all call types:
Note: Ensure that the AW (SPOG) on PCCE and OAMP on UCCE have open communication to *.wbx2.com and *.ciscoccservice.com
- On AW Web Administration tool, navigate to Features and select Contact Center AI.
2. On the Contact Center AI page select the CCAI configured before in Control Hub.
Step 6. To apply the CCAI configuration to only a subset of the call types or to override the global configuration for specific call types do this:
1. In Web Administration tool, navigate to Route Settings and select Call Type.
2. Click the Contact Center AI tab and select the Contact Center AI configured on the Control Hub.
Note: Steps 1 to 3 are for UCCE only. For PCCE start with Step 4.
Step 1. Provision Cloud Connect on Cisco Finesse. For more information, visit the Cloud Connect Server Settings topic in the Cisco Finesse Administration Guide.
Step 2. Open Finesse Admin page, and navigate to settings and to Cloud Connect.
Step 3. On the Cloud Connect Server Settings provide the credentials and the FQDN of the publisher and the subscriber.
Step 4. Add the Agent Answers gadget on the Finesse Desktop Layout. On the Cisco Finesse Administration Page, click Desktop Layout and remove the comment on the gadget information related to Agent Answers.
Step 5. On CCE Administration Page select Agents and on Manage Agents enable the CCAI services. Once enabled, the Agent Answers gadget appears on the Home tab and displays relevant articles and suggestions during a call. For details on how to use the gadget, visit the Contact Center AI Gadgets guide. Gadget auto-hide/un-hide and notifications capability is available only if the gadget is configured as a multi-tab gadget in Cisco Finesse. For more details, visit Agent Answers Gadget in the Cisco Finesse Administration Guide.
VCUBE and CVP Configuration
Step 1. On VCUBE, enter to config mode.
Step 2. Create a Voice Class Sip profile to add Call-Info SIP header in INVITE message for CVP to send forking request.
voice class sip-profiles 100
request INVITE sip-header Call-Info add "X-Cisco-Forking: supported"
Step 3. Create a media stream service profile.
media profile stream-service 99
connection idle-timeout 45 ! default 30 mins
connection calls-threshold 5 ! default 3 calls per websocket connection
proxy host proxy.dk.org ! optional, http proxy server IP or DNS if used
source-ip A.B.C.D ! VCUBE source IP for websocket sessions
secure-ciphersuite aes-128-cbc-sha ! optional, VCUBE advertises all cipher suites if not specified.
Step 4. Associate media stream service profile to a media class.
media class 9
stream-service profile 99
Step 5. Add the sip and media profile to the outgoing dial-peer towards CVP.
dial-peer voice 802 voip
description CVP SIP Comprehensive dial-peer
session protocol sipv2
session target ipv4:X.X.X.X
voice-class codec 1
voice-class sip profiles 100
Step 6. Only if your CUBE supports SIP Info forking, In CVP Server sip.properties file set the SIP.UseSIPINFOForking to true. If CUBE responds with a "415 unsupported media type" error when the SIP INFO Forking request is sent by CVP, leave this parameter SIP.UseSIPINFOForking as the default (false).
There is currently no verification procedure available for this configuration.
There is currently no specific information to troubleshoot available for this configuration.