Genesys and Zendesk

Two platforms that both want to be the place agents work. Making them cooperate is mostly a governance decision, not a technical one.

Start free trial All guides

What the integration gives you

Strip away the marketing and a contact centre to helpdesk integration does four things.

Screen pop. A call arrives, Genesys identifies the caller, Zendesk opens the matching user and their recent tickets. This is the feature people actually buy it for.

Click to call. An agent clicks a number in a ticket and Genesys dials it. Small, and agents notice its absence every single day.

Call logging. The call ends and a ticket is created or updated with duration, direction, disposition and a link to the recording.

Presence and controls. Answer, hold, transfer and wrap up from inside the Zendesk window, so agents aren't alt tabbing between two apps mid sentence.

Anything beyond that list is usually reporting, and reporting is where the two systems fight.

Genesys or Zendesk: who owns routing

This is the whole decision, and teams postpone it until something breaks.

Genesys has a serious routing engine. Skills, queues, priority, estimated wait, callbacks, the lot. Zendesk has omnichannel routing that assigns tickets, chats and calls to agents based on capacity and skills. Both are good. Neither knows what the other is doing.

Run both and you get double assignment: Genesys sends a call to an agent who Zendesk has just handed three chats, or Zendesk holds capacity for an agent Genesys has parked in after call work. The queue looks fine on both dashboards and agents are quietly overloaded.

Pick one. In practice, if you have Genesys, Genesys routes voice, and Zendesk routing handles the digital channels it owns. Set agent capacity in Zendesk so voice work is accounted for, or accept that your capacity numbers describe half the job. See Zendesk omnichannel routing for what that side can and can't do.

How the connection is built

Genesys publishes integrations through its own AppFoundry marketplace, and Zendesk exposes a framework for embedding a phone client in the agent workspace with a channel for creating tickets from calls. The usual shape is a Genesys built app that embeds the interaction client in a Zendesk sidebar and writes call records back.

App names, supported Genesys editions and which pieces need a specific Zendesk plan all move around. Check the current AppFoundry and Zendesk Marketplace listings for what's supported today rather than taking a number from an article.

If your Genesys deployment is an older on premises estate rather than Genesys Cloud, expect a different and usually heavier integration story, often through a CTI adapter or a partner build.

What breaks in practice

Caller matching

Screen pop only works when the calling number matches a Zendesk user. Withheld numbers, switchboards, mobiles that aren't on the record, and shared office lines all fail. Decide what agents see on a miss: a blank creation form is honest, a wrong customer is dangerous.

Two records for one conversation

A customer emails, then calls about the same thing. You now have a ticket from email and a ticket from the call log. Nothing links them automatically, and both count in your volume.

Reporting that disagrees

Genesys counts interactions. Zendesk counts tickets. They will never match, and somebody in a QBR will ask why. Agree in advance which system is the source of truth for volume, handle time and abandonment, then stop reconciling the other one.

A sane rollout order

Teams try to launch every feature at once and then can't tell which piece is broken. Stage it.

Week one, screen pop only. Read only, low risk, and it delivers most of the perceived value. Watch your match rate before you build anything else on top of it.

Week two, click to call. Trivial to add, immediately loved, and it surfaces any number formatting problems you still have.

Week three, call logging. By now you know how many calls match a known customer, which is exactly the number you need to decide whether every call should create a ticket.

Later, the embedded controls. Answer, transfer and wrap up in the Zendesk window. Nice, and the piece most likely to break on either vendor's next release.

Pilot with a handful of agents who will tell you the truth. Voice integrations fail in ways that are obvious in the first hour of real use and invisible in a demo.

Is it worth it

If you already run Genesys for voice and Zendesk for everything else, yes, the integration is worth building. The alternative is agents with two apps open and a copy paste habit.

If you are choosing from scratch and your voice volume is modest, look hard at Zendesk Talk first. Fewer moving parts, one routing engine, one set of reports. Genesys earns its complexity at scale, with real workforce management and real IVR needs, and not much below that.

FAQ

Frequently asked questions

Which Genesys product does this connect?

Zendesk Genesys Cloud is the usual pairing, through a Genesys Cloud Zendesk connector that handles screen pop and call logging. Like any Zendesk CTI integration, the hard question is which system owns routing.

Does Genesys have a Zendesk integration?

Yes, published through the Genesys AppFoundry, with the phone client embedded in the Zendesk agent workspace. Check the current listing for supported editions and features.

Should Genesys or Zendesk route calls?

Genesys, if you have it. Running both routing engines against the same agents causes double assignment that neither dashboard shows.

Does the integration create a ticket for every call?

Typically yes, or it updates an existing one. Decide whether abandoned and very short calls should create tickets, or your volume metrics will be noise.

Why do Genesys and Zendesk numbers never match?

They count different objects. Genesys counts interactions, Zendesk counts tickets, and one conversation can be several of either. Pick one as authoritative.

Can we use Zendesk Talk alongside Genesys?

Technically yes, and it's usually a bad idea. Two voice platforms means two numbers, two sets of recordings and two reporting stories.