How to Merge Tickets in Zendesk

Four clicks, one caveat that catches people out: in Zendesk, a merge is permanent.

Merging a Zendesk ticket, step by step

Work from the ticket you want to close, not the one you want to keep. Zendesk merges the ticket you are viewing into the one you name.

1

Open the ticket you want to close

This is the duplicate. Everything in it moves to the ticket you are about to name, and this one ends up closed.

2

Ticket options, then Merge into another ticket

The Ticket options menu sits in the upper right of the ticket. Choose Merge into another ticket.

3

Enter the ticket number and confirm

Type the ID of the ticket you are keeping, click Merge, review the comment Zendesk is about to add, then click Confirm and merge.

What actually happens when you merge

  • The most recent public comment from the closing ticket is copied into the surviving ticket, along with a link back. You can edit or remove that comment in the merge window before you confirm.
  • Ticket fields do not travel. Tags, type, priority and status from the closing ticket are not carried over, so anything you needed from those fields has to be set manually on the survivor.
  • The closed ticket picks up the tag `closed_by_merge`, which is genuinely useful: build a view on it and you can see how much merging your team is doing.
  • The merge is permanent. Zendesk does not offer an unmerge.
  • Tickets Zendesk will refuse to merge

    SituationCan you merge?What to do instead
    Ticket is Solved or ClosedNo, tickets must be less than SolvedReopen the ticket first, then merge
    Ticket is shared with another Zendesk instanceNoUnshare it, then merge
    Different requestersYes, but check firstConfirm they are the same human before merging, since the requester does not change
    Custom agent role on EnterpriseOnly if the role grants merge permissionAn admin adds the merge permission to the role
    More than two ticketsYes, one at a timeMerge each duplicate into the survivor in turn

    The part that is not in the documentation

    Merging is easy. Noticing is not.

    To merge a duplicate an agent has to know the other ticket exists. That ticket might be in a different view, assigned to someone on another shift, worded nothing like the one in front of them, and already answered. By the time somebody spots the pair, both customers have had a reply and the merge no longer saves anyone anything.

    That is why teams with a merge button still have a duplicate problem, and why merging Zendesk tickets automatically is a different job from merging them manually.

    Frequently asked questions

    Can you unmerge tickets in Zendesk?+

    No. Zendesk merges are permanent. The closest thing to a fix is to open a new ticket for the content that should not have been merged. See unmerging in Zendesk.

    Can I merge more than two tickets at once?+

    Not in a single action. Merge each duplicate into the surviving ticket one at a time. If this is a regular chore, that is a sign the duplicates should be caught automatically.

    What happens to the requester and CCs?+

    The surviving ticket keeps its own requester. The requester of the closed ticket is not added automatically, so if two different people reported the same issue, add the second one as a CC yourself.

    Does merging affect my reporting?+

    Yes, in a good way. The closed duplicate is tagged `closed_by_merge`, so you can exclude merged tickets from volume and handle-time reporting and finally see real numbers.

    Can Zendesk merge tickets automatically?+

    Zendesk offers merging suggestions on some plans, which flag likely duplicates for an agent to confirm. Fully automatic merging, with your own rules, needs a tool like Ticket Merger.

    Never hunt for a Zendesk duplicate again

    Ticket Merger watches your Zendesk queue and merges the duplicates through the same native merge you just read about, before an agent opens either one.

    Start free trial

    14-day free trial. No credit card required.