Merge Zendesk Tickets Automatically
Triggers and automations can do almost anything in Zendesk. Merging is the one thing they can't do. That is the gap Ticket Merger fills.
Why a Zendesk trigger cannot merge tickets
Zendesk triggers fire on one ticket at a time. They can set fields, notify people, add tags and route work, and none of that helps here, because merging is a decision about a relationship between two tickets. A trigger looking at ticket 41822 has no way to know that ticket 41805 is the same request from the same person twenty minutes earlier.
The Zendesk API can perform a merge. Somebody still has to decide which two tickets to merge, and that's the whole problem.
Ticket Merger does the deciding. It holds a live picture of your open queue, compares every arriving ticket against it, and calls the merge endpoint when your rules say the pair is a duplicate.
What you control
Automation is only worth having if it behaves predictably. Every one of these is yours to set.
Requester matching
Same user, same email, or any address on the same company domain. Strict for consumer support, looser for B2B.
Similarity thresholds
How close two subjects and bodies need to be before it counts. Merge above one number, suggest above another, ignore below.
Time window
Ten minutes, two hours, three days. Match it to your first reply time and duplicates land inside it.
Exclusions
Groups, brands, ticket forms, tags and specific requesters that must never be merged. Exclusions always beat matches.
Suggest-only mode
Every rule can run in suggest mode first, so agents approve the merges while you tune the numbers.
Merge notes
Each merge writes a private note explaining the match, the score and the rule that fired.
Your options for automatic merging in Zendesk
| Approach | Catches duplicates on arrival | Merges without an agent | Rules you control |
|---|---|---|---|
| Manual merge | |||
| Zendesk merging suggestions | |||
| Custom script on the API | You build and maintain it | ||
| Ticket Merger |
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.
Turn it on in five minutes
Connect Zendesk, run a week in suggest mode, then let the confident matches merge on their own.
Start free trial14-day free trial. No credit card required.