How to Merge Tickets in Zendesk (Step by Step)
A customer emails about a broken checkout, hears nothing for an hour, then emails again — and now you have two tickets for one problem. Multiply that across a busy queue and you get duplicate work, conflicting replies, and a confused customer who gets two different agents. The fix is merging: Zendesk lets you fold one ticket into another so all the history lives in a single thread. This guide walks through exactly how to do it, step by step, plus the rules that trip people up — chiefly that a merge is effectively permanent, so it pays to get it right the first time.
If you want the bigger picture of how tickets, statuses, and the queue fit together, our guide to the Zendesk ticketing system is the companion read. This post is the hands-on how-to. Every step below is verified against Zendesk's own documentation; Zendesk does revise its UI periodically, so confirm the labels in your own account.
Why merge tickets in the first place?
Merging exists for one core scenario: two or more tickets that are really the same conversation. The usual culprits:
- A customer replies from a different email address, or starts a fresh email instead of replying to the existing thread, spawning a second ticket.
- The same person reaches you across channels — a web form and a chat and an email — about one issue.
- A customer gets impatient and re-submits before the first ticket is answered.
When you merge, you stop two agents from working the same problem in parallel, you keep the full context in one place, and you keep your metrics honest — duplicate tickets quietly inflate volume and skew your reporting. The goal is one customer, one issue, one thread.
Before you start: who can merge, and what can't be merged
Two quick checks save a lot of frustration:
- Permissions. On most plans, agents can merge tickets by default. On Enterprise, merging can be gated behind a custom role permission — if you don't see the option, ask an admin to grant it.
- The tickets must be mergeable. You can only merge tickets that are less than Solved (Open, Pending, or a custom status in those categories). You cannot merge a Closed ticket — once a ticket is Closed it's locked, and a merge can't touch it. You also can't merge shared tickets or AI agent tickets. (For a refresher on what each status means, see Zendesk ticket statuses explained.)
One useful nuance: while the ticket you merge from must be less than Solved, you can merge an unsolved ticket into a Solved one — and doing so will not reopen the Solved ticket.
Decide which ticket to keep
Before you click anything, pick your target — the ticket that survives. The other ticket is the one that gets closed. A good rule of thumb: keep the ticket with the most useful context (the longer thread, the right assignee/group, the correct fields) and merge the thinner duplicate into it.
This matters because ticket fields don't carry over. Tags, Type, Priority, Status, and custom fields from the ticket being closed are not copied to the survivor — only the fields already filled in on the target ticket are kept. So make the ticket you want to keep the one that's already set up correctly.
Step 1 — Open the ticket you want to merge from
Open the duplicate — the ticket you're willing to close. In Zendesk's Agent Workspace, the merge action lives on the ticket itself, not in any admin page.
A small but important framing point: you merge from the ticket you're viewing into another ticket. So whatever ticket is open when you start the merge is the one that gets closed. If that feels backwards, just remember: open the throwaway, send it into the keeper.
Step 2 — Open the ticket options menu and choose "Merge into another ticket"
In the upper-right corner of the open ticket, click the Ticket options menu (the "more" menu — the icon with the three dots / arrow). From the dropdown, select Merge into another ticket.
This opens the merge dialog, where you'll identify the target and review what's about to happen. Nothing is committed yet, so it's safe to open it and look.
Step 3 — Find and select the target ticket
In the merge dialog, point Zendesk at the ticket you want to keep. You have three ways to do it:
- Enter the ticket number directly and click Merge — fastest if you already know it.
- Select from the requester's open tickets — handy when the same customer has more than one ticket open.
- Select from your recently viewed tickets — convenient if you just had the keeper open.
Pick whichever fits, and Zendesk loads a preview of the merge so you can confirm you've got the right target.
Step 4 — Clear the warning if requesters, brands, or orgs differ
If the two tickets have different requesters, brands, or organizations, Zendesk shows a warning before it lets you continue. This is a deliberate guardrail: merging tickets from two different people means one person's conversation gets attached to another's.
Read the warning, make sure you're not about to expose one customer's details to another, and if it's genuinely correct, click Continue Merge. (A common, legitimate case is two different email addresses that belong to the same human.) Note that to merge tickets with different requesters, your account needs ticket CCs enabled.
Step 5 — Review (and trim) the auto-added private comments
Zendesk automatically adds a comment to both tickets explaining the merge and linking them together, so the trail is never a mystery later. Before you confirm, review them:
- By default these merge comments are private (internal notes). If you want the requester to not see the merge note, leave "Requester can see this comment" deselected.
- You can edit the comment text. If you empty the comment box entirely, Zendesk falls back to displaying the merged ticket's most recent comment instead.
This is the moment to decide how visible the merge should be. For an internal cleanup of two duplicates, keeping the notes private is usually right.
Step 6 — Confirm and merge
When everything looks right, click Confirm and merge.
That's it — the merge runs immediately. Before you click, take this seriously: a merge cannot be undone. There is no "un-merge" button in Zendesk. If you target the wrong ticket, the only remedy is manual cleanup, and the closed ticket stays closed.
What actually happens after a merge
Once you confirm, here's the exact result:
- **The ticket you merged from is set to Closed. It's no longer editable, and it picks up the system tag
closed_by_merge** so you (and your reports) can identify merged-away tickets later. - A linking comment is added to both tickets, so each one points to the other.
- The requester of the closed ticket becomes a CC on the surviving ticket — so they stay in the loop on the conversation that continues.
- Only the most recent public comment from the closed ticket transfers across with the merge link (and note that HTML formatting is lost in transferred content — it comes over as plain text).
- The requester is notified per your settings. Whether the customer sees anything depends on how you set the comment visibility in Step 5 and your account's notification triggers.
The surviving ticket keeps its own fields and assignee; you continue the conversation there as normal.
A note on duplicates at scale
Merging is a one-at-a-time, manual action — there's no native "bulk merge" button that fuses a stack of tickets in one click. For a handful of duplicates that's fine. When duplicates are a recurring drain, two things help:
- Merge suggestions. On Zendesk's Copilot add-on, Zendesk surfaces a Related tickets section in the context panel that flags tickets it thinks might be duplicates, with a red badge when new suggestions appear. It's still a human who reviews and confirms each merge.
- Prevention beats cleanup. Triggers and good intake design (clear "check your existing tickets" messaging, requiring sign-in) cut down on duplicates landing in the first place.
Where AI fits
Spotting that two tickets are the same conversation is exactly the kind of pattern-matching an AI layer is good at. An AI agent layer like Macha runs on top of your existing Zendesk — it isn't a help desk and it isn't a Zendesk replacement — and it can read incoming tickets, recognize when a new one looks like an open issue from the same customer, and flag the likely duplicate for an agent to review (rather than silently merging, since a merge can't be reversed). It can also handle the routine tagging and triage around those tickets. On cost, Macha bills per AI action — any automated step it takes, like detecting a duplicate, tagging, or drafting a reply — not per closed or resolved ticket, because most of that work isn't a "resolution," it's the cleanup along the way. The honest caveat: it's another integration to set up, and a human should still own the irreversible click. If duplicate volume is genuinely eating your team's time, you can try it free — 7-day free trial, no credit card required.
Best practices and common mistakes
- Merge into the better-set-up ticket. Fields don't carry over, so make the survivor the one with the correct assignee, group, tags, and priority. The classic mistake is keeping the bare-bones duplicate and losing the context.
- Double-check the requester before clicking Continue Merge. Merging two different people's tickets exposes one customer's thread to another. Only do it when you're sure it's the same human.
- Don't treat merge as "undo-able." It isn't. If you're unsure, link the tickets or add a note first, and confirm the target twice before you commit.
- Decide comment visibility deliberately. Leaving the merge note public when it should be private can send an internal-sounding message to the customer.
- Catch duplicates early. A ticket that's already Solved or Closed can't be the source of a merge — so clean up duplicates while they're still Open or Pending, not days later.
Frequently asked questions
How do I merge two tickets in Zendesk? Open the duplicate ticket (the one you'll close), click the Ticket options menu in the upper-right corner, and select Merge into another ticket. Identify the target — by ticket number, from the requester's open tickets, or from recently viewed tickets — review the auto-added private comments, then click Confirm and merge.
Can I merge a closed ticket in Zendesk? No. A Closed ticket is locked and can't be merged. The ticket you merge from must be less than Solved (Open or Pending). You can, however, merge an unsolved ticket into a Solved ticket, and it won't reopen the Solved one.
Can you un-merge tickets in Zendesk? No — a merge is permanent and can't be undone. There's no un-merge button. If you merge into the wrong ticket, the closed ticket stays closed and you'd have to recreate context manually, so confirm the target carefully before clicking.
What happens to the ticket I merge from? It's set to Closed, becomes uneditable, and gets the closed_by_merge tag. A comment links it to the surviving ticket, its requester is added as a CC on that ticket, and its most recent public comment carries over with the merge link.
Can I merge tickets from two different customers? Yes, but Zendesk warns you first, and you must click Continue Merge to proceed. Merging different requesters requires ticket CCs to be enabled on your account. Only do it when the two requesters are genuinely the same person (e.g. two of their email addresses).
Why don't my tags and fields carry over after a merge? By design. Ticket fields — Tags, Type, Priority, Status, and custom fields — are not copied from the ticket being closed. Only the fields already filled in on the surviving ticket are kept, which is why you should merge into the ticket that's already set up correctly.
The bottom line
Merging tickets in Zendesk is quick: open the duplicate, use the Ticket options → Merge into another ticket menu, pick the ticket you want to keep, review the private linking comments, and click Confirm and merge. The ticket you merged from goes to Closed with a closed_by_merge tag, its requester is added as a CC on the survivor, and the two threads are linked. The one rule to burn into memory: a merge can't be undone, and Closed tickets can't be merged — so pick the right survivor, double-check the requester, and confirm before you commit. For how merging fits the wider workflow, see our Zendesk ticketing system guide and the breakdown of ticket statuses.
Merge steps verified against Zendesk's official documentation, June 2026. Zendesk updates its product periodically — confirm labels in your own account before relying on them.
