Zendesk merged tickets report: track duplicates without distorting volume
Merged tickets are easy to ignore because they often look like cleanup work. In reality, they tell you something important about demand quality, intake friction, and reporting accuracy.
When customers submit the same issue multiple times, or when agents create duplicate follow-up threads that later get combined, your raw ticket counts stop describing unique problems. That affects ticket volume, queue planning, and how stakeholders interpret support demand. A merged tickets report helps you see how much duplication exists and whether it is growing.
This guide shows how to build a merged tickets report in Zendesk, what it reveals about your operations, and how to keep merge behavior from distorting your dashboard. For the metric background, see merged tickets in the glossary and the main support metrics dashboard.
Why merged tickets are worth tracking
A merged ticket pattern can reveal:
- Customers submitting multiple tickets for the same issue
- Routing confusion that creates duplicate ownership paths
- Poor help center findability or intake design
- Incident spikes where customers contact support through multiple channels
- Volume inflation in dashboards that count raw created tickets
If your team sees a sudden increase in merged tickets, the question is not just “are agents cleaning up duplicates?” It is also “why are we generating more duplicate work in the first place?”
How to build the report in Zendesk
Step 1: Identify merged ticket events
Use the dataset or ticket event stream that records merge activity. The key is to capture tickets that were merged into another ticket rather than solved normally.
Depending on your reporting setup, this may appear as:
- a merge event in ticket updates
- a merged status or flag
- an operational export that marks merged records
Step 2: Measure merge count and merge rate
Build two core metrics:
- Merged ticket count for the raw number of merged records
- Merge rate as merged tickets divided by created tickets in the same period
The count tells you scale. The rate tells you whether duplicate demand is actually getting worse or just moving with overall volume.
Step 3: Segment by source
Break the report down by:
- Channel
- Form
- Group
- Tag or issue category
This is where the report becomes useful. If most merges come from one web form, the intake design may be unclear. If merges spike during outages, the issue is probably demand behavior, not internal process.
Step 4: Trend the metric weekly
Review the trend week over week so you can separate steady-state duplication from event-driven spikes. If the merge rate jumps only during incident weeks, that suggests communication gaps during outages. If it rises steadily over months, your intake process may be creating duplicate work all the time.
How merged tickets affect the rest of your dashboard
Merged tickets can distort several metrics if you do not account for them:
- Ticket volume may look higher than the number of unique customer problems
- Backlog may look worse temporarily if duplicates accumulate before cleanup
- First reply time can look better or worse depending on which ticket becomes the surviving thread
- Resolution time may not reflect the customer journey cleanly when duplicate tickets are closed through merging
This does not mean you should exclude merged tickets from every dashboard. It means you should know when they are significant enough to change the story.
What a healthy report looks like
Healthy does not mean zero merges. Some duplication is normal.
You are usually in a good place when:
- merge rate is stable over time
- duplicate demand spikes only during known incidents
- a small number of forms or channels explain most merge activity
- agents follow a consistent process for merging and preserving the right source ticket
You should investigate when:
- merge rate rises without a clear incident or launch
- one channel produces far more duplicates than others
- merged volume grows alongside reopen rate or backlog
- stakeholders rely on raw created-ticket counts without understanding duplicate inflation
What to do when merge rate is high
- Audit the intake experience. Customers often submit duplicate tickets when confirmation is weak or help center suggestions miss the issue.
- Review auto-acknowledgement timing. Slow confirmations can prompt customers to submit again before they trust the first ticket went through.
- Check incident comms. During outages, customers may contact you through email, chat, and forms for the same problem. Better status messaging can reduce that duplication.
- Standardize merge workflows. Agents should know which ticket survives, which tags to preserve, and how to keep reporting consistent.
- Annotate executive reporting when needed. If duplicate demand materially inflated created-ticket counts, explain that in the weekly review rather than letting the raw number speak for itself.
Common mistakes
- Treating merges as cleanup only. Merge behavior is also a demand-quality signal.
- Reviewing count without rate. High merge count during a high-volume week may be normal.
- Ignoring the surviving ticket logic. How your team merges affects downstream metrics and drill-down workflows.
- Assuming duplicates mean customer error. Weak confirmation emails, unclear forms, and incident noise often create the duplicates.
- Leaving merged tickets out of post-incident analysis. They are often one of the clearest signs that customers were confused or unable to self-serve.
FAQ
Should merged tickets count toward ticket volume? It depends on the question. For raw contact demand, yes. For unique issue volume, probably not. Many teams report both and explain the difference.
What is a normal merge rate? There is no universal benchmark. Use your own baseline by channel and ticket type. Incident-heavy teams naturally see more duplication.
Can merged tickets affect first reply time? Yes. The surviving thread may have a different reply history than the duplicate ticket that was merged, so you should interpret speed metrics carefully during heavy merge periods.
What should I pair this report with? Use Zendesk ticket volume report, Zendesk help center analytics, and the main support metrics dashboard.
See duplicate demand before it inflates your queue metrics - start free