CXone supports integrations with third-party virtual agent
A software application that handles customer interactions in place of a live human agent. providers on Any channel, contact, or skill associated with Digital Experience. channels
- Amazon Lex V1
- Amazon Lex V2
- Cognigy
- Enlighten Autopilot
- Google Dialogflow CX
- Google Dialogflow ES
- IBM Watson Assistant
- Omilia
- Salesforce Einstein
If you want to use a virtual agent provider that's not natively supported, you can do a custom virtual agent integration. Custom integrations require additional development work to set up a secure communication route between the virtual agent provider and CXone.
Integration Process
Integrating a virtual agent A software application that handles customer interactions in place of a live human agent. with CXone involves the following tasks:
- Set up, configure, and test your virtual agent with the provider. Refer to your provider's documentation for help with this step.
- Create at least one Studio script with a virtual agent action.
- Add a configuration app in Virtual Agent Hub to connect your virtual agent to CXone. Link the app to the Studio action used in your script.
- Test the connection and communication between CXone and the virtual agent. You can do this from the virtual agent configuration app in Virtual Agent Hub.
- Create a CXone voice The entry point that an inbound contact uses to initiate an interaction, such as a phone number or email address.) and assign the Studio script to it.
- Test the virtual agent end-to-end using the voice
Every virtual agent provider has unique requirements and configuration needs. The online help for the integration of each supported virtual agent provider contains information about the process specific to that provider.
Voice Connection Options
There are two ways to set up a connection between CXone and the voice virtual agent provider. In most cases, CXone supports only one of the options for each provider. The options are:
- Utterance-based communication: Routing and utterance What a contact says or types. processing happens in CXoneVirtual Agent Hub. You're able to control and customize each turn in the conversation. This is the option supported for most virtual agent providers.
- SIP backchannel connection: This option uses backchannel audio connections and a signaling connection. The connections are configured in Virtual Agent Hub, but no other Virtual Agent Hub processing or routing is used. The signaling connection allows the virtual agent to communicate with CXone when the conversation is complete or needs to be escalated to a live agent. Contact your CXone Account Representative for more information about this option.
The voice connection option supported for each virtual agent provider is described in the table on the Virtual Agent Hub overview page.
Rich Text Support for Text Virtual Agents
If your channel supports it, you can include rich media Elements in digital messaging such as buttons, images, menus, and option pickers. content in the messages. The type of rich media that can be sent differs from channel to channel, as shown in the following table.
| Adaptive Cards | HTML & Markdown Text | Rich Link | Quick Replies | List Picker | Time Picker | Form message | |
|---|---|---|---|---|---|---|---|
| Apple Messages for Business |
|
|
|
|
|
|
|
|
Digital Chat |
|
|
|
|
|
|
|
|
|
|
|
Uses fallback text |
|
|
|
|
| Facebook Messenger |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Google Business Messages |
|
|
|
|
|
|
|
Supported:
Not Supported:
Learn more about digital channel support for rich media.
When you want to include rich media content in text virtual agent responses, configure it in your virtual agent's management console. It should go in the configuration for each response that will send the rich media.
Rich media content is sent as JSON. When building your rich media JSON, follow the schema for the digital channel you're using. The schemas are different for each channel. Find the JSON for the media content you want to use, then add it to the response message configurations that you create in Cognigy
Conversation Transcripts
CXone can collect the transcripts and intent The meaning or purpose behind what a contact says/types; what the contact wants to communicate or accomplish data from voice and chat virtual agent conversations. You can use the information in whatever way meets the needs of your organization. For example, you could have them saved to an external database. You could also have them sent to the agent application for interactions that are escalated to live human agents. This feature must be enabled in the configuration app for your virtual agent in Virtual Agent Hub. By default, transcripts and intents are not collected.
The exact data that's collected depends on how the feature is configured. You can have only transcripts collected, only intents, or both transcripts and intents. If you have more than one virtual agent, you can configure each one separately.
What you do with the collected data is up to you. If you want to save it for record-keeping, the virtual agent's Studio script must be configured to do so. By default, when conversation transcript collection is enabled, the collected data is stored until the interaction is complete.
Using this feature requires custom scripting in the virtual agent Studio script. It must also be enabled on the Transcript page in the virtual agent's configuration app in Virtual Agent Hub.
Integration Versions
Periodically, Virtual Agent Hub receives updates that are controlled through numbered versions. Updates of this kind are not applied automatically. You must manually select the new version for each of your virtual agent apps in Virtual Agent Hub. This gives you control over what version you're using and when you upgrade. This is important because some versions require you to update and test your scripts before moving to a new version.
If you have more than one virtual agent, you can choose the version for each one. Additionally, if you ever need to, you can revert one of your virtual agents to a prior version.
Some numbered versions are limited to certain virtual agent providers. Not all virtual agents have the option for every integration version. The following integration versions are available:
- Version 1.0.0:
- Version 2.0.0:
- Version 3.0.0: This version introduced StandardBot, which standardizes how CXone communicates with virtual agent providers. The customPayload object returns as an array, as customPayloadscriptPayloads[n].xxxx. This version is available for all providers.
You can check the integration version you're currently using on the Properties page of the app for your virtual agent in Virtual Agent Hub. The Integration Version field shows the version the app is currently using.
Use care when changing versions. The changes made from version to version can affect many aspects of your integration, including scripts, settings, schemas, and more. Changing to the wrong version without testing the upgrade first can result in your virtual agent not working as expected. This could result in your contact center's ability to handle contacts through that channel being disrupted.
Custom Studio Scripting
Custom scripting is required for all virtual agent integrations. The scripts define the routing of contacts through an interaction with the virtual agent. They also configure the connection between the virtual agent provider service and CXone.
The online help provides guidelines and requirements for the scripts you need for integrating virtual agents. See the CXone online help page for your virtual agent provider for details.
There are three virtual agent Studio actions. They connect CXone and your virtual agent. The virtual agent you use might work best with a specific action. The virtual agent