Bringing Zendesk to the AI interfaces where work happens
How Zendesk Bridge brings service context and capabilities to the AI interfaces people now use.
Thomas Verschoren
Director, AI Product Evangelism
Laatst gewijzigd 19 november 2026
With Zendesk Bridge, our headless offering, the user is no longer someone with a license or a log-in. It's anyone who needs insights into the rich intelligence we've built over 20 years.” - Tom Eggemeier, Zendesk CEO
When doing complex work, the context and actions needed to get that job done rarely live in one place. A support agent handling a question needs access to a customer’s orders or account details alongside the conversation. They can switch between tabs, or they can bring that context right within Agent Workspace. Similarly, a developer in an issue tracker or someone in finance investigating a transaction has the same need for similar customer context within their own environment.
Today, more of that work starts in an AI assistant. People describe what they want to achieve rather than navigate each application themselves. In order to do that, the assistant needs access to the information and capabilities behind those applications to help them get it done.
That shift is happening, and more and more, instead of going to an app or platform, people interact with their data via AI Assistants. And that's where Zendesk Bridge comes in. With Bridge, Zendesk is making its service context and platform capabilities available to those external AI Assistants via a supported, governed connection. Rather than requiring people to go to Zendesk for every task, we can bring Zendesk to the AI interfaces they now use, where an assistant can help them understand an issue and, where the available tools and permissions allow it, take the next step in Zendesk.
That shift enables new possibilities for service teams and for everyone else whose work depends on understanding customers. It changes what they can combine, how the business governs that access and how much they need to know about Zendesk itself before they can leverage the data and capabilities within the platform.
Rather than requiring people to go to Zendesk for every task, we can bring Zendesk to the AI interfaces they now use.
Bringing service context into broader work
When an AI assistant can work with Zendesk alongside the other systems a business uses, people can investigate an issue with more of its context available and act on what they find, within the tools and permissions they have been given. That can help someone doing service work as much as a colleague whose work only occasionally touches Zendesk.
Consider three examples:
Who
What they need to do
How Bridge can help
Support agents
A travel agency needs to rebook multiple customers after a flight cancellation, combining requests in Zendesk with booking details held in a backend system.
With authorised access to both systems, an AI assistant could match requests to bookings, help prepare rebooking options in bulk and update tickets as decisions are made. Agents can coordinate work across affected customers rather than check each request separately.
Service team leads
A growing backlog requires a team lead to understand which queues are affected and whether an external incident explains the increase.
An AI assistant could combine waiting requests with incident reports to identify affected customers and issues, helping the team lead prioritise work with a clearer view of its impact.
Other business teams
A developer investigating a product update or someone in finance reviewing payment failures needs to understand what customers experienced alongside records in their own systems.
With appropriate access, an AI assistant could bring together relevant Zendesk conversations and external records, helping teams investigate without requesting exports or asking service agents to look up individual cases.
As Bridge unlocks this capability, it’ll not only make this easier for teams that already access and use Zendesk data today, but it will also unlock these capabilities for any other team in the business that might not be able to use those data or actions today.
How does Zendesk Bridge manage security and permissions?
Making information and actions available beyond the Zendesk interface also means being specific about who can use them and what they are allowed to do. Someone investigating a payment issue may need to read a conversation without changing the ticket, while a support agent working on that request may need to update it. Moving the interaction to an AI assistant needs to preserve those differences, allowing the business to expose the tools needed for a task without treating access to information as permission to change it.
Zendesk Bridge maintains Zendesk's existing permissions and access controls when people use its capabilities through external AI assistants. Admins control what tools an external AI can access, and which Zendesk users can use them. Requests are evaluated against the connected user’s existing permissions, and actions taken through the connection are recorded, so using an AI Assistant can not bypass the controls already applied in Zendesk. The capabilities available through the connection and the permissions of the person using it determine what the AI Assistant can help them do.
For a finance team investigating a failed payment, the customer’s conversation with support may explain what happened in a way the transaction record alone cannot. By enabling the appropriate tools, the Zendesk admins can make that context available to finance through its AI assistant, while the service team continues to own the records and govern access within Zendesk. Finance can carry out its own investigation without taking over control of the platform or its security, and the service team does not need to help with every individual lookup. The same principle applies when work involves several systems, each with its own owners and access rules.
Bridge is making Zendesk easier to work with
For someone who only occasionally needs service information, finding the right view, understanding a filter or knowing where to look can be a significant part of the task. An AI assistant offers a more accessible starting point because they can describe the question in the language of their own work. A developer can ask what customers have reported since a release without first learning how the service team has organised its workspace, and then narrow the question or ask to see the conversations behind an emerging pattern.
The AI Assistant uses the tools available to it to retrieve relevant information and carry out authorised actions, while the person can stay focused on the task rather than navigating the application. A support agent could work through an investigation and ask the assistant to add the findings to the ticket, without translating each step into a separate search, filter or form. For people who already know Zendesk, this provides another way to work with familiar capabilities; for colleagues who use it less often, it lowers the effort needed to put those capabilities to use.
People still need to understand their business, interpret the evidence and decide what should happen, but reaching the information and acting on it becomes less dependent on their familiarity with Zendesk’s interface. Someone who knows the customer, the product or the payment process can use that expertise to guide the work through their AI Assistant, with the available tools and permissions defining what it can carry out on their behalf.
Bringing Zendesk to where the work happens
The Zendesk platform brings together the context, knowledge and capabilities that teams use to run their service operations and deliver outcomes for customers and employees. Bridge extends that platform into the AI assistants people are choosing for their work, so they can both understand what is happening and use authorised capabilities to drive towards the outcomes they want. The platform continues to support the teams working directly in Zendesk while contributing to tasks that begin elsewhere.
And this is part of a broader shift in how software is designed and delivered. My colleagues Ben Mitchell and Jackson Wolfe explore what it means to build software for a world where the interface and the underlying capabilities no longer need to live together.
Instead of making Zendesk another destination everyone needs to visit, Bridge brings its context and capabilities to the AI interfaces where people are already asking questions and getting work done.
Thomas Verschoren
Director, AI Product Evangelism
Thomas Verschoren is Director of AI Product Evangelism at Zendesk, where he translates the platform’s rapid AI evolution into clear narratives for customers, go-to-market teams, and product leaders. He writes Internal Note, a strategic blog that connects individual Zendesk releases into the bigger story of modern AI-powered resolution platform
Before joining Zendesk, Thomas spent years as an implementation partner, designing and deploying the platform for organizations across industries. That hands-on experience grounds his work today: showing what is possible now, where the practical limits are, and where the platform is heading next.
Bring Zendesk into your AI workflows
Learn how Zendesk Bridge connects your service data and capabilities to external AI assistants, helping teams work with customer context wherever they need it.
Learn how Zendesk Bridge connects your service data and capabilities to external AI assistants, helping teams work with customer context wherever they need it.