Integrating Zendesk with Genesys Cloud CX: A Step-by-Step Configuration Guide

How-To-Articles
1

Integrating Zendesk with Genesys Cloud CX: A Step-by-Step Configuration Guide

What This Guide Covers

This guide details the configuration necessary to integrate Zendesk Support with Genesys Cloud CX, enabling features like screen pops, call logging, and CTI functionality directly within the Zendesk agent interface. The end result is a seamless agent experience where incoming and outbound calls are synchronized with Zendesk tickets, providing a unified view of customer interactions.

Prerequisites, Roles & Licensing

  • Genesys Cloud CX Licensing: Genesys Cloud CX requires at least the CX 2.0 edition for full CTI integration capabilities. The Digital Channels subscription is also necessary for leveraging the APIs used in this integration.
  • Zendesk Support Plan: Zendesk Support Professional or Enterprise is required to utilize the necessary API access and webhooks.
  • Genesys Cloud CX Permissions: The user configuring the integration requires the following permissions:
    • Admin > Integrations > Third-Party > Edit
    • Admin > Users > View (to create/modify a dedicated integration user)
    • Telephony > Call Flows > View/Edit (to modify call flows)
  • Zendesk Permissions: The Zendesk administrator requires permissions to install and configure Zendesk apps and manage API tokens.
  • OAuth Scopes (Genesys Cloud): The integration requires the callcenter OAuth scope.
  • External Dependencies: A stable internet connection for both platforms is essential. A dedicated Genesys Cloud user specifically for the integration is highly recommended.

The Implementation Deep-Dive

1. Creating the Genesys Cloud Integration User

First, we create a dedicated user in Genesys Cloud CX solely for the Zendesk integration. This is critical for security and auditing.

  • Navigate to Admin > Users > Users.
  • Click + Add User.
  • Provide a descriptive name (e.g., “Zendesk Integration”).
  • Assign the role of “Agent” only. Do not grant any supervisor or administrative privileges.
  • Ensure the user is assigned a valid extension number. This number will be used within Zendesk for CTI functionality.
  • The Trap: Assigning excessive permissions to this integration user is a common mistake. If compromised, the impact is limited to the Zendesk integration, rather than granting broader access to your Genesys Cloud environment.

The architectural reasoning is simple: Least Privilege. Restricting the user’s access limits the blast radius of potential security breaches.

2. Configuring the Genesys Cloud CX CTI Adapter

Next, we configure the CTI adapter in Genesys Cloud CX. This adapter acts as the bridge between Genesys Cloud and Zendesk.

  • Navigate to Admin > Integrations > Third-Party > Zendesk.
  • Click Configure.
  • Enter the Zendesk Subdomain. (e.g., yourcompany.zendesk.com).
  • Enter the Zendesk Email Address associated with the Zendesk account.
  • Enter the Zendesk API Token. To generate this token in Zendesk:
    • In Zendesk, navigate to Admin Center > Account > API.
    • Click Add API Token.
    • Provide a descriptive name.
    • The token will be displayed immediately – copy and paste it into the Genesys Cloud configuration.
  • Select the Genesys Cloud user created in step 1.
  • The Trap: Using a personal agent’s account for the integration is a dangerous practice. If that agent leaves the company or their account is compromised, the integration breaks.
  • Enable Enable Call Logging to automatically create call records within Zendesk.
  • Save the configuration.

Architecturally, we are leveraging Zendesk’s API to authenticate and authorize Genesys Cloud CX to perform CTI actions on its behalf. The API token acts as a password, so treat it with extreme care.

3. Installing the Genesys Cloud Integration within Zendesk

Now, we install the Genesys Cloud integration application within Zendesk.

  • In Zendesk, navigate to Admin Center > Apps > Marketplace.
  • Search for “Genesys Cloud”.
  • Click Install.
  • Follow the installation prompts.
  • During installation, you will be prompted to authorize the app. Click Install.
  • After installation, navigate to the Genesys Cloud integration within Zendesk ( Admin Center > Apps > Manage > Genesys Cloud).
  • Enter the Genesys Cloud OAuth Client ID and Client Secret. These can be obtained from Genesys Cloud by navigating to Admin > Integrations > Third-Party > Zendesk > OAuth Credentials.
  • Configure the Agent Mapping. This determines how Zendesk agents are linked to Genesys Cloud CX users. You can map based on email address or Genesys Cloud extension number. Email mapping is generally more reliable.
  • Configure Call Flow Association. This determines which Genesys Cloud call flows will be triggered when a call is initiated from Zendesk.
  • The Trap: Incorrectly mapping agents can result in calls being routed to the wrong person or failing to connect. Carefully review the mapping configuration and test thoroughly.

The rationale behind using OAuth is to avoid storing long-lived credentials within Zendesk. OAuth allows for secure, delegated access.

4. Configuring Call Flows in Genesys Cloud CX

Finally, adjust Genesys Cloud CX call flows to handle calls initiated from Zendesk appropriately.

  • Open the relevant call flow(s) in Genesys Cloud CX (Admin > Call Flows > Call Flows).
  • Ensure the call flow is configured to accept calls from the Zendesk integration.
  • Consider adding a “Transfer to Agent” step, using the mapped Zendesk agent as the destination.
  • The Trap: Failing to account for calls originating from Zendesk within your call flow can cause routing issues, resulting in dropped calls or unexpected behavior.

The purpose of call flow adjustments is to ensure a smooth and predictable call handling experience for both agents and customers.

Validation, Edge Cases & Troubleshooting

Edge Case 1: Agent Mapping Fails

  • Failure Condition: Calls initiated from Zendesk do not connect, or are routed to the wrong agent.
  • Root Cause: Incorrect agent mapping configuration in Zendesk.
  • Solution: Verify the agent mapping settings in Zendesk. Ensure email addresses or extension numbers are accurately matched. Review the Genesys Cloud user configuration for inconsistencies.

Edge Case 2: Screen Pop Not Working

  • Failure Condition: Customer details do not appear in the Zendesk agent interface when a call is received.
  • Root Cause: Incorrect Zendesk API Token or missing configuration in Genesys Cloud CX.
  • Solution: Double-check the Zendesk API token configured in Genesys Cloud. Ensure that the “Enable Call Logging” option is selected. Verify that the customer data within Genesys Cloud is accurately associated with the calling number.

Edge Case 3: Call Logging Fails

  • Failure Condition: Call records are not being created in Zendesk.
  • Root Cause: Permissions issues within Genesys Cloud or Zendesk, or a misconfiguration in the CTI adapter.
  • Solution: Verify that the Genesys Cloud integration user has the necessary permissions to create call records. Check the Zendesk integration logs for errors. Ensure that the “Enable Call Logging” option is enabled.

Official References