Zendesk Merging Suggestions, Honestly Reviewed
Zendesk merging suggestions are a genuinely useful feature with a narrow remit. Worth turning on, and not a duplicate strategy on their own.
What Zendesk merging suggestions actually do
Zendesk can surface related tickets from the same requester and offer to merge them, so an agent working a ticket sees the other one without going looking. An admin turns it on in the Support settings, and after that it appears inside the ticket for agents.
When it fires, it's excellent: the agent gets the pair in front of them and merges in two clicks instead of searching.
Where it stops
Merging suggestions versus automatic merging
| Zendesk suggestions | Ticket Merger | |
|---|---|---|
| Shows a likely duplicate to an agent | ||
| Works before any agent opens the ticket | ||
| Merges without a human | ||
| Matches across different requesters at one company | ||
| Your own thresholds and exclusions | ||
| Runs overnight and at weekends | ||
| Reporting on your real duplicate rate |
Use both
This isn't an either-or. Turn merging suggestions on, because a free feature that helps agents is a free feature that helps agents.
Then put automatic merging underneath it for everything suggestions can't see: the pairs nobody has opened, the cross-requester duplicates, and the 60 hours a week when your team isn't at their desks.
Frequently asked questions
How does Zendesk decide two tickets are similar?
Zendesk similar tickets are matched on the same requester plus overlapping subject text, inside a recent window. That's why merging suggestions catch the honest repeats and miss anything sent from a second address.
How do Zendesk merging suggestions work?
When an agent opens a ticket, Zendesk looks for other tickets from the same requester that look similar and offers them for merging. The agent decides. It never merges anything on its own.
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.
Cover the gap suggestions leave
Ticket Merger works the queue, not the open ticket, so duplicates get caught before an agent ever sees either one.
Start free trial14-day free trial. No credit card required.