# Zoho Desk Ticketing: Statuses, Merges, Work Modes and Limits

> How Zoho Desk ticketing works: channels into tickets, statuses and On Hold, work modes, five-ticket merges, parent-child links and the edition behind each.

_Source: https://professionalstoolkit.com/articles/zoho-desk-ticketing — The Professional's Toolkit · updated November 2026_

---

Zoho Desk turns every email, web form, social post, chat and call into a ticket that sits in one of three states: Open, On Hold or Closed. The core works on every edition, including the Free plan for three agents, but the tools that keep a busy queue manageable are gated. Merging, splitting and cloning start on Express, at $7 per agent per month billed annually or $9 billed monthly. Cost grows with every agent, and all agents must be on the same edition; see the [Zoho Desk pricing breakdown](/articles/zoho-desk-pricing). Work modes, followers and time tracking start on Standard. Collision detection, ticket sharing and parent-child links need Professional. **Pick the edition by the ticket tools your team will touch daily**, not by the channel list.


**5** — Tickets you can merge into one master ticket at a time, from Express; merges cannot be undone.



- **3 states** — Open, On Hold, Closed under every status
- **200** — Child tickets per parent (Professional and higher, early access on request)
- **50** — Tickets per mass action such as close (mass reply from Professional)


## How conversations become tickets

Email is the base channel, and the number of support addresses grows with the edition: one on Free, two on Express, five on Standard, ten on Professional and 100 on Enterprise. Advanced web forms follow a similar ladder, from one on Free and Express to 50 on Enterprise. Social channels (Facebook, Instagram, X) arrive on Express for one brand. Instant messaging, including WhatsApp and Zoho's own Business Messaging live chat, starts on Standard. Telephony starts on Professional, where missed calls and voicemails land in the queue as tickets.

Email threading decides whether a reply joins an old ticket or opens a new one. By default Zoho Desk threads by the email's message ID. Threading by ticket ID is stricter: it reads an ID in the subject line, is switched off by default, and needs Standard or higher. You can limit it to active agents, or to the ticket's contact and the people who took part in the ticket, which blocks spam from attaching itself to live tickets. Chat follows its own rule. A reply that arrives more than 60 minutes after an instant-messaging chat creates a new ticket, and admins can stretch that window to 24 hours or choose to always reopen the same ticket. Anonymous Business Messaging visitors never become tickets. Only saved contacts do.

| Ticketing feature | Lowest edition |
|---|---|
| Email ticketing, default statuses, tags | Free |
| Merge, split, clone, table view | Express |
| Work modes, followers, snippets, time tracking | Standard |
| Threading by ticket ID, happiness ratings | Standard |
| Collision detection, ticket sharing, approvals | Professional |
| Parent-child tickets (early access, on request), mass reply, ticket templates | Professional |
| Layout and validation rules, custom modules | Enterprise |



> ⚠ **Bulk closes skip notifications:** Notification rules do not fire on tickets closed with bulk actions, so customers may not get a closing email.

## Statuses, states and the SLA clock

Every ticket starts with four statuses: Open, On hold, Escalated and Closed [1]. You can add your own per department, but each custom status must be typed as Open, On Hold or Closed. That type applies across the whole organization, and it drives custom views, automation rules and reports. A status called Waiting on Vendor therefore behaves exactly like On Hold everywhere. Choose the type carefully. Views, rules and reports will group tickets by it.

**On Hold freezes the SLA timer**, and escalations stop firing while a ticket waits there. When it returns to Open, the new due time is worked out from the old due time plus the time spent on hold. Overdue tickets moved to On Hold stop counting as overdue. That can flatter an SLA report. Agents who park tickets to dodge breaches will look better than they are. By default a customer reply sends any ticket back to the default Open status. You can make a status sticky by unchecking its fall-back option, and an On Hold status can never be the default.


> 💡 **Type custom statuses with care:** Each custom status must be typed Open, On Hold or Closed, and that type applies across the organization. Decide before you build views and rules on it.


## Views and work modes for the daily queue

Custom ticket views filter the queue by any field and can be visible to one agent, all agents or a chosen group. Agents can save their own filters on top of a shared view. A custom view nobody opens for 60 days is archived automatically, restorable for 30 days, then deleted, so seasonal views need an occasional visit. Table view, which shows up to 15 columns, is on every paid edition. Free does not get it.

Work modes are the bigger change to how agents pick their next ticket. They need Standard. There are four of them: Status, Handshake, Countdown and Priority, each a different board layout of the same queue. Handshake surfaces tickets raised by CRM leads that carry a deal value, so it depends on the Zoho CRM integration, which is available on Standard and higher only. Countdown can hold up to seven columns, including a dedicated On Hold column, which keeps parked tickets visible instead of buried. Teams that sell and support from one Zoho stack get the most from Handshake.

## Merging, splitting, cloning and linking

Duplicates are the most common mess in a shared inbox, and the merge rules are strict [2]. You can merge up to five tickets at a time, only from the same department, and the agent needs the Find and Merge permission. The oldest ticket becomes the master by default, and its created time, response time and on-hold time win. Replies, comments and attachments from the others move into the master in date order. The merged tickets go to the Recycle Bin. **A merge cannot be undone.**


> ⚠ **Merges are permanent:** Zoho Desk cannot unmerge tickets; the oldest ticket becomes the master by default, and the others go to the Recycle Bin.


Splitting works the other way, but narrowly. It applies only to an incoming response and moves that single reply into a new ticket, leaving later threads behind. Resolution time on the split ticket counts from the reply that caused it, not from the moment of the split. Cloning, on paid editions only, copies ticket properties and the description but no attachments, threads or comments. The subject gets a Clone tag. Use cloning for a repeat request, not for an ongoing conversation.

Parent-child ticketing suits one incident reported by many customers. It needs Professional or Enterprise, is opened on request through an early-access form, and is set up by an admin [3]. A parent can hold up to 200 children, a child has only one parent, and children cannot have children. You choose how closing works. Children can close automatically with the parent, or the parent can stay open until every child is closed; the two options cannot run together. From the parent you can act on up to 50 children at once.

## Working a ticket as a team

### Collaboration on one ticket

Comments are private by default, and a public comment emails the customer. On Professional, collision detection shows who is viewing or drafting a reply, warns when someone is already replying, and opens a quick chat among the agents on that ticket. Ticket sharing, also Professional, lets another department see a ticket at full, restricted or read-only access. The receiving department can never change the status or the owner, whatever its level. Sharing keeps one ticket in sync across both teams.

Standard adds the tools agents use every hour. Followers track a ticket in the Notification Center. Snippets insert saved text with placeholders, up to 200 snippets of 25,600 characters each, with no images. Time tracking runs timers on several tickets at once, can log time automatically for replies and field updates, and can pause after 30 seconds of idle time. Four billing preferences turn that time into support costs. Agencies that bill clients by the hour need this.


> 💡 **Restrict ticket-ID threading:** On Standard and higher, limit ticket-ID threading to active agents, or to the ticket's contact and the people who took part in it, so spam cannot attach itself to live tickets.


### Bulk actions, tags and field limits

Mass actions cover up to 50 selected tickets; bulk actions handle more, up to 200,000 records per run, with one running and ten queued. Reply, comment, close, mark as spam and macro are mass-only, so they stop at 50 tickets per click; merge is mass-only too and stops at five. Notification rules do not fire on tickets closed in bulk. Customers may miss the closing email. Mass reply and scheduled replies arrive on Professional. A scheduled reply can wait up to 60 days, only on email tickets, and turns back into a draft if the customer writes in first.

Tags are department-specific, three to 50 characters, letters and numbers only. Each ticket carries 10 on Free and Express, 20 on Standard, 30 on Professional and 50 on Enterprise. Deleting a tag breaks the views, reports and rules built on it. Custom fields cap what you capture: none on Free, 10 per module on Express, 50 on Standard, 150 on Professional and 230 on Enterprise [4]. Happiness ratings, with Good, Okay and Bad buttons on each reply or at closing, are listed for Standard and higher.

## Which edition the ticketing work needs

Start from the hard caps. Free stops at three agents and Express at five. Every agent must sit on the same edition. For five agents billed annually, by our arithmetic, Express runs $35 a month, Standard $70 and Professional $115. Paid monthly, Standard runs $100 a month and Professional $175 for that same team. The step from Express to Standard for five agents is $35 a month billed annually ($55 billed monthly), and it buys work modes, time tracking, ticket-ID threading and room for a sixth agent. Six agents on Standard come to $84 a month billed annually.

Professional earns its extra $45 a month billed annually ($75 billed monthly) over Standard for five agents only if collisions, cross-department sharing or incident-style parent tickets are daily problems. A team of three answering email can live on Free. Per-agent pricing grows with headcount, and deactivated agents stay billed until you cut seats, so check the [Zoho Desk pricing breakdown](/articles/zoho-desk-pricing) before you scale. For rules that assign, escalate and close tickets on their own, see [Zoho Desk automation](/articles/zoho-desk-automation).


## FAQ

**How long can I recover a deleted Zoho Desk ticket?**

Deleted tickets stay in the recycle bin for 60 days and are then deleted permanently. Tickets marked as spam are removed automatically every 30 days.

**Can I change the ticket ID format in Zoho Desk?**

Ticket ID customization is a Professional and Enterprise feature. The default starting number is 101, a custom starting number can have up to 9 digits, and a prefix plus suffix may total 16 characters, set per organization or per department.

**How many people can be copied on a Zoho Desk ticket?**

Up to 20 CC email addresses per ticket. CC users become secondary contacts who can track the ticket in the help center and can leave happiness ratings where ratings are enabled.

**What happens when a ticket moves to another department?**

It becomes a new ticket in that department with the status Open, and it loses the automations and SLAs of the department it left. Sharing the ticket instead keeps it in place.


## The bottom line

Zoho Desk's ticketing is deep and rule-bound: three states under every status, a strict five-ticket merge that cannot be undone, and parent-child links capped at 200 children. The edition decides the experience more than the channel list does. Express covers duplicates, Standard adds the daily queue tools, and Professional adds the team-safety features that busy queues eventually need. Map your weekly ticket habits to those gates before you buy. Buy for the queue you run.



## Sources

[1] Zoho Desk help: Customizing Ticket Statuses — https://help.zoho.com/portal/en/kb/desk/ticket-management/ticket-status/articles/customizing-ticket-statuses (2026-11)
[2] Zoho Desk help: Merging Tickets — https://help.zoho.com/portal/en/kb/desk/ticket-management/actions-in-tickets/articles/merging-tickets (2026-11)
[3] Zoho Desk help: Understanding Parent-Child Ticketing System — https://help.zoho.com/portal/en/kb/desk/ticket-management/linking-tickets/articles/understanding-parent-child-ticketing-system (2026-11)
[4] Zoho Desk pricing plan comparison - Choose your perfect fit Plan Comparison Compare and — https://www.zoho.com/desk/pricing-comparison.html (2026-11)
[5] Zoho Desk pricing page — https://www.zoho.com/desk/pricing.html
[6] Zoho Desk help center — https://help.zoho.com/portal/en/kb/desk
[7] Zoho Terms of Service — https://www.zoho.com/terms.html