Genesys Cloud and Zendesk: integration options, requirements and costs

Zendesk and Genesys Cloud CX overlap less than their marketing suggests. Zendesk is a ticketing and customer service platform, with its own voice and AI products. Genesys Cloud CX is a contact centre platform: routing, telephony, digital channels, workforce engagement and analytics. Many organisations run both, keeping Zendesk as the system of record for tickets and customers, and using Genesys Cloud CX to route and handle the contact that creates and resolves those tickets.

Zendesk makes room for this through Voice Partner Edition, formerly Talk Partner Edition, which Zendesk describes as a toolbox that lets you integrate Zendesk Support with third-party telephony systems, and which lets you choose your own call centre software. Genesys builds on it with Genesys Cloud for Zendesk, and adds a separate data actions integration for flows and scripts. The two together cover most designs, and they are independent: you can use either without the other.

Genesys describes the client as a variant of its contact centre services inside Zendesk, with nothing to install on each user's computer. It supports call, callback, outbound dialling, email, message and ACD voicemail interactions, with click-to-dial, screen pop, scripts, search, call controls, transfers, wrap-up, status changes, call history, co-browse and Agent Copilot. Genesys advises running Genesys Cloud alongside the client for fuller functionality, and warns against running different variants of its embedded clients at the same time.

Screen pop searches all phone number fields in Zendesk for the caller's number. Architect flows can steer it with the ZD_SearchType and ZD_SearchValue attributes, for example to pop a ticket identified in the IVR; where several contacts match, the agent chooses. By default every interaction creates an interaction log saved to a Zendesk ticket, as a public or private comment or as a searchable ticket field, and advanced mappings write interaction attributes into ticket fields. New tickets can be created with mapped custom fields of every type except credit card.

The app is installed from the Zendesk Marketplace, pointed at the organisation's Genesys Cloud region, and optionally restricted by Zendesk role or group; updates arrive automatically. Single sign-on works if the identity provider allows its sign-in window to be embedded, and an Auto Redirect to SSO setting sends every agent to it.

On the Zendesk side, the key requirement is Voice Partner Edition. Zendesk's Marketplace listing for the Genesys Cloud app states that it is available only to agents with Partner Edition seats. Zendesk includes Partner Edition in its Customer Service Suite plans from Team upwards, and in Employee Service Suite plans from Growth upwards. Legacy plans need Partner licences for every agent using a third-party voice app, and Zendesk is explicit that Partner Edition seats are separate from seats for its own voice product.

On the Genesys side, each user needs a Genesys Cloud licence at Communicate level or higher, and the Genesys Cloud for Zendesk integration is licensed and billed in its own right. Permissions are optional and feature by feature, so roles can be shaped to what each team does. Browsers must be current versions of Chrome, Firefox or Microsoft Edge with third-party cookies and browser storage enabled.

The Zendesk data actions integration lets Genesys Cloud act on Zendesk data in Architect flows, to make routing decisions, and in scripts, to show agents what they need. Nine static actions cover the common lookups: the most recent ticket by email address or user ID, an organisation by ID or name, a ticket by ID, and a user by email address, phone number, user ID or name. Custom actions extend this to anything the Zendesk API exposes, and separate integrations can point at different Zendesk accounts. Timeouts are configurable from one to sixty seconds.

Every lookup consumes Zendesk API capacity, which Zendesk limits per minute by plan. Genesys does not quantify the integration's API usage, so high-volume designs should be sized against these limits: an IVR that looks up every caller, plus agents' clients and other integrations, can approach them at peak. Zendesk's High Volume API add-on raises the ceiling where needed.

Three licences are involved. Genesys Cloud CX licences cover the contact centre itself. Genesys lists CRM and case management integration, including Zendesk, as an add-on on every Genesys Cloud CX tier; it publishes no price for it, and bills it for each user who holds the integration licence and logs in at some point in the month. On the Zendesk side, Partner Edition is included in Suite plans from Team upwards, so most current Zendesk customers already have it, but organisations on Support-only or legacy plans may need a plan change or Partner licences first.

Two Zendesk points often surprise people. Partner Edition seats and Zendesk's own voice seats are separate, so running both for the same agents means paying for both. And some Zendesk features are tied to Zendesk's own voice: Zendesk lists its AI agents for voice as requiring Zendesk voice, and Zendesk Explore shows only data associated with tickets for Partner Edition calls, so voice analytics come from Genesys Cloud. The table shows the vendors' published list prices.

Published by each vendor and checked on 12 October 2026. These are list prices, before any discount, tax or contract terms, and they change; the sources at the end of this page are authoritative. QVCCS does not sell licences.

Zendesk offers its own options for telephony: Zendesk Voice, formerly Talk, and Zendesk Contact Center, built on Amazon Connect. For a small team taking simple calls into tickets, those may be enough, and they keep everything in one vendor. Genesys Cloud CX comes into its own when the contact centre needs more than ticket-centred calling: skills-based and predictive routing across voice and digital channels, outbound campaigns, workforce management, quality management, speech and text analytics, and the ability to grow to thousands of agents and several regions.

The decision is rarely about Zendesk versus Genesys, because the two do different jobs. It is about where routing, workforce engagement and analytics should live, and whether agents work mainly in tickets or mainly in conversations. Organisations already running Genesys for voice and digital usually keep Zendesk for tickets and connect the two; organisations whose contact is light and ticket-led often start with Zendesk's own products.

PureConnect organisations last had a Zendesk integration in the Zendesk Screen Pop Connector for CIC, which reached end of support on 25 August 2020, with Genesys naming what is now Genesys Cloud for Zendesk as its replacement. PureConnect itself reached end of support on 31 July 2025. Any PureConnect site still integrated with Zendesk is therefore running unsupported software on both sides of the integration, and its move should go straight to Genesys Cloud CX with Genesys Cloud for Zendesk.

Genesys Engage organisations have used the Gplus Adapter for Zendesk, an option of Workspace Web Edition. Genesys has announced 31 December 2028 as the end of maintenance and support for all Engage on-premises products, after which subscription licences stop working. Unlike Salesforce, Zendesk is not retiring the integration framework the Genesys client uses, so the Zendesk side of the move can follow the platform plan; the work is in mapping today's screen pops, logging and ticket creation rules to their Genesys Cloud for Zendesk equivalents.

1. Inventory current behaviour: screen pop rules, ticket creation, logging, click-to-dial and wrap-up
2. Confirm Zendesk plans and Partner Edition seats for every agent group
3. Design data actions and Architect logic for caller lookup and routing decisions
4. Map interaction logging to ticket comments or fields, and check reports and triggers that rely on them
5. Size API usage at peak against the Zendesk plan's rate limit
6. Pilot with one team, then move teams in phases with hypercare

QVCCS starts by establishing how each team actually works: in tickets or in conversations, which Zendesk fields and triggers matter, and which Zendesk features depend on Zendesk's own voice. The design records the choice between the embedded client and the Genesys Cloud workspace, the screen pop and ticket creation rules, the logging design and the data action catalogue, together with the licence position on both sides.

Build and test follow our engineering standards: data actions, Architect flows, scripts and app configuration are built to a build book, peer reviewed and proven with real agents before phased go-live. For PureConnect and Engage organisations we plan the Zendesk integration inside the platform migration, so agents arrive on Genesys Cloud CX with Zendesk working as they expect from the first day.