How to Link Tickets in Zendesk, Not Merge Them
How to link tickets in Zendesk matters because merging is for one request that arrived twice, and linking is for different requests that share a cause.
Merge or link?
| Situation | What to do | Why |
|---|---|---|
| Same person, same problem, twice | Merge | One request, one thread, one answer |
| Ten customers reporting one outage | Link to a problem ticket | Each needs their own reply and their own resolution time |
| A follow-up question on a solved ticket | Link | Different request, different SLA clock |
| One email that contains three unrelated requests | Split | Each needs its own owner and its own close |
| Same company, same outage, two reporters | Judgement call | Merge if one reply serves both. Link if both need updating. |
How to link tickets in Zendesk, in practice
Zendesk gives you a few ways to express a relationship without collapsing the tickets: parent and child style problem and incident tickets, side conversations, and simple cross-references in a private note. Which one fits depends on whether you need the child tickets to close automatically when the cause is fixed.
The important discipline is deciding deliberately. Merging an incident that needed its own reply hides a customer who is still waiting, and that's a worse outcome than the duplicate you were trying to clean up.
Frequently asked questions
How do you show Zendesk related tickets to an agent?
Through the problem and incident types, a shared tag, or an app in the sidebar. Zendesk related tickets are not a native field, so whichever route you pick becomes a convention the team has to follow.
How do you link tickets in Zendesk?
Zendesk has no generic link action. You relate tickets with the problem and incident types, with a shared tag or custom field, or by referencing the ticket ID in a comment so agents can move between them.
Does merging in Zendesk lose the customer replies?
No. Ticket Merger uses the native Zendesk merge, so the conversation, attachments and audit history move onto the surviving ticket. The duplicate is closed with a note pointing at the original.
Can I review merges before they happen?
No. Once a pair matches your rules, Ticket Merger merges it. What you control is what qualifies: requester, the subject keywords you list, the time window, and the groups, forms or tags you exclude. To see how it behaves before it touches everything, point it at one group first and widen from there. Every merge leaves a note on the thread saying what was merged and why.
What stops it merging two tickets that are not the same?
Rules you set. Match on requester, subject keywords, status, priority, category or group, and a time window, and exclude anything you want left alone, like tickets from a specific form, group or tag. Anything that does not clear those rules is left alone.
How long does setup take?
About five minutes to connect, and the first scan of your open queue runs immediately after. Onboarding help is included on every plan.
Let the obvious duplicates merge themselves
Ticket Merger only merges same-request pairs, and leaves the related-but-different ones for your team to link.
Start free trial14-day free trial. No credit card required.