Duplicate Ticket Detection That Catches Them On Arrival
Finding duplicates a week later is archaeology. Ticket Merger checks every incoming ticket against your open queue as it lands, so the duplicate never reaches an agent.
Why duplicates happen, no matter how good your team is
Duplicates are not an agent failure. They are a natural result of giving customers more than one way to reach you, which is exactly what you were told to do.
You cannot design these away without making it harder to contact you. What you can do is catch them automatically.
What detection looks at
Same requester, different address
Personal and work email, aliases, and multiple contacts inside one company domain.
Fuzzy subject and body match
Similarity scoring rather than exact match, because nobody writes the same sentence twice.
A time window you choose
Tight for high-volume consumer support, wider for slow-moving B2B queues.
Cross-channel pairs
Email plus web form is the single most common duplicate pattern there is.
Confidence thresholds
High confidence merges, medium confidence gets suggested, low confidence is ignored.
A real duplicate rate
Stop guessing. See the actual percentage, by channel and by week.
Detection without merging is just another queue
Plenty of tools will tell you that two tickets look similar. That is a notification, and notifications become a second inbox nobody reads.
Ticket Merger is built the other way round: detection exists so the merge can happen automatically. The default outcome is one ticket, one thread, one answer, with a note explaining what happened. You only get involved for the borderline cases you asked to see.
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 your real duplicate rate
The first scan runs against your open queue as soon as you connect. Most teams are surprised by the number.
Start free trial14-day free trial. No credit card required.