Understanding the Zendesk Ticket Lifecycle
Every Zendesk ticket moves through a lifecycle: created, assigned, replied, solved, closed. Understanding this lifecycle is essential for accurate reporting and ops decisions.
The basic lifecycle
New → Open → Pending → Solved → Closed
↘ ↗
On-hold
| Status | What it means |
|---|---|
| New | Ticket created; no agent has acted yet |
| Open | Agent is working on it |
| Pending | Waiting for customer response |
| On-hold | Waiting for third party (optional status) |
| Solved | Agent marked resolved; awaiting auto-close |
| Closed | Ticket is closed; can’t be reopened |
For definitions, see open tickets, pending tickets, solved tickets, and closed tickets.
Why lifecycle matters for metrics
Each status change affects your metrics:
- First reply time — Measured from creation to first agent reply (usually when ticket goes from New to Open or Pending).
- Resolution time — Measured from creation to Solved.
- Reopen rate — Tickets that go from Solved back to Open.
- Backlog — Tickets not yet Solved (New + Open + Pending).
Misunderstanding statuses leads to misreported metrics.
Status transitions
New → Open
Happens when an agent takes action (replies, assigns, updates). If agents don’t touch tickets promptly, time to first assignment grows.
Open → Pending
Agent replied; waiting for customer. The ticket is “on the customer” now. Most teams stop counting time toward resolution when a ticket is Pending.
Pending → Open
Customer replied. The ticket is back on the agent. This is where delays can accumulate if agents don’t respond quickly.
Open/Pending → Solved
Agent marks the ticket as resolved. In Zendesk, Solved is a temporary state before auto-close (usually 4 days by default).
Solved → Open (Reopen)
Customer replies to a solved ticket. This is a reopen. High reopen rate signals quality issues. See reopen rate as a quality metric.
Solved → Closed
Automatic. After X days, Zendesk moves Solved tickets to Closed. Closed tickets can’t be reopened—replies create a new ticket.
Common mistakes
1. Conflating Pending with Solved
Pending = waiting for customer. Solved = issue resolved. If agents mark tickets Pending when they should mark them Solved, your resolution metrics will be wrong.
2. Ignoring On-hold
Some teams use On-hold for third-party waits (waiting on vendor, internal escalation). If you use it, make sure it’s consistent—otherwise, reports will be inconsistent.
3. Counting Pending in backlog
Some teams count only New + Open as backlog; others include Pending. Define your backlog clearly. See open tickets for conventions.
4. Not understanding auto-close timing
If Solved → Closed timing is too short, customers can’t reply before the ticket closes. If too long, your “Solved” count includes tickets that might reopen.
How to audit ticket lifecycle
- Check status distribution — What % of tickets are in each status right now? Is Pending unusually high (agents not closing)?
- Check average time in each status — Where do tickets spend the most time?
- Check reopen patterns — Are reopens coming from Solved or from Pending?
For dashboard setup, see support metrics dashboard.
FAQ
What’s the difference between Solved and Closed?
Solved is agent-set; the issue is resolved but the ticket can reopen if the customer replies. Closed is final; replies create a new ticket.
Should I use On-hold?
Optional. If your team waits on third parties often, On-hold provides better visibility. If not, it adds complexity.
Does time in Pending count toward resolution?
It depends on your settings. Zendesk can measure resolution in business hours and exclude Pending time. Configure based on how you want to measure.