How to Merge & Unmerge Tickets in Freshdesk

What merging actually does

When you merge tickets in Freshdesk, one ticket you nominate becomes the primary and the rest become secondary. Per Freshworks' Merging two or more tickets together documentation, all conversations from the secondary tickets are moved into the primary ticket and sorted chronologically, so the primary ends up holding the full, time-ordered history of the issue.

A few things happen automatically the moment you confirm:

• The secondary tickets are closed — they don't vanish, they're just resolved and moved out of the active queue.
• A note is added to each ticket with a link to the primary, so anyone landing on a secondary later can follow the trail.
• You can optionally keep the secondary requesters and CC'd people in the loop on the primary by ticking "Add secondary ticket recipients to CC."

That last option matters more than it looks. If three separate customers reported the same bug and you merge their tickets, leaving the box unchecked means only the primary requester hears the eventual resolution — the others go silent. Tick it when the duplicates come from different people; leave it unchecked when they're all the same person emailing twice.

Step 1: Select the tickets and choose your primary

There are two ways in, and both start from the Tickets tab.

1. In the ticket list, use the checkboxes to select every ticket you want to fold together, then click Merge in the action bar. (Alternatively, open one ticket and click Merge from inside it, then pull the others in.)
2. In the merge dialog, use the Contact filter and search box to find and add candidate tickets — you can add more with the search bar and dropdown, or remove one with the minus icon.
3. Mark which ticket should be Primary — a tick appears next to the one you've chosen. Everything else becomes secondary.
4. Decide whether to tick "Add secondary ticket recipients to CC."
5. Click Merge to confirm.

Notice in the modal above that the candidate search is scoped by contact and matches on ticket ID or contact, not on subject text — so even three tickets all titled "Where is my refund?" won't auto-select each other. You still confirm each secondary deliberately. That's a safety feature, not a bug: merging is permanent, so Freshdesk makes you point at each ticket on purpose.

Which ticket should be the primary?

The primary ticket is the one that survives as the living record, so choose it with intent rather than grabbing whichever is on top:

The trap teams fall into: merging into the newest ticket because it's the one open on screen, then discovering the primary has the wrong priority or a blank custom field. Set the primary's fields correctly before you merge, because the secondaries won't fix them for you.

Step 2: Make sure the right people can merge

Merging isn't open to everyone by default configuration. Anyone holding a default role — Account admin, Admin, Supervisor, or Agent — can merge tickets out of the box. But if your team runs on custom roles, an agent won't see the option until the merge/split ticket permission is enabled for their role under Admin → Team → Roles. If a teammate swears the Merge button is missing, that permission is almost always why.

Can you unmerge tickets in Freshdesk? (The honest answer)

Short version: no, not really. Freshworks is blunt about it in How to undo ticket merging: "Merging is an irreversible process. Once two tickets are merged it cannot be split." There is no "unmerge" button, and the conversations that moved into the primary don't split back out.

What you can do is a manual workaround that gets you close. Because the secondary tickets were closed, not deleted, they still exist. If you merged in error, you can:

1. Find the secondary ticket (follow the merge note's link, or search by its ID).
2. Reopen it by changing its status back to Open — it returns to the active queue as its own thread again.
3. Optionally delete the auto-added merge note on both tickets to reduce confusion.

The catch is that this doesn't un-move the conversation replies that were merged into the primary. Reopening the secondary gives you a working ticket again, but the two threads' histories won't cleanly separate back to their original state. Treat merging as a one-way door: get the primary right the first time, and lean on the "add secondary recipients to CC" option rather than expecting to reverse a mistake later.

Step 3: Stop merging by hand with the Auto Ticket Merger app

Merging one duplicate at a time is fine; merging fifty is not. Freshworks publishes a free first-party Auto Ticket Merger app that folds duplicates together automatically. Per the Auto Ticket Merger setup guide, you install it from Admin → Support Operations → Apps, then configure a few rules:

• Window Duration — the time period, in minutes, during which tickets from the same contact get merged. A 30-minute window, for example, catches the customer who emails twice in a panic but leaves next week's separate issue alone.
• Exclude Emails and Domains — contacts whose tickets should never be auto-merged (use the @domain.com syntax to exclude a whole domain).
• Include Emails and Domains — contacts whose tickets should be merged regardless of the time window.

The critical thing to understand is how it matches: the app's primary connector is the contact's email ID. It merges tickets from the same email address inside your window — it does not read subject lines or ticket bodies to judge whether two tickets are truly about the same thing.

The honest limits — and where an AI layer picks up

The Auto Ticket Merger is a solid, free, first-party tool, and for the common case — one customer, two emails, a few minutes apart — it just works. But be clear-eyed about its boundaries, because they're real:

• Email only. The app matches on email ID, so it will not merge tickets raised via Facebook or Phone. A customer who emails and calls creates two threads it can't connect.
• No mandatory fields. The app cannot merge tickets that have mandatory fields. If your ticket form requires a category or reason, auto-merge stops working until that requirement is relaxed.
• Same person, same window — nothing smarter. It merges by who and when, not by what. Two customers reporting the identical outage from different addresses won't be merged, and one customer with two genuinely different problems in the same window might be merged when they shouldn't.

Those gaps are the seam where an AI agent layer helps — and it's worth weighing the build-versus-buy tradeoff before you reach for one. Macha is one such layer: it runs on top of the Freshdesk you already use as a native connector, and it does not replace your help desk or its merge feature. Instead of matching duplicates by email address, an agent reads each ticket by intent across channels — so a refund question that arrives once by email and again by another channel can be recognised as the same underlying issue and answered consistently, rather than sitting as two threads waiting to be merged. Better still, a duplicate you never have to merge is one where the first ticket already got a good answer — Macha can draft or post a grounded first reply (backed by a canned response or a live lookup) fast enough that the customer never emails a second time. When the answer needs real account data, a custom tool lets the agent pull an order or refund status through your own API. (Macha's connector is for Freshdesk specifically — not Freshchat, Freshservice, or Freshcaller. And credits are consumed per AI action, not per resolution — see the pricing breakdown.)

The clean division of labour: keep Freshdesk's merge feature and the Auto Ticket Merger for the deduplication housekeeping they're built for, and layer an agent on top to answer fast enough — and reason well enough — that fewer duplicates get created in the first place.

FAQ

How do I merge tickets in Freshdesk? From the Tickets tab, select the tickets with their checkboxes and click Merge (or open a ticket and click Merge inside it). In the dialog, mark one ticket as Primary, optionally add or remove candidates via the contact-scoped search, decide whether to tick "Add secondary ticket recipients to CC," and confirm. The secondary tickets are closed and their conversations move into the primary in chronological order.

Can I unmerge tickets in Freshdesk? Not truly. Freshdesk states that merging is irreversible and cannot be split. The practical workaround is to reopen the secondary tickets — they were closed, not deleted — but this won't cleanly separate the conversation history that was already moved into the primary.

What is the Auto Ticket Merger app? A free first-party Freshworks app, installed from Admin → Support Operations → Apps, that automatically merges tickets from the same contact within a Window Duration you set in minutes. It matches by the contact's email ID and supports exclude/include lists by email or domain.

Why won't the Auto Ticket Merger merge some of my tickets? Because it matches on email ID, it won't merge tickets from Facebook or Phone, and it cannot merge tickets that have mandatory fields. If a merge you expected didn't happen, one of those two limits is usually the reason.

Who is allowed to merge tickets in Freshdesk? Agents with a default role (Account admin, Admin, Supervisor, or Agent) can merge out of the box. For custom roles, the merge/split ticket permission must be enabled under Admin → Team → Roles.

Want fewer duplicates to merge in the first place? Start a free trial of Macha and connect it to your Freshdesk in minutes.