Freshdesk Linked Tickets, and When to Merge Instead
Freshdesk linked tickets are for when several customers each need their own answer. Merge when one customer asked twice. Mixing them up hides people who are still waiting.
Freshdesk linked tickets, or a merge?
| Situation | Do this | Because |
|---|---|---|
| One requester, two tickets, same question | Merge | Only one reply is going out |
| Fifteen customers, one outage | Link to a tracker ticket | Each needs their own reply and resolution time |
| A follow-up on a closed ticket | New ticket, linked | Different request, fresh SLA clock |
| Two colleagues, one company, same fault | Usually merge, sometimes link | Merge if one reply serves both |
Why this distinction matters more than it looks
Merging a set of incidents into one ticket looks tidy and without anyone noticing damages two things: fourteen customers never get a reply on their own thread, and your reporting records one ticket where fourteen people contacted you.
Ticket Merger takes the conservative side of this by default. It merges same-request pairs and leaves broad incident patterns for a human, because that call depends on whether one reply serves everyone, and only your team knows that.
Frequently asked questions
How do you link 2 tickets in Freshdesk, or split one?
How to link 2 tickets in Freshdesk: open the parent and add the other as a child. A Freshdesk split ticket goes the other way, taking one conversation and creating a second ticket from part of it.
What are Freshdesk linked tickets?
A parent ticket with children attached to it. Each child keeps its own requester and its own reply, and you can update all of them from the parent, which is exactly what an outage needs.
Does merging in Freshdesk lose the customer replies?
No. Ticket Merger uses the native Freshdesk 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.
Automate the obvious half
The same-request duplicates merge themselves. The judgement calls stay with your team.
Start free trial14-day free trial. No credit card required.