Skip to main content

Documentation Index

Fetch the complete documentation index at: https://koreai.mintlify.app/llms.txt

Use this file to discover all available pages before exploring further.

Agent AI integration in Genesys supports multiple bots and queue-based functionality, improving on the earlier single AI Agent and department-specific approach. This allows Genesys Cloud CX to offer a flexible and scalable solution for businesses seeking to leverage AI to improve agent efficiency and customer satisfaction across multiple departments.
This integration process also works for Genesys Desktop App.

Definitions

Section/GroupKeyDefinitionReference
Generate Oauth ID to enable Kore Services to Connect with Genesys
+
Create an Interaction Widget in Genesys for Agent AI
Agent AI URLThe domain of the Agent AI.- If it’s legacy Agent AI, URL is https://agentassist.kore.ai
- If it’s AI for Service, refer to the Getting Started doc and use an appropriate URL.
- If it’s on-prem, the URL points to the origin where your Agent AI runs.
Client AppTo use any Kore AI Agent SDKs, you must create a client app to get the authentication credentials to communicate between the Kore AI Agent and Agent AI.
Note: The system supports only the default Client App.
adding-the-webmobile-client-channel
Create an Interaction Widget in Genesys for Agent AICustom Data / x_passthru_metadataUse this to pass information to Kore AI Agent.
Capture AI Agent Information in Kore Data TableSecure Custom Data / KvpConfigUse this to pass sensitive information to Kore AI Agent.json-web-encryption-jwe
Create an Interaction Widget in Genesys for Agent AIInteraction WidgetThe Interaction Widget displays the Agent AI iframe within the Genesys Agent Desktop.set-up-an-interaction-widget-integration
Create an Interaction Widget in Genesys for Agent AIInteraction Widget URL params- multibot=true represents usage of new version of Agent AI integration that supports agent specific AI Agent.
- x_metadata - URL-encoded JSON containing the data that Kore Middleware service needs.
- x_passthru_metadata - Optional, can be JWE/JWT/base64/URL-encoded JSON stored as custom data.
x_metadata JSON object structure:
{“datatable”:{“name”:“<datatable name>”,“token”:“<jwt token>”,“qDelimiter”:“<Paste the special character used in the queue name>“}}
Capture AI Agent Information in Kore Data TableBotIdA unique identifier assigned to an AI Agent.Agent AI > Flows & Channels > Digital > Web/Mobile Client > JWT App Details
Capture AI Agent Information in Kore Data TableClientIdAn identifier provided to a client application.Agent AI > Flows & Channels > Digital > Web/Mobile Client > JWT App Details
Capture AI Agent Information in Kore Data TableClientSecretA secret key or password associated with the ClientId.Agent AI > Flows & Channels > Digital > Web/Mobile Client > JWT App Details
Capture AI Agent Information in Kore Data TableAgentAssistWidgetURLURL that points to the Agent AI widget.
For example: https://agentassist.kore.ai/koreagentassist-sdk-v3/UI/agentassist-iframe.html
Agent AI > Flows & Channels > Digital > Web/Mobile Client > JWT App Details
Capture AI Agent Information in Kore Data TableAudiohookEnabledA setting or flag indicating whether Kore audio processing runs for the AI Agent.Set to true to turn on Kore audio processing, or false to turn it off.
Capture AI Agent Information in Kore Data TableQueueIdentifierA unique identifier in the Data Table to fetch AI Agent details at run time.
Capture AI Agent Information in Kore Data TableKvpConfigThe key-value pairs (KVPs) to include in SecureCustomData. JSON object containing the necessary keys and xpath (paths to locate the value in Genesys Conversation API result JSON object). Genesys API Explorer
Note: Optional column. You need it to send secure custom data to Agent AI.
Sample:
{
”queueName”: “participants[0].queueName,"
"callStatus”: “participants[0].calls[0].state”}
Capture AI Agent Information in Kore Data TableJWEPublicKeyPublic key assigned to the Client App.Agent AI > Flows & Channels > Digital > Web/Mobile Client > JWT App Details
Capture AI Agent Information in Kore Data TableRSPrivatePemThe Private Key that corresponds to the Public Key supplied during the creation of a Client App using the RS256 or RS512 algorithm.RSPrivatePemKey is an optional column, and you need it only when the algorithm is RS256 or RS512.
(Not supported)
Capture AI Agent Information in Kore Data TableAlgorithmAlgorithm assigned to the Client App.The value must be HS256.
Install Audiohook for Voice StreamingVoice GatewayFor the US region, value is savg-webserver.kore.ai.
For on-prem, refer to corresponding host.

Architecture Diagrams

Chat architecture-diagram-chat Voice architecture-diagram-voice

Interaction Sequence

interaction-sequence This document provides detailed, step-by-step instructions for setting up the integration of the Agent AI widget in the Genesys environment.

Activities on Platform

Activities on Genesys Cloud

Chat Setup

Voice Setup

Prerequisites

  • Genesys Administrator with access to a Genesys Cloud account with Admin rights.
  • Platform Administrator with access to Agent AI instance.

Capture AI Agent Information

Genesys Data Table

This step involves creating a Genesys Data Table with Agent AI bot details.
The Custom Fields of the Data Table store the configuration data, not the Data Table row. A single Data Table represents a configuration of AgentAssist. The default values of the Custom Fields contain the necessary configuration data to load the AgentAssist widget.
  1. Sign in to Genesys Cloud.
  2. Go to Admin > Architect > Data Tables. architect-data-tables
  3. Create a new Data Table by clicking + Add:
  4. Enter a relevant name, such as KoreaiAA-configuration, and then click Save. create-data-table
    You must set the Reference Key label to agentAssist. The Interaction Widget uses this value to load the configuration data.
    1. Click the pencil icon to edit a data table. pencil-icon
      Don’t click on the data table name.
  5. Click Add Field under Custom Fields to create five custom fields to provide the AgentAssist configuration. Set the data type of all custom fields as String. custom-fields-add-field add-field-string
  6. Add the custom fields with Bot details. bot-details
  7. Follow these conventions in the table for other custom fields. Use the exact names, including upper/lower case.
Get these values in the Agent AI > Flows & Channels > Channels > Digital > Web/Mobile Client > JWT App Details section.
Field LabelDefault Value
AgentAssist URLAgent AI URL
Bot Idst-8cb94691-xxxx-xxxx-xxxx-xxxxxxxx
Client Idcs-b60f544d-xxxx-xxxx-xxxx-xxxxxxxxxxxx
Client Secret<secret-key from AgentAssist>
is Audiohook Enabledtrue / false
  1. All custom fields require the string type.
  2. When is Audiohook Enabled is set to false, the application uses the Genesys native transcription service through the Transcriptions API.
To change the values, click the gray box surrounding each Custom Field, not directly on the text box. enable-audiohook

Third-Party Configuration

Third-Party Configuration maps Agent AI bots to specific queues. Within this configuration, you can define the bot’s language, custom data configuration, or secure custom data configuration. For example, if you want to associate Agent AI Bot1 with Queue1 and Agent AI Bot2 with Queue2, you need to:
  • Create a record in Third Party Configuration for Agent AI Bot1, setting the Queue Identifier as Queue1.
  • Create a record in Third Party Configuration for Agent AI Bot2, setting the Queue Identifier as Queue2.
This setup ensures that the correct Agent AI widget renders for conversations in the defined queues.
  • The system doesn’t support Custom Data.
  • You can’t map one queue to multiple Agent AI bots.
Refer to this doc for instructions on creating records in Third-Party Configuration for an Agent AI Bot. Example: You have a queue named Chat_Skill that handles incoming chat requests, and you want the Agent AI widget to render to this queue. You must create the following details of the Third-Party Configuration record in your Agent AI account: create-record add-value
Encode all values in base64.
third-party-configuration
Verify that Third Party Configuration is turned on in Widget Settings > Agent AI General Settings.

Kore Data Table

Data Tables store queue-specific AI Agent credentials. Each record in the Kore Data Table represents a unique Genesys agent queue and its corresponding AI Agent definitions. If you use a single AI Agent for several queues, create a record and insert the queue names, separated by commas, as the value for the QueueIdentifier, along with the AI Agent details. Kore matches the third-party queue name with the QueueIdentifier credential name in its AI Agent credentials to render the appropriate AI Agent.
  • The system fetches AI Agent credentials based on Genesys desktop queue names. If the Genesys queue name is of the <QUEUEIDENTIFIER><QDELIMITER>XXXXX format, for example ALPHAINC_CUSTOMERSERVICE_16092024, then:
  • QueueIdentifier = ALPHAINC and qDelimiter = _.
  • Update the QueueIdentifier in the Kore Data Table.
  • Update the qDelimiter in the Create an Interaction Widget in Genesys for Agent AI section.
Don’t enter multiple records with different AI Agent credentials in Kore Data Table for a single QueueIdentifier.

How to create a new Data Table

  1. Sign in to AI for Service.
  2. Click Data > Data Tables.
  3. Click New Table. new-table
  4. Enter the following details in the New Table page:
    1. Name of the Data Table (any alphanumeric name).
    2. Description of the Data Table.
    3. Columns to include in the Data Table. Click the check mark to add multiple columns. multiple-columns Add the following case-sensitive columns with type string: Mandatory Columns:
      • QueueIdentifier (unique identifier for the table)
      • BotId
      • ClientId
      • ClientSecret
      • AgentAssistWidgetURL
      • AudiohookEnabled
      • JWEPublicKey
      Optional Columns:
      • KvpConfig
      • Algorithm (HS256)
      • RSPrivatePem (Ignore/Not Supported)
      • isAgentAISDK
    4. Indexes for the table.
      • Index Name for reference.
      • Is Unique flag to define if the index contains unique values. (Turn on is Unique.)
      • Column & Sort Order - List of columns to include in the index; you can select multiple columns and specify the sorting order (ascending or descending) for each column. (Select QueueIdentifier with ascending order.) queue-finder
    5. AI Agent Assignments (not applicable).
    6. App Assignments to let apps access data in this table.
      1. Select any app from the list, or click Create New App and enter your app name: create-new-app
      2. Select the Read, Write, and Delete permissions, as required.
        You can also create new apps by clicking Data > Apps > New App in the home page:
        apps-new-app
    7. Process Assignments (not applicable).
  5. Click Create to create the new data table.

Insert data into Data Table

Set up necessary permissions and app assignments and insert AI Agent-specific data into the Data Table.
  1. Sign in to AI for Service.
  2. Click Data > Apps.
  3. Select the App with write access to the Data Table where you want to add information.
  4. Copy Client ID and Client Secret of the App. app-write-access
  5. Create a JWT Token using the Client ID and Client Secret by following this doc.
  6. Insert the following data into the Data Table by following this doc. Use the JWT Token you created. API Body Payload Structure:
    {
        "data": {
            "QueueIdentifier": <Unique QueueIdentifier>,
            "BotId": <Kore BotId>,
            "ClientId": <Kore ClientId>,
            "ClientSecret": <Kore ClientSecret>,
            "AudiohookEnabled": `true` / `false`,
            "AgentAssistWidgetURL": <Kore Agent AI Widget URL>,
            "KvpConfig": <KVPs of SecureCustomData>,
            "JWEPublicKey": <Public Key assigned to Client App>,
            "Algorithm": "HS256"
        }
    }
    
  • For a single queue, the QueueIdentifier value contains one queue name (for example, Kore). For multiple queues, it includes all the queue names separated by commas (for example, Kore, KoreSupport).
  • JWEPublicKey and KvpConfig values must be JSON objects converted to strings.
Single Queue Example single-queue-example Multiple Queues Example multiple-queues-example

Generate Oauth ID to enable Kore Services to Connect with Genesys

Steps to get Genesys OAuth ID:
  1. Sign in to Genesys Cloud.
  2. Go to Admin > Integrations > OAuth. single-queue-example
  3. Click Add Client.
  4. Enter the app name, description, and token duration in the App Name, Description, and Token Duration fields.
  5. Select Token Implicit Grant (Browser) in the Grant Types section. token-implicit-grant
  6. Add {Agent AI URL}/koreaiaa-genesys/ in the Authorized redirect URIs field.
  7. Add the following list of scopes in the Scope section:
    • conversations
    • conversations:readonly
    • integrations
    • integrations:readonly
    • messaging
    • messaging-platform
    • messaging-platform:readonly
    • messaging:readonly
    • notifications
    • user-basic-info
    • web-chat
    • web-chat:readonly
authorized-redirect-uris After saving the configuration, you get the Client Id of the OAuth client. Copy the ID and have it available for the next step.

Create an Interaction Widget in Genesys for Agent AI

Create a new Interaction Widget. The Genesys Agent Desktop hosts this widget, and it provides the Agent AI solution features to agents. Steps to create an Interaction Widget:
  1. Sign in to Genesys Cloud.
  2. Click Admin > Integrations.
  3. If you haven’t created an Interaction Widget for Agent AI, install a new Interaction Widget by clicking the Integrations tab. genesys-cloud-integrations interaction-widget
  4. Name the Interaction Widget with a meaningful name, such as KoreaiAA Interaction Widget.
  5. Open the Interaction Widget by clicking the name.
  6. Go to the Configuration tab of the Interaction Widget. interaction-widget-configuration
  7. In the Application URL field, enter the following structure:
    {Agent AI URL}/koreaiaa-genesys/?conversationid={{gcConversationId}}&lang={{gcLangTag}}&environment={{gcHostOrigin}}&genesysid=<genesys-oauth-Id>&x_passthru_metadata=<Token>&showWidget=true/false&sendEventsToVG=true/false
    
    • x_passthru_metadata is an optional query parameter that you need to pass custom data to Agent AI.
    • showWidget: Determines whether the Agent AI widget appears during agent transitions.
      • Set to true to display the widget for Agent 1, if Agent 1 exits and Agent 2 takes over the conversation.
      • Set to false if you don’t want the widget to appear during these transitions.
    • sendEventsToVG: Determines whether the system sends events to VG to pause or resume transcriptions when agents put a call on hold or resume it. This helps reduce Automatic Speech Recognition (ASR) costs by avoiding transcription of hold music from Genesys.
      • Set to true to allow the new Audiohook flow for transcriptions, which uses the configurations under the Advanced Settings.
      • Set to false to continue using the old Audiohook flow for transcriptions.
Add the following parameters to the Application URL based on how you store bot details: Kore Data Table: &multibot=true&x_metadata=<?x=%7B%22datatable%22%xxxxx> The x_metadata value equals the URL-encoded string of JSON object. Third Party Configuration: &accountId=<bot-account-id> You can fetch the accountId from the Agent AI > Flows & Channels > Digital > Web/Mobile Client > JWT App Details page. The x_metadata value equals the URL-encoded string of the JSON object.
  1. For the oauthId value, use the OAuth ID from the Generate Oauth ID section.
  2. Build x_metadata:
    1. Sign in to AI for Service.
    2. Click Data > Data Tables, and copy the Data Table name:
    3. Click Apps, and click one of the app names with read access: click-apps-read-access
    4. Copy the Client ID and Client Secret values.
    5. Create a JWT Token using the Client ID and Client Secret by following this doc.
    6. Generate a JSON object with the following structure, and then convert it into a URL-encoded string:
      {
       "datatable": {
         "name": <paste datatable name>,
         "token": <paste token created in previous step>,
         "qDelimiter": <Paste the special character used in the queue name to distinguish the QueueIdentifier from the remaining part of the queue name>
       }
      }
      Website for url encoding - urlencoder
      
      Reference: java-script-demo
    7. Copy the URL-encoded string and paste it as the x_metadata value.
  3. Allow all permissions in iFrame Sandbox Options and iFrame Feature/Permission Policy: iFrame Sandbox Options: allow-forms,allow-modals,allow-popups,allow-presentation,allow-same-origin,allow-scripts,allow-downloads. iFrame Feature/Permission Policy: camera,microphone,geolocation,clipboard-write,display-capture,fullscreen. Communication Type Filtering: chat and call.

Provide Interaction Widget access to agents

To view the Interaction Widget, agents must have the following accesses:

Group Membership

An Interaction Widget uses Group Membership to determine who can view it on the agent desktop.
  1. Use an existing group, if your agents are already part of it. Otherwise, create a new group for Agent AI permission.
  2. Name the group KoreAA-Agents or a similar name to distinguish it.
  3. Add any agent to allow them to use the Agent AI functionality. You can use multiple groups.
  4. Go back to the Integrations section and open the Interaction Widget you created in the Create an interaction widget section.
  5. On the Configuration tab, add access using the group you identified or created for Agent AI in the Group Filtering option. You may also use Queue Filtering (optional). group-filtering

Custom Role/Permission

along with the basic agent role, add the following role:
  1. Sign in to Genesys Cloud.
  2. Go to Admin > People & Permissions > Roles / Permissions.
  3. Click Add Role to create a new role.
  4. Give a distinctive name to the role; for example, KoreaiAA Agent.
  5. On the Permission tab, search for Conversation > Transcription > View, and add (select the box):
    The Conversation permission is available only in the CX3 license.
    The Assigned Permissions view looks like the following image: assigned-permissions
  6. Click the three dots at the right end of the Permission role, and select Change Membership. Add the appropriate agents to the role.

Create a Queue in Genesys

  1. Sign in to Genesys Pure Cloud.
  2. Go to Admin > Contact Center > Queues, or enter queues in the search bar under the Admin section and press the Enter key.
  3. Click Create Queue. An empty page to create a new queue appears on the right side of the page. create-queue
  4. Enter/select the following details in the Create Queue page:
    • Name: Enter a unique name for the new queue.
    • Division: Select a division in which you want to place this queue.
    • Copy settings and members from (Optional): Select an existing queue name, if you want to copy the settings and members from it.
    • Peer Id (optional): Enter a unique ID the system can use to identify the queue from an external platform. peer-id
  5. Click Save.

Enabling the Audio Monitoring toggle

To stream audio to third-party services, follow these steps:
  1. Sign in to Genesys Pure Cloud.
  2. Go to Admin > Contact Center > Queues, or enter queues in the search bar under the Admin section and press the Enter key.
  3. Click the intended queue name.
  4. Click the Voice tab.
  5. Turn on the Audio Monitoring toggle. audio-monitoring-toggle Audio Monitoring: Voice settings on a Queue have an additional Audio Monitoring option, separate from Voice Transcription. This gives you control over which features you turn on. Audio Monitoring activates in the queue only if your organization activates Audiohook Monitor.

Chat Setup

Create/Update Architect Inbound Message Flow in Genesys for the Agent Queue

This step manages incoming messages to the Genesys platform. When you initiate a chat from the web chat messenger, Genesys routes it to this inbound message flow first.

Steps to create a chat architect flow

  1. Sign in to Genesys Cloud.
  2. Go to Admin > Architect > Architect.
  3. Click the three dots next to Flows: Inbound Call, and select Inbound Message. inbound-message
  4. Click +Add to create an Inbound Message Flow.
  5. Click Create Flow. The final architect flow looks like the following screenshot: create-flow
  6. Click Publish.

Create Messenger Configuration

Before using web messaging, you must configure it in Genesys Cloud. To configure Web or Mobile Messaging in your organization, follow these steps:
  1. In Genesys Cloud, go to Admin > Message > Messenger Configurations.
  2. Click New Configuration.
  3. Enter a name and description. messenger-configuration-name-description
  4. Click the Appearance tab and complete the following information:
    • Under Select your Supported Languages, click the Select language(s) list and choose the languages that you want to support in the Messenger interface.
      You must configure the same language in Kore AI Agent.
      select-supported-languages
    • Under Select Default Language, click the Select language list and choose the default language. default-language
    • Adjust the other settings according to your preferences.
  5. Click the Apps tab and complete the following steps:
    • Under Clear Conversation, turn the toggle on. You need this for the Agent AI Conversation Summary feature to work. clear-conversation-toggle
    • Adjust the other settings according to your preferences.
  6. Click Save New Version to create a new version.

Create Messenger Deployment

To deploy the Messenger snippet to your website, follow these steps:
  1. In Genesys Cloud, go to Admin > Message > Messenger Deployment.
  2. Click New Deployment.
  3. Enter a name and description.
  4. Under Select your Configuration, click Select Configuration to select a version of a Messenger configuration you created in the previous step to assign to this deployment.
    • In the Assignment pane, navigate to the Messenger configuration you want to assign to the configuration, and click the name of the Messenger configuration.
    • Select the version that you want to assign.
    • Click Save.
  5. Under Restrict domain access, determine whether to allow all domains or restrict the domains on which you want to deploy the snippet.
    • To allow all domains, select Allow all domains. (Use this option for testing and development purposes.)
    • To restrict domains, enter a domain and click Add Domain. You can add multiple domains to the list. Restrict domains to prevent unauthorized usage of your snippet from unknown domains. If you restrict a domain, Messenger doesn’t run on that website and rejects API requests from that domain.
  6. Under Select your Architect Flow, select the inbound message flow created in the previous steps.
  7. Click Save. The Messenger Deployments page now displays the snippet and the deployment key.
  8. Copy the Messenger snippet and deploy the Messenger snippet to your website.
    • If you are building a custom Messenger, copy the deployment key.
      The Messenger window appears after the website page loads.

(Optional) Install Audiohook for Voice Streaming

Install Audiohook for voice streaming if using Kore-managed transcriptions.
  1. In Genesys Cloud, go to Admin > Integrations > Integrations.
  2. Enter audiohook in the search bar. Audiohook integration requires specific configuration values to support Agent AI configuration.
  3. Install a new audiohook app by clicking Integrations on the upper-right corner.
  4. Open the Audiohook, and go to the Configuration tab.
    1. Channel value should be both.
    2. The Connection URI format should be similar to wss://{Voice Gateway}/audiosocket/genesys/?sipuri=xxx&token=xxx&botId=xxx&accountId=xxx&agentassist=true.
    • Add multiBot=true parameter to it to use multiple Agent AI bots with different queues.
    • Configure the SIP of any of the bots inserted in the Data Table.
    • Get the Voice Gateway host name from the corresponding environment you use at SaaS or on-prem.
  5. Follow these steps to get the Connection URL:
    1. Go to Agent AI > Flows & Channels > Voice Gateway > SIP Numbers > Configure SIP Trunk.
    2. Select Agent AI in the Product Selection section.
    3. Select Genesys Audiohook in the Select the SIP Trunk connection method dropdown list.
    4. Click Copy next to the Connection URL field. configure-sip-trunk
  6. Add the following details in the Advanced tab:
    {
      "environment": <genesys-environment(For example: mypurecloud.com)>,
      "oauthClientId": <genesys-oauth-id>,
      "koreDomainURL": <Agent AI URL>,
      "oauthClientSecret": <genesys-oauth-secret>,
      "sendEventsToVG": `true`,
      "botId": <Bot-ClientID>,
      "token": <JWT-token-created-in-previous-step-using-Bot-ClientID-and-ClientSecret>
    }
    
    Create an OAuth using the Client Credentials grant type, and use the resulting Client ID and Client Secret for configuration.
    advanced-configurations
  7. Add credentials in the Credentials tab.
  8. Use the ClientID and ClientSecret of the AI Agent you used while configuring the Audiohook. The system uses these credentials to validate the audio stream signature.
  9. Click Save.

Create/Update Architect Inbound Call Flow in Genesys for the Agent Queue

Calls coming to a Genesys number pass through an architect flow. If you don’t have an Automatic Call Distribution (ACD) architect flow for the queue, create one by following this section.

Steps to create a call architect flow

  1. In Genesys Cloud, go to Admin > Architect > Architect.
  2. Click +Add to create an Inbound Call Flow.
  3. Click Create Flow. The final architect flow looks like the following screenshot: final-architect-flow
  • Inside the Transfer to ACD node, select the queue name to transfer the call.
  • The Transcription node is optional, if you have turned on Voice Transcription and Audio Monitoring in the queue-level voice configuration.
  • Architect flow is a mandatory step, as it directs the incoming call to the Genesys agent desktop.

Access Custom Data and Secure Custom Data in AI Agent

You can access Custom Data and Secure Custom Data in:
  • Welcome Events in the Agent AI configuration page
  • Dialog Tasks in the Agent AI automation page
You can access Custom Data as {{context.session.UserContext.customData.internalMetaData.<key>}}. Follow this doc for the detailed steps on how to access Custom Data. You can access Secure Custom Data as {{context.session.UserContext.secureCustomData.<key>}}. Follow the same steps of this doc for detailed information on how to access Secure Custom Data,except for the path being {{context.session.UserContext.secureCustomData.<key>}}.
If a URL-encoded JSON is provided in the x_passthru_metadata, use the JavaScript option in the Message node. Then, parse the value of context.session.UserContext.customData.internalMetaData before accessing its content.
Example:

var cd = JSON.parse(context.sessiinternalMetaDataon.UserContext.customData.internalMetaData);

print(cd.\<key\>);

Post Installation Setup

Steps to start a Chat Request Simulation

  1. Sign in to Genesys Developer Applications.
    To start chat simulation, you must have access to the Genesys Developer portal (an account with Genesys).
    chat-simulation
  2. Click Web messenger, select the Deployments, and then click Start Chat to initiate the chat request. chat-simulation-web-messenger
  3. Enter a message on the Message Us window, and then click the Send icon. chat-simulation-message-use
  4. Turn on the On Queue toggle on the upper-right corner of the page. A new chat notification appears on the Genesys Agent Desktop.
  5. Accept the conversation by clicking Answer on the left panel.
  6. Select the Interaction Widget icon to view the Agent AI widget. interaction-widget-icon-chat

Steps to start a Voice Request Simulation

  1. In Call Routing, assign the Architect flow you created in Step-4 to a Genesys phone number.
  2. Initiate a call using this Genesys phone number. A new call notification appears on the Genesys Agent Desktop.
  3. Accept the conversation by clicking Answer on the left panel.
  4. Select the Interaction Widget icon to view the Agent AI widget. call-interaction-details

Set default contextual panel to Kore Agent AI Interaction Widget

To streamline call handling and improve efficiency, you can embed the Agent AI widget as the primary contextual panel interaction widget. To enable this:
  1. In Genesys Cloud, click Admin.
  2. Click Panel Manager under the Contact Center section. This opens the Default Contextual Panel.
  3. Select the interaction widget name in both Voice and Web Messaging field dropdown lists (refer to step-4 of Create an Interaction Widget in Genesys for Agent AI).
  4. Click Save. default-contextual-panel
    Reload the Genesys Agent Desktop before testing this latest change.

Support for Agent Transfer

The Agent AI widget supports both Cold and Warm Transfers:
  • Cold Transfer: A cold transfer occurs when one agent hands over a conversation to another, applicable across Voice, Chat, and Email channels. The system generates a new conversation summary for the receiving agent and adds it to Agent-1’s Assist tab, along with feedback options. Agent-2 can modify the summary feedback for Voice and Email channels.
  • Warm Transfer: A warm transfer is like a conference call between two agents, applicable to Voice and Chat channels. During the transfer, Agent-2 can modify the summary feedback. However, the Run, Override, Send, Copy, Terminate, Restart, and List View buttons remain unavailable until Agent-1 disconnects from the call.

Switch to Agent AI SDK (Optional)

You can embed the Agent AI widget into the Genesys desktop using the Web SDK. To do this, update the following configurations:

Kore Data Table Change

  1. Go to the Kore Data Table.
  2. Click on the name of the Data Table.
  3. Add a new column to the existing data table as isAgentAISDK and data type as string. new-column
  4. Click Create/Update (for existing table configuration).

Insert/update data into Data Table

For first time users, use the POST API and for existing users, use the PUT API to insert this new field into the Kore Data Table. API Body Payload Structure:
    {
        "data": {
            "QueueIdentifier": <Unique QueueIdentifier>,
            "BotId": <Kore BotId>,
            "ClientId": <Kore ClientId>,
            "ClientSecret": <Kore ClientSecret>,
            "AudiohookEnabled": "true" / "false",
            "AgentAssistWidgetURL": <Kore Agent AI Widget URL>,
            "KvpConfig": <KVPs of SecureCustomData>,
            "JWEPublicKey": <Public Key assigned to Client App>,
            "Algorithm": "HS256",
           "isAgentAISDK": "True"
        }
    }

XO 11 Configuration Notes

For the configured app, ensure configuration of at least one Dialog Task for Agent AI use. dialog-settings-page Where to find configuration settings You can find it in Flows & Channels > Digital > Web/Mobile Client. jwt-app-details