Freshservice Merge Tickets, and the Duplicates Behind Them
Freshservice merge tickets the same way Freshdesk does. The harder question in an internal IT queue is which of the forty tickets from one outage should be merged at all.
How duplicates work on Freshservice
The shape of the problem, and the order to tackle it in.
Merge the genuine repeats
One frustrated requester raising the same thing three times is one request. Merge those and the queue count starts telling the truth.
Attach the crowd to an incident
Forty people reporting one outage each need their own update. Link them to a major incident rather than merging them away.
Fix the requester records
Duplicate requester profiles split one person history and make everything above harder. See merging requesters.
Freshservice merge tickets: how duplicates work here
External support duplicates are usually one customer contacting you twice. Internal IT duplicates are usually forty people reporting one outage, which needs the opposite response.
Merge the crowd and thirty-nine people get no reply on their own ticket. Ignore the crowd and your volume reporting says you had forty incidents when you had one.
The right split is to merge the genuine repeats, where one person raised the same thing more than once, and attach everyone else to a major incident so they all get the update when it is fixed.
What Freshservice does today
The native merge is good. Knowing what to merge is the part that is missing.
| Freshservice | With Ticket Merger | |
|---|---|---|
| Merge tickets on request | ||
| Merge requesters | ||
| Identify which tickets are repeats | Coming | |
| Leave incident crowds alone | Manual | Coming |
| Run during a spike without a technician | Coming |
What we are building for Freshservice
Requester matching
Directory sync and email rarely agree perfectly, and the gap creates duplicates.
Spike handling
Internal queues are flat until they are not. The response has to work at forty tickets in ten minutes.
Repeats versus incidents
Two different problems that look identical in the queue and need opposite treatment.
Rules you control
Thresholds and exclusions, so change requests and recurring maintenance are never touched.
Start on one group
Begin with one technician group and widen once the merges have earned trust.
On the roadmap
Freshservice is next after Zendesk and Freshdesk. Ask us and it moves up.
Freshservice guides worth reading
Written for the admin who needs it working today.
How to merge tickets in Freshservice
Selecting, choosing the primary, and when to associate with an incident instead.
Read moreHow to unmerge tickets in Freshservice
No one-click undo, and the recovery that keeps the audit trail clean.
Read moreMerging requesters in Freshservice
One employee with two profiles produces tickets that look unrelated.
Read moreFreshdesk vs Freshservice
Customers or colleagues. The routing decision behind the product choice.
Read moreIT ticketing systems compared
What internal IT needs that customer support tooling does not have.
Read moreFreshservice pricing calculator
Cost per agent per month across the tiers.
Read moreAll Freshservice guides
Every guide we have written about Freshservice, broken down by subject: setup, automation, reporting, integrations and the rest.
Read moreFrequently asked questions
How does Freshservice merge tickets?
Select the duplicates in the ticket list, choose Merge, and pick the primary. The secondaries close and their conversations move into the primary, exactly as they do in Freshdesk.
Does Ticket Merger support Freshservice yet?
Not yet. Ticket Merger connects to Zendesk and Freshdesk today, and Freshservice is next on the roadmap. Tell us you want it and we will let you know the moment it is ready, since we prioritise by how many people ask.
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.
The full Freshservice library
Everything we have written about this platform, most-searched first.
Freshservice support is coming
Ticket Merger runs on Zendesk and Freshdesk today, and Freshservice is next in the queue. Tell us you want it and we will let you know the week it lands.
Start free trial14-day free trial. No credit card required.