Zendesk Child Tickets, and When to Use Them
Zendesk child tickets are the right tool when one cause produced many separate requests, each of which still needs its own answer.
Zendesk child tickets, in plain terms
Zendesk models this with ticket types. A Problem ticket represents the underlying fault. An Incident ticket is one customer reporting it, and it's linked to the problem.
Solve the problem ticket and Zendesk offers to solve every linked incident with one comment. Ten customers, one investigation, ten replies sent at once, ten resolution times recorded properly.
When to use this instead of merging
Use incidents when each reporter needs their own reply. Use a merge when the same person sent the same request more than once and only one reply is ever going out.
The failure mode to avoid is merging ten reporters into one ticket. Nine customers then get nothing, and your reporting shows one ticket where there were ten.
Frequently asked questions
Are these the same as problem and incident tickets?
Yes. Zendesk parent child tickets are modelled through the Zendesk problem incident tickets types: one problem ticket, many incidents linked to it, all closed by one reply.
What are Zendesk child tickets?
Incident tickets linked to a single problem ticket. Solving the problem closes every incident attached to it with the same public reply, which is what an outage needs and what a merge would ruin.
Does merging in Zendesk lose the customer replies?
No. Ticket Merger uses the native Zendesk merge, so the conversation, attachments and audit history move onto the surviving ticket. The duplicate is closed with a note pointing at the original.
Can I review merges before they happen?
No. Once a pair matches your rules, Ticket Merger merges it. What you control is what qualifies: requester, the subject keywords you list, the time window, and the groups, forms or tags you exclude. To see how it behaves before it touches everything, point it at one group first and widen from there. Every merge leaves a note on the thread saying what was merged and why.
What stops it merging two tickets that are not the same?
Rules you set. Match on requester, subject keywords, status, priority, category or group, and a time window, and exclude anything you want left alone, like tickets from a specific form, group or tag. Anything that does not clear those rules is left alone.
How long does setup take?
About five minutes to connect, and the first scan of your open queue runs immediately after. Onboarding help is included on every plan.
Keep incidents, kill duplicates
Ticket Merger merges the same request arriving more than once and leaves genuine incident groups alone.
Start free trial14-day free trial. No credit card required.