How Automatic Ticket Merging Actually Works
No black box. Here is precisely what Ticket Merger compares, when it decides two tickets are the same request, and what it leaves alone.
How Ticket Merger works
Three steps, and only the first one needs you.
Connect your helpdesk
Paste an API key and pick the views you want watched. It takes about five minutes and nothing changes for your agents on day one.
It spots the duplicates
Every new ticket is checked against the open queue: same requester, similar subject, matching content, inside a time window you set. You decide how strict that is.
It merges them for you
The duplicate is merged into the original through your helpdesk own API, with a note on the thread explaining what happened. History, attachments and the audit trail stay intact.
What gets compared
A duplicate is rarely an exact copy. These signals are weighed together, and you decide how much each one matters.
Requester identity
Same email, same verified user, or the same contact behind two different addresses on one domain.
Subject similarity
Fuzzy matching, so "Cannot log in" and "Can not login to my account" land together.
Body content
Similarity across the message body, with quoted signatures and reply chains stripped out first.
Time window
Two tickets ten minutes apart are almost always a duplicate. Two a month apart usually are not. You set the window.
Channel pattern
The classic duplicate is one person using email and the web form. Cross-channel pairs get extra weight.
Your exclusions
Recurring tickets, monitoring alerts, order numbers, specific forms or groups: tell it once, it never touches them.
What your agents see
Nothing new to learn, which is the point. The surviving ticket picks up the conversation from the duplicate, and a private note explains what was merged and why. The closed ticket points at the survivor so anyone following a link still ends up in the right thread.
If a merge was wrong, you undo it the same way you would undo any other action in your helpdesk, and Ticket Merger learns that pair should be left alone.
Start cautious, then loosen
Every team we onboard starts in suggest-only mode. Ticket Merger flags candidates, an agent approves or rejects, and you watch the accuracy for a week. Once the confident matches are consistently right, you let those merge on their own and keep the borderline ones as suggestions. That is where most teams settle.
Frequently asked questions
Does merging in your helpdesk lose the customer replies?+
No. Ticket Merger uses the native your helpdesk 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.
See it on your own queue
The trial runs against your real tickets in suggest mode, so you can judge the accuracy before anything is merged.
Start free trial14-day free trial. No credit card required.