Linking Tickets in Zendesk, Not Merging Them
Merging is for one request that arrived twice. Linking is for different requests that share a cause. Getting this wrong buries real work.
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 linking works 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 is a worse outcome than the duplicate you were trying to clean up.
Frequently asked questions
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?+
Yes. Start in suggest-only mode: Ticket Merger flags the pairs it believes are duplicates and leaves the decision to an agent. Most teams run that way for a week, check the hit rate, then let the confident matches merge on their own.
What stops it merging two tickets that are not the same?+
Rules you set. Match on requester, subject similarity, body similarity and a time window, and exclude anything you want left alone, like tickets from a specific form, group or tag. Anything below your confidence threshold gets suggested rather than merged.
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.