This article explains the policy for splitting support tickets in Zoho Desk. It is intended for support consultants and team leads who manage inbound client queries. Following these guidelines ensures accurate ticket tracking and efficient client service.

When should a ticket be split?

A ticket should only be split when doing so adds clear value to the support process. Split a ticket — creating a new, separate ticket — in the following circumstances:

• New, unrelated query: The client submits a query that is entirely unrelated to the original issue and requires its own tracking path.

• Response after closure (unresolved): The client responds after the original ticket was closed but not resolved. If the new response relates to the initial issue, open a new ticket to continue assistance.

• Query on a fully closed ticket: The client raises a new query on a ticket that is already fully closed.

• Escalation to Development required: The query relates to a different, previously handled issue that specifically requires escalation to the Development team.

When should a ticket NOT be split?

Continue assisting within the existing ticket — do not split — in the following circumstances:

• Same general topic: The queries fall under the same general topic or umbrella issue, even if phrased differently.

• Same-day response: The client responds on the same calendar day as the previous interaction.

• Simple, unrelated query: The query is unrelated but simple enough to resolve quickly within the existing thread. Unnecessary splitting inflates ticket volumes without benefit.

Key principles

The guiding principle is to assist the client as efficiently as possible while maintaining clear, logical ticket tracking. Splitting a ticket should be a deliberate action that adds value to the support process — not a default response. When in doubt, keep the conversation in the same thread.

Frequently asked questions

When a client replies after a ticket is closed, do I always need to open a new ticket?

Not always. If the ticket was closed but not fully resolved and the client's reply relates to the original issue, open a new ticket to continue. If the ticket was both closed and resolved, a new ticket is appropriate regardless of whether the query is related.

Can I split a ticket if the new query is unrelated but very quick to resolve?

No. If an unrelated query is simple and can be resolved quickly, keep it in the same thread. Splitting in these cases creates unnecessary ticket volume without improving tracking or service quality.

What does "closed but not resolved" mean?

A ticket is closed but not resolved when it was administratively closed — for example, due to no response — before the client's issue was actually fixed. In this state, if the client responds again on the same issue, a new ticket should be created to ensure the matter is tracked and addressed properly.

Does a same-day response always mean I should keep the ticket together?

Yes, as a rule. If the client responds on the same calendar day as the previous interaction, continue in the existing ticket regardless of whether the query has shifted slightly in focus.

When must I split a ticket for a Development escalation?

Only when the query relates to a different, previously handled issue that specifically requires escalation to Development. If the Development escalation is part of the same ongoing issue, keep it in the same ticket.