How Ticket Merging Works, Exactly
No black box. Here is how ticket merging works: what Ticket Merger compares, when it decides two tickets are the same request, and what it leaves alone.
How ticket merging works, end to end
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, the subject keywords you list, 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 and keyword conditions
Match where the subject contains, equals or starts with the words you list, so a login keyword catches the login tickets.
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 narrow, then widen
Point Ticket Merger at one group first, with a tight rule: same requester, close subject match, a short time window. Watch it for a week on that slice of the queue. When the merges are consistently right, widen the window or add the next group. That is where most teams settle.
Frequently asked questions
How does ticket merging work?
Every new ticket is compared with the open queue on requester, subject keywords and a time window. If a pair clears your rules, the newer ticket is merged into the original through your helpdesk's API, with a note on the thread.
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?
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 it on your own queue
The trial runs against your real queue, so you can start it on one group and judge the merges on your own tickets before you widen it.
Start free trial14-day free trial. No credit card required.