A ticket in Zoho Desk rarely stays a single, tidy conversation for its whole lifecycle. A customer replies with a second, unrelated question halfway through a thread, two people raise what turns out to be the same issue, or a reply needs to go to a team that has no visibility of the ticket at all. Zoho Desk gives you three distinct ways to reshape a ticket's threads to match what is actually happening: splitting, merging and forwarding.
The Three Ways a Thread Can Move
- Splitting takes one thread out of an existing ticket and turns it into a brand new ticket of its own, so a second issue buried in a long conversation gets tracked and resolved independently.
- Merging does the opposite: it brings two or more tickets that turn out to be about the same issue together into one, so an agent is not duplicating work across separate records.
- Forwarding sends a copy of a thread to someone, inside or outside your helpdesk, without changing which ticket it belongs to, useful when you need input from another team but the ticket itself should stay where it is.
Choosing the Right Action
| Action | What it does | Best used when |
|---|
| Split | Moves one thread into a new, separate ticket | A reply raises a second, unrelated issue |
| Merge | Combines two or more tickets into one | The same issue has been logged more than once |
| Forward | Sends a copy of a thread elsewhere | Another team needs context but should not own the ticket |
Where Splitting Fits In
Of the three, splitting is the one agents reach for least often, largely because it is easy to miss that a second issue has crept into a conversation until you are partway through replying to it. Zoho Desk currently lets you split a single incoming thread at a time into a new ticket, and the same action is available via the Deluge task zoho.desk.ticket.split if you want to trigger it automatically as part of a workflow. For the full step-by-step, see our companion guide on how to split a ticket in Zoho Desk.
A Quick Decision Checklist
- Is a reply raising something genuinely unrelated to the original issue? Split it.
- Have two customers, or one customer twice, raised what is really the same problem? Merge them.
- Does another team need to see the conversation without inheriting ownership of it? Forward it.
- Not sure yet? It is simpler to leave a ticket as it is until the picture is clearer than to reorganise it twice.
Worth knowing: None of these three actions delete anything. Splitting and merging both preserve the original conversation history, they simply reorganise which ticket record it lives under.
Need help? 1 Cloud Consultants can help you design ticket handling and escalation processes in Zoho Desk that fit the way your support team actually works.
Book a discovery call with 1 Cloud Consultants.