How Do You Merge Duplicate Tickets in Zendesk?
Video
A customer who emails twice becomes two tickets, two agents and two different answers. How to merge the duplicate in Zendesk, what the merge does to each ticket, and the limit to know before you confirm.
Chapters
Two tickets, one customer
A customer who hears nothing emails again, and Zendesk opens a second ticket. The two can land with different agents in different groups. Both agents answer in good faith, neither can see the other's reply, and the customer ends up with two emails from the same company saying two different things. The queue also looks busier than it is, and the metrics look worse.
This walkthrough follows one delayed order through that split. Ticket 28 goes to payments and refunds, where the agent checks with logistics and gives a delivery date. Ticket 29 goes to support, where the agent has no history and promises to chase the courier.
Merging the duplicate
From the duplicate ticket, the ticket options menu opens Merge tickets. Step one picks the destination ticket, and Zendesk warns you when the two tickets have different requesters. Step two shows the comment each ticket will receive: the source is marked as merged and closed, and the destination picks up the source's last comment.
After the merge, ticket 29 is closed and ticket 28 carries the whole conversation, so whoever works it next has the full context.
Reporting and limits
Zendesk tags every ticket closed this way with closed_by_merge. Filter that tag out of reporting and ticket volume, resolution time and CSAT count each customer contact once. Merges can also run in bulk from a view, which makes clearing a backlog of duplicates a short job.
A merge is permanent and has no undo, so decide which ticket survives before you confirm.
