Zendesk Ticket Sharing
Zendesk ticket sharing hands a ticket to another Zendesk account and keeps both sides in step. Useful in a narrow set of situations, awkward outside them.
What Zendesk ticket sharing actually does
Ticket sharing sends a ticket from your Zendesk account to another one. The receiving account gets its own ticket, linked back to yours, and comments flow between the two so both sides can follow the conversation.
The important detail: the customer stays yours. The requester relationship, the SLA and the responsibility for replying sit with the originating account. The partner is doing work on a copy, not taking over your customer.
This is genuinely different from an integration. There's no middleware, no API build, no third-party app. Two Zendesk accounts agree to talk to each other, and after that it's a menu item on the ticket.
Setting up an agreement
Sharing runs on an agreement, which both accounts have to consent to. One side sends an invitation, the other accepts, and until that happens nothing can be shared.
The agreement carries the permissions, and this is the part to read slowly. You choose what the receiving account may do with the shared ticket: whether their comments come back as public or private, whether they can change status, whether tags travel. Options and labels vary by account age and plan, so open your own agreement settings and read the current wording rather than trusting a summary.
Agreements can be one-way or reciprocal. A one-way agreement, where you send and they cannot send to you, is the right default with an outsourcer. Reciprocal makes sense between two internal teams that genuinely trade work.
Either side can end an agreement. Do check what happens to tickets already shared under it before you pull the plug, because that behaviour isn't always what people expect.
What syncs and what does not
Assume less syncs than you hope, test with a real ticket, and write down what you observed. That test takes twenty minutes and saves an argument later.
When to use it, and when not to
Sharing earns its place in a few clear cases. An outsourced partner running their own Zendesk, where you want their work visible without giving them seats in your account. A sister company or an acquisition that has not been consolidated. A supplier who owns one part of your product and needs the customer's actual words rather than your summary.
It's the wrong tool more often than it's the right one. If the other party is inside your own company, groups and views in one account are simpler and far easier to report on. If you just need an answer from a colleague, side conversations keep everything on one ticket. If the other team needs read access and occasional comments, light agents are cheaper than a second instance. And if the reason you have two accounts is branding, multibrand inside one account solves it without any sharing at all.
The honest test: sharing is for crossing an organisational boundary you cannot remove. Everything inside your own boundary should be solved inside one account.
Reporting on shared work
This is the weak spot. Each account reports on its own tickets, so end-to-end resolution time across a shared ticket isn't something Explore hands you.
The practical workaround is a tag applied on share, so you can at least isolate the population and measure your own side of the clock cleanly. It isn't a full picture. Nobody has one.
Agree the numbers with the partner up front, in writing, before a single ticket moves. Who owns first response, who owns resolution, and what happens when a customer chases you about work sitting in somebody else's queue. That conversation doesn't get easier three months in.
Frequently asked questions
How do you share tickets between two accounts?
With a sharing agreement. To share Zendesk tickets between accounts, both sides accept a Zendesk sharing agreement, and each Zendesk ticket sharing partner controls what syncs back.
Can I share a Zendesk ticket with another company?
Yes, if they also run Zendesk and both sides accept a sharing agreement. Without an accepted agreement in place, sharing is not available.
Do custom fields transfer when a ticket is shared?
Generally no. The two accounts have separate field definitions, so build your process on comments and tags rather than assuming field values arrive.
Is ticket sharing the same as merging tickets?
No. Sharing creates a linked copy in another account and keeps both alive. Merging combines two tickets in one account into a single conversation and closes the loser.
What is the alternative to ticket sharing inside one company?
Groups, side conversations or light agents, depending on whether the other team owns the work, answers a question, or just needs visibility.
Two accounts, two chances to duplicate
When work crosses a boundary, the same request often gets raised twice. Ticket Merger catches the repeats inside your own queue.
Start free trial14-day free trial. No credit card required.