Customers file duplicate tickets all the time. They reply to an old auto-response, they submit on the portal then call in, they cc a colleague who refiles. Merging is the right answer, but the merge button hides three traps.
What merge actually does
Freshdesk merge takes two or more tickets and consolidates them into a single primary ticket. All conversations, attachments, and notes from secondary tickets append to the primary in chronological order. Secondary tickets close with a status note pointing to the primary.
The customer sees the primary ticket only on the portal. Past replies on secondaries no longer trigger new tickets; they append to the primary thread.
Trap 1: agent assignment
Merging does not change ownership. The primary keeps its current owner; the secondary’s owner loses the ticket. If the secondary owner was actively working on it, they are not notified. Set up a workflow to notify the secondary owner when their ticket gets merged into another.
Trap 2: SLA reset
The primary keeps its SLA clock. The secondary’s SLA disappears. If the secondary was older and closer to breach, you just lost the worse case. Always merge the older into the newer when both are similar age, or pick the one with worse SLA standing as the primary.
Trap 3: custom field collisions
Custom field values on secondaries do not merge in. The primary’s values win. If the secondary had a more detailed problem description in a custom field, copy it manually before merging.
Pattern for support duplicates
Customer files via portal, then emails. Two tickets, same issue. Default merge: pick the one with more conversation history as primary, merge the other in. Reply once on the primary acknowledging both inquiries.
Configure a duplicate-detection automation: when a new ticket arrives from the same requester with similar subject within 24 hours, auto-suggest merge. Do not auto-merge; that surprises customers when their second message disappears.
Pattern for billing duplicates
Billing duplicates often come from finance and the customer separately. Both want resolution. Merge into the customer-facing ticket and add finance as a watcher (CC). This way finance gets updates without owning the ticket.
Pattern for major incident
During an outage, you may get 200 tickets about the same issue. Do not merge all 200; that creates a primary ticket with 200 different requesters and merge becomes irreversible. Instead, link them all to a single “Major Incident” parent ticket and use the broadcast feature to update all linked tickets at once.
Linked tickets close independently when each customer confirms resolution. Merge would close them all simultaneously.
Undo and audit
Merge is reversible within 30 days via the ticket history panel on the primary, but it is messy. The unmerged ticket comes back as a new ticket with a new ID; the original ID is gone. Treat merge as one-way for practical purposes.
Merge across requesters
Default Freshdesk does not allow merging tickets from different requesters. This prevents accidental privacy breaches. If two requesters from the same account both file the same issue, merge into one and cc the other rather than overriding the protection.
What to do this week
Audit your duplicate-detection automation. If you do not have one, build it: trigger on new ticket from existing requester, check for open tickets in last 24 hours with similar subject, post an internal note suggesting merge.
