Zendesk Duplicate Tickets, Merged Automatically
Zendesk duplicate tickets are easy to merge and hard to notice. Zendesk gives you a merge button and, on some plans, a suggestion. Neither one watches your queue at 2am.
How it works on Zendesk
Connect once. After that it runs without anybody thinking about it.
Connect Zendesk
Create an API token, paste it in, and choose which views to watch. Nothing changes for your agents on day one.
It reads the open queue
Every arriving ticket is compared against everything still open: same requester, your subject keywords, inside a window you set.
It merges natively
Matches are merged with the same Zendesk merge an agent would use, tagged closed_by_merge, with a private note recording the reason.
Why Zendesk duplicate tickets keep appearing
Zendesk is good at taking tickets in from everywhere: email, web form, Web Widget, chat, API, social. That is the product working correctly, and it is exactly why one person ends up with two open tickets about the same thing.
The usual pattern is email plus web form. Someone writes in, hears nothing for an hour because your first reply target is four, then fills in the form on your help centre. Two tickets, two views, two agents, one increasingly annoyed customer.
Zendesk will merge them happily once you tell it to. Nobody on your team is looking for the pair.
Zendesk on its own, and with Ticket Merger
The native merge is good. Knowing what to merge is the part that is missing.
| Zendesk | With Ticket Merger | |
|---|---|---|
| Merge two tickets on request | ||
| Suggest related tickets from the same requester | ||
| Watch the queue before an agent opens anything | ||
| Match across different requesters at one company | ||
| Match across email, form, chat and API | ||
| Run overnight and at weekends | ||
| Your own thresholds and exclusions | ||
| Report your actual duplicate rate |
What you get on Zendesk
Real-time detection
Checks run as tickets land, not in an overnight batch, so the duplicate never reaches an agent.
Identity beyond the email
Matches verified users, secondary addresses and colleagues on one company domain.
Rules you control
Thresholds, time windows and exclusions by group, brand, form or tag. Exclusions always win.
Start on one group
Point it at a single group with a tight rule, watch the merges for a week, then widen it.
Documented merges
Every merge writes a note with the match, the score and the rule that fired.
Your real duplicate rate
By channel and by week. Most teams have never seen this number.
Zendesk guides worth reading
Written for the admin who needs it working today.
How to merge tickets in Zendesk
The exact steps, what happens to comments and tags, and why the merge cannot be undone.
Read moreMerge Zendesk tickets automatically
Why no trigger can do it, and what rule-based merging looks like instead.
Read moreHow to unmerge a ticket in Zendesk
The honest answer, and the three-minute recovery when a merge was wrong.
Read moreZendesk merging suggestions reviewed
What the native feature catches, and the gap it leaves.
Read moreFinding duplicate tickets in Zendesk
What you can do with views and search, and which duplicates always survive it.
Read moreMerging users in Zendesk
Duplicate profiles create duplicate tickets. Fixing the user fixes the cause.
Read moreAll Zendesk guides
Every guide we have written about Zendesk, broken down by subject: setup, automation, reporting, integrations and the rest.
Read more"We knew we had duplicates. We had no idea it was one ticket in eight. The first week paid for the year."
Frequently asked questions
How do you find Zendesk duplicate tickets?
Natively, by sorting a view by requester and reading it. Merge suggestions catch some same-requester pairs, and anything sent from a second address or worded differently stays invisible.
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.
The full Zendesk library
Everything we have written about this platform, most-searched first.
See your Zendesk duplicate rate
Connect with an API token and the first scan of your open queue runs immediately. No change to how your agents work, and nothing merges until you say so.
Start free trial14-day free trial. No credit card required.