Find the answer you are looking for

Genesys Pure Cloud integration requirements

To perform the integration, you must have an account in Genesys Cloud and inform us through a Service Request of data listed below according to the version.

Genesys Cloud:
a. regionDomain: This parameter will be the URL base for the requests in the transfer. It has the following format: api.mypurecloud.XX ➡Where "XX" is the region of the Purecloud instance.
b. queueName: This will be taken from the "queueName" parameter, which can be set in a pre-form or via the Aivo SDK. If the parameter "queueName" is not found in the Queue Chat Request, then the "queueName" of the credentials will be taken by default.
c. organizationId
d. deploymentId


📢Note that organizationId and deploymentId must match a valid web chat or Widget deployment.

Genesys Cloud Open Messaging:
a. regionDomain
b. init_message (when there is no previous history with the bot)
c. Client ID
d. Secret ID
e. Integration ID

f. Conversation start message
g. attended_timeout: Timeout time for lack of attention. If the agents can not attend to the user, they can continue talking to the bot instead of being on hold indefinitely.

➡In this link, you can search the regionDomain of your Pure Cloud for any of the versions.

⚠ Important: Since we are not part of the Genesys technical support team, our assistance is limited to aspects that directly involve our platform:
           ✓ Creating the integration at the points relevant to our platform.
           ✓ Configuring conversation routing from the Virtual Assistant.
           ✓ Implementing pre-forms in the Virtual Assistant, if applicable, before the routing.
➡ You should contact the official Genesys support team for any other technical questions or internal information related to Genesys.
This website stores cookies on your computer. These cookies are used to collect information about how you interact with our website and allow us to remember you. We use this information in order to improve and customize your browsing experience and for analytics and metrics about our visitors both on this website and other media. To find out more about the cookies we use, see our Privacy Policy.

If you decline, your information won’t be tracked when you visit this website. A single cookie will be used in your browser to remember your preference not to be tracked.