Duplicate Ticket Merge
Duplicate tickets in Zoho Desk: what Zoho does, and your options
A customer emails, then fills in the web form, then replies to last month's thread. Three tickets, one problem. This page explains what Zoho Desk does about it out of the box, where the limits are, and the ways teams handle the rest.
Disclosure: we build Duplicate Ticket Merge, one of the options below. Everything about Zoho's own features links to Zoho's documentation or community.
Why duplicates happen
- The same customer writes again before anyone answers ("any update?").
- A reply loses the ticket number in the subject, so it opens a new ticket.
- The same issue arrives through two channels: email and web form, or email and chat.
- An outage: dozens of customers report the same thing within an hour.
1. Merge by hand (every edition)
Select the tickets in the list view and choose Merge. Zoho Desk keeps one master ticket and moves the others into it. The limits matter for clean-ups:
- At most five tickets per merge (Zoho use case, help article).
- Only tickets in the same department.
- A merge can't be undone. Status, due date, response times and created time come from the master ticket.
- Finding the duplicates is up to the agent. Zoho has been asked for bulk merge and duplicate detection for years (bulk merge request, duplicate detection thread).
2. Let threading catch replies
Replies that keep the ticket number in the subject are added to the existing ticket. Keep the ticket number in your auto-acknowledgement subject so customers reply into the same ticket. Threading is not perfect: some teams report unrelated emails being attached because their subjects looked alike (community thread).
3. Email Deduplication
Zoho Desk can stop one email sent to two of your support addresses from opening two tickets (community thread). It does not find duplicates that already exist, and it does not cover a customer writing twice, a web form plus an email, or an outage flood.
4. Automate with a custom function (Enterprise)
Zoho's usual answer to "merge duplicates automatically" is a workflow rule that runs a Deluge custom function on each new ticket. Zoho says custom functions are available only in the Enterprise edition (Zoho, May 2025). Things to plan for:
- Someone has to write and maintain the script.
- It acts on new tickets only; it doesn't clean up the duplicates you already have.
- It merges without anyone looking first, and merges are permanent. A loose rule can merge two different customers' problems.
5. Use an extension
Duplicate Ticket Merge adds a panel to every ticket that lists likely duplicates (same contact, similar subject, same department), and a department scan for clean-ups. You review a preview, it merges in batches of five, and it writes a private audit note on the master ticket. It works on Standard and Professional without custom functions, and it calls the Zoho Desk API from your browser, so ticket data stays in Zoho.
Side by side
| Manual merge | Custom function | Duplicate Ticket Merge | |
|---|---|---|---|
| Editions | All | Enterprise | Standard, Professional, Enterprise |
| Finds duplicates for you | No | New tickets only | New and existing |
| Preview before merging | You pick each ticket | No | Yes |
| More than 5 tickets | Repeat by hand | Script handles it | Batches of 5 automatically |
| Audit trail | Ticket history | If you script it | Private note on the master |
| Cost | Included | Enterprise plan + script time | $19 per organization per month, 15-day trial |
A simple routine that works
- Keep the ticket number in every auto-reply subject.
- Once a week, scan each department for the last 7 days and merge what the preview confirms.
- During an outage, scan by same subject and merge each wave into one master ticket, then reply once.
Questions or corrections: support@atesensoftware.com.