How to Find Duplicate Tickets in Zendesk

How to find duplicate tickets in Zendesk is harder than it sounds, because Zendesk search is built for finding a ticket, not for finding a pair.

How to find duplicate tickets in Zendesk natively

A view grouped by requester. Sort open tickets by requester and pairs jump out visually. It works, it takes a human every morning, and it only catches same-requester duplicates.
Search by subject fragment. Useful when you already suspect a duplicate. Useless as a routine sweep.
The `closed_by_merge` tag. Not a detector, but the best measure you have of how many duplicates you're already catching.
Merging suggestions. Helpful inside a ticket an agent has opened. See merging suggestions.

Every one of these needs a person to be looking. That's the flaw they share.

The Zendesk duplicate tickets that never get found

The pairs your team catches are the easy ones: identical subject, same person, minutes apart, both in the same view.

The ones that survive are worded differently, land in different views, arrive on different channels, or come from two people at the same company. They are also the expensive ones, because two agents work them in parallel and neither knows the other exists.

Continuous comparison finds those. Human review does not, and no amount of process discipline changes that.

FAQ

Frequently asked questions

How to easily see duplicate tickets in Zendesk?

Build a view sorted by requester and scan for the same person twice in a day. That's how to easily see duplicate tickets in Zendesk without an app, and it only catches the obvious half.

How do you find Zendesk duplicate tickets?

Sort a view by requester and look for the same person twice in a day, or search a distinctive phrase from the ticket. Both catch the obvious pairs and miss anything sent from a second address or worded differently.

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.

See your real Zendesk duplicate rate

Connect Zendesk and the first scan reports the number, by channel and by week. It's usually higher than anyone guessed.

Start free trial

14-day free trial. No credit card required.