One of the clearest signals of where the contact centre market has gone is this: Zendesk Contact Center is powered by Amazon Connect. Rather than build telephony from scratch, Zendesk builds its voice contact centre on top of Connect — which is exactly the kind of "big platforms build on it rather than needing to" signal that marks Amazon Connect as becoming the infrastructure layer underneath enterprise CX.[1][5]
This guide explains how the two work together today, the setup model, how data flows between them, and who the combination is actually for.
The Integration Model: Who Does What
The cleanest way to understand the pairing is to see which system owns which job. Amazon Connect is the engine; Zendesk is the agent experience and ticketing layer.
| Amazon Connect provides | Zendesk provides |
|---|---|
| The telephony, call management, chats, queues, and contact flows[2] | The agent interface for managing calls and chats (the Contact Center app)[1] |
| Routing and IVR / self-service logic | Ticketing, workflows, and the omnichannel CX platform around the interaction |
| Runs in your own AWS account | The admin and agent experience, linked to one Connect instance[2] |
Crucially, Connect is the cloud service that powers Zendesk Contact Center — it manages calls, chats, queues, and contact flows — while installing the Contact Center app gives agents the interface to actually handle those calls and chats inside Zendesk.[1][2] Content was rephrased for compliance with licensing restrictions.
How It's Set Up
The setup reflects that split. You stand up Amazon Connect in your own AWS account, then link it to Zendesk:
- Create an Amazon Connect instance in the AWS Management Console — either via an automatic CloudFormation template or manual customisation, configuring SAML authentication, telephony options, and data streaming.[3]
- Link it to Zendesk Contact Center — a Contact Center account links to exactly one Connect instance.[2]
- Configure user access and allowed domains, and enable call recording writeback so recordings flow back appropriately.[1]
- Install the Contact Center app to give agents the call/chat management interface.[1]
Key architectural point: each Zendesk Contact Center customer runs their own Amazon Connect instance in their own AWS account.[2] This matters for cost (you pay AWS directly for Connect usage, on top of Zendesk), for data residency and control, and for how you'd run a Well-Architected review or apply your own IaC and runbooks to the underlying Connect instance.
How Data Flows Between Them
Beyond the live call interface, the two platforms share data in both directions:
Zendesk data into Amazon Connect (Customer Profiles)
Amazon Connect Customer Profiles can integrate external applications such as Zendesk and Salesforce, combining their data with Connect contact history to build a single unified customer profile — so agents see everything they need in one place during an interaction.[6] That means a caller's Zendesk ticket history can surface as part of their Connect customer profile.
Zendesk events out via EventBridge
Zendesk can stream event data to Amazon EventBridge, which can then route those events to AWS services like Lambda, SNS, SQS, and Kinesis — letting you build event-driven automation that reacts to Zendesk events within your AWS environment.[7]
AI & Knowledge Integration
The AI story has tightened recently too. Amazon Bedrock managed knowledge bases now support Zendesk as a native data source connector[8] — meaning your Zendesk help centre content can directly feed the knowledge base that powers AI answers in Amazon Connect self-service and agent assist. Instead of maintaining knowledge in two places, your existing Zendesk content can ground the AI.
Why this combination is getting stronger, not weaker: the fact that Zendesk builds its contact centre on Amazon Connect — and that Bedrock now natively connects to Zendesk content — means the integration points keep deepening rather than being a bolt-on. You get Zendesk's CX workflows and Connect's AWS-grade telephony and AI as an increasingly joined-up stack.[5]
Who the Pairing Is For
Amazon Connect + Zendesk makes most sense when:
- You're already standardised on Zendesk for ticketing and omnichannel CX and don't want to move agents to a different desktop
- You want AWS-grade cloud telephony, routing, and AI — pay-as-you-go, scalable, deeply integrated with the rest of AWS — as the engine under that experience
- You value keeping the contact centre engine in your own AWS account for control, data residency, and the ability to apply your own IaC, security, and operations to it
- You want your Zendesk knowledge content to power AI self-service and agent assist without duplicating it
It's less compelling if you're not on Zendesk, or if you'd rather use Amazon Connect's native agent workspace directly rather than through Zendesk's interface — in which case you're really just evaluating Connect on its own.
Frequently Asked Questions
How do Amazon Connect and Zendesk work together?
Zendesk offers Zendesk Contact Center, which is powered by Amazon Connect. Amazon Connect runs in your own AWS account and provides the telephony, routing, queues, and contact flows, while the Zendesk Contact Center app provides the agent interface for managing calls and chats inside Zendesk. A Zendesk Contact Center account links to one Amazon Connect instance.
Does Zendesk Contact Center require its own AWS account?
Yes. Each Zendesk Contact Center customer must run an Amazon Connect instance in their own AWS account, and a Contact Center account can link to only one Connect instance. You set up Connect in the AWS console (via a CloudFormation template or manually), then link it to Zendesk and configure user access, allowed domains, and call recording writeback.
Can Amazon Connect pull data from Zendesk?
Yes. Amazon Connect Customer Profiles can integrate external applications like Zendesk and Salesforce, combining their data with Connect contact history into a single unified customer profile for agents. Separately, Amazon Bedrock managed knowledge bases support Zendesk as a native data source connector, so Zendesk help content can power AI answers.
Who should use Amazon Connect with Zendesk?
The pairing suits organisations already standardised on Zendesk for ticketing and CX who want AWS-grade cloud telephony and AI without leaving the Zendesk agent experience. It gives you Zendesk's omnichannel ticketing and workflows as the front end, with Amazon Connect's pay-as-you-go voice, routing, and AI as the contact centre engine underneath.
Conclusion
Amazon Connect and Zendesk aren't an either/or — Zendesk Contact Center is built on Amazon Connect, with Connect running in your own AWS account as the telephony and AI engine and Zendesk providing the agent and ticketing experience on top. Add Customer Profiles pulling Zendesk data into unified profiles, EventBridge streaming events the other way, and Bedrock now connecting natively to Zendesk knowledge, and it's a genuinely joined-up stack for anyone already invested in Zendesk.
If you're weighing Connect against other platforms more broadly, see our Amazon Connect vs Genesys vs Twilio comparison and our independent Amazon Connect review.
Sources
- Zendesk, Implementing Zendesk Contact Center (app)
- Zendesk, Implementing Zendesk Contact Center (Connect powers it; one instance)
- Zendesk, Setting up Amazon Connect for Contact Center
- CX Today, The Amazon Connect ecosystem
- AWS, Integrate external applications with Customer Profiles
- Zendesk, Event connections to Amazon EventBridge
- AWS, Bedrock managed knowledge base — Zendesk native connector
Content was rephrased for compliance with licensing restrictions.