To Setup a Connector to a Genesys Environment, follow the steps here.
Refer to the full list of Botium Connectorsfor more information on supported Connectors and their capabilities.
There are two possible configurations for a Genesys connector. Follow the instructions for the appropriate configuration:
-
Web messaging:
- Websocket based communication
- Pure text and Rich content
- NLP analytics
-
Open messaging:
- Webhook based communicationNote: Only pure text is supported
- NLP analytics
- Webhook based communication
Web Messaging
-
First, you need to deploy your chatbot by following the available Genesys documentation at the following URL
- Then copy your Deployment Key from your Messenger Deployment:
-
In Botium, create a new chatbot, and select Genesys from the Connector/Chatbot Technology dropdown menu. In the Genesys Settings that appear, enter the following information:
- Genesys messaging channel: Web messaging (websocket)
- AWS Region: Your AWS region in Genesys cloud (If you are unsure, contact your Genesys Administrator)
- Deployment ID: Deployment Key from Genesys (see above)
- Check your connectivity to the Genesys Environment with a "SAY HELLO" and if you receive a response, click Save to save your configuration.
Open Messaging
Before starting to configure a Genesys connector that uses Open Messaging, you must first configure an Open messaging integration in Genesys cloud, and create client credentials.
- Copy the Genesys Outgoing Webhook URI from Botium and paste it into the
Outbound Notification Webhook URL in your Open Messaging
integration within the Genesys cloud.Note: Genesys Outgoing Webhook URI in Botium will be formatted as follows
https://***client***.botiumbox.com/api/inbound?APIKEY=***APIKEY***
- Enter the Outbound Notification Webhook URL in Open Messaging integration
in Genesys cloud as shown in the following screenshot.
- Then, from the Open Messaging url, the ID of your open messaging
integration must be copied into Botium.Note: Example:
https://apps.mypurecloud.com/directory/#/admin/messaging/platforms/open-messaging/details/1234d005-b06a-7890-bf12-34c567cdc890
- Next, the Client ID and Client Secret info must be copied into Botium.
-
In Botium, create a new chatbot, and select Genesys from the Connector/Chatbot Technology dropdown menu. In the Genesys Settings that appear, enter the following information:
- Genesys messaging channel: Open messaging (webhook)
- AWS Region: Your AWS region in Genesys cloud (If you are unsure, contact your Genesys Administrator)
- Outgoing Webhook URI: You have to configure your Genesys Open Messaging channel to use this URL as Outbound Webhook URL
- API Key: Choose an API Key to generate the Outgoing Webhook URI
- Open Messaging Integration ID: This is the ID of the open messaging integration.
- Client ID: Enter the client ID from the Genesys OAuth integration
- Client Secret: Enter the client secret from the Genesys OAuth integration
-
Optional:
- Add Inbound Message-flow Name
- Add Bot-flow Attribute Name
- Click the SAVE button to save your configuration in Botium.
- Next, in Genesys Cloud you have to bind your inbound message flow and the Open
messaging integration that you have created (as Inbound Address) together. You
can do it in the Message Routing page as shown here:
- Your task is now complete. If you wish to test the connection you can use the SAY HELLO (CHECK CONNECTIVITY) option seen is the last step of the Botium Chatbot Configuration above (step 5i)
Enable NLP Analytics
-
Client ID - same as in open messaging channel
-
Client Secret - same as in open messaging channel
-
Inbound Message Flow Name - you can find it among the inbound message flows on Architect page in Genesys cloud
-
Intent Resolution
-
Intent Confidence Score
-
Alternate Intents
-
Entity Resolution
-
Entity Confidence Score
Conversation Model Downloader
Once you have successfully created your Genesys chatbot configuration, you can then use the Conversation Model Downloader feature in the Botium Test Data Wizard.
-
Client ID - same as in open messaging channel
-
Client Secret - same as in open messaging channel
-
Inbound Message Flow Name - same as in enable NLP analytics
Permissions for OAuth client credentials
-
architect:flow:view
-
languageUnderstanding:nluDomainVersion:view
-
dialog:botVersion:view
-
conversation:message:receive
-
messaging:integration:allPermissions