Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallA help-desk ticket status shows where a support request sits in a workflow: newly received, being worked on, waiting for a reply, resolved, or closed. The labels are not universal. A status can also be internal, and a customer reply may move a ticket back into active work. To understand any label, check who is expected to act next, what the customer can see, and what the platform does when someone replies.
What a ticket status tells you
A status is a workflow marker, not a complete account of a ticket. It describes a stage or waiting condition, but does not necessarily identify the agent responsible, show every internal detail to the requester, or mean the same thing in another help desk. Platforms may use different labels, allow administrators to customize states, and automate transitions.
When you see an unfamiliar status, ask three questions: what work is happening, who must act next, and what event changes the status? These questions are more reliable than interpreting a label such as “waiting” on its own.
Common help-desk ticket statuses
| Workflow stage | Common label | What it usually means | Important qualification |
|---|---|---|---|
| Newly received | New | The request has arrived and may not yet have been assigned or acted on. | In Zendesk, a ticket cannot return to New after its status changes. |
| Active work | Open or In progress | An agent or team is expected to work on the request. | Zendesk defines Open as assigned and in progress; other platforms may configure their active state or use a different label. |
| Waiting for the requester | Pending or Waiting on customer | The support team needs information, confirmation, or another response from the customer. | A customer reply can move the ticket back to an active state automatically. |
| Waiting for someone else | On-hold | Progress depends on a third party, another team, or an external event. | Zendesk treats On-hold as optional and internal; the requester sees the ticket as Open in its Help Center. |
| Resolution submitted | Solved | The agent considers the issue answered or resolved. | In Zendesk, a requester can reply before closure and reopen the ticket. |
| Final or inactive stage | Closed | The ticket has reached a later, inactive stage in its lifecycle. | Meaning and controls vary: Zendesk applies Closed through system automation, while Freshdesk describes Closed as completed according to the customer. |
“Waiting” is especially easy to misread. Pending usually means the support team is waiting for the requester; On-hold commonly means the team is waiting on someone else. A platform may use different labels or configure the states differently, so identify the person or group expected to act rather than relying on the word alone.
Recommended Free Tools
Pending versus On-hold
Pending: the requester needs to respond
Support may set a ticket to Pending when it needs a missing detail, a confirmation, or information that only the requester can provide. The ticket is not necessarily abandoned; work is paused until that response arrives. Zendesk documents that a requester’s reply can reset a Pending ticket to Open. Intercom describes a reply moving a Waiting on customer ticket into the ticket type’s default In progress state.
On-hold: the team is waiting on another dependency
An agent may use On-hold when the next step depends on a vendor, a different internal team, or another external party. In Zendesk, On-hold is optional and is an internal status: its documentation says the requester does not see it, and Zendesk Help Center displays the ticket as Open instead. That means the internal state and customer-facing label can differ without the ticket being in two conflicting workflow states.
Solved versus Closed
Some help desks separate “the agent has submitted a resolution” from “the ticket has reached its final system state.” Zendesk makes that distinction: Solved is the agent-submitted solution stage, and Closed is applied later by system automation. Zendesk says agents cannot set Closed manually, and a requester cannot reopen a closed ticket. Its documentation states that tickets are automatically closed 28 days after they are set to Solved, regardless of triggers or automations; this is a Zendesk-specific rule, not a general help-desk standard.
Do not assume every platform uses the same two-stage lifecycle. Freshdesk describes Closed as a completed ticket, illustrating that the label’s meaning and the transition rules depend on the product. If a ticket appears closed, the available next step may therefore be to create a new request rather than reply to the old one.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →How statuses change as a ticket moves through support
A simple Zendesk-based example is New → Open → Pending while the agent waits for customer information → Open after the customer replies → Solved → Closed after the system closure step. It is an illustration of Zendesk’s documented lifecycle, not a universal sequence. A ticket can move backward into active work, and platforms can add or configure states.
- New: A request enters the queue; it may still need assignment or initial review.
- Open: An agent or team is expected to investigate or respond.
- Pending: The agent needs the requester to supply information or take an action.
- Open again: A requester replies, prompting an active-work state under the documented Zendesk behavior.
- Solved: The agent submits a resolution.
- Closed: Zendesk’s system applies the later closure state; the requester cannot reopen a ticket once it is closed.
Other systems may use different names and transitions. Intercom’s ticket states are configurable, and a reply to Waiting on customer moves a ticket to that ticket type’s default In progress state. Freshdesk says a customer response to a Pending ticket moves it back to Open.
How ticket-status behavior differs by platform
| Platform | Documented states and configuration | Reply and visibility behavior | Closure behavior |
|---|---|---|---|
| Zendesk | Standard statuses are New, Open, Pending, On-hold, Solved, and Closed. On-hold is optional; accounts may have custom statuses. | A reply can move Pending back to Open. On-hold is internal; the requester sees Open in Help Center. | Closed is applied by system automation, not manually by agents. Requesters cannot reopen a closed ticket. Zendesk documents automatic closure 28 days after Solved. |
| Intercom | Ticket states are configurable; a ticket type can have a default In progress state. | A reply to Waiting on customer moves the ticket to that ticket type’s default In progress state. | A general closure interval or rule is not stated in the cited Intercom material. |
| Freshdesk | Its documentation describes its own status behavior, including Pending and Closed. | Pending pauses while the agent gathers additional information; a customer response moves the ticket back to Open. | Freshdesk describes Closed as completed according to the customer; a universal timed closure interval is not stated in the cited Freshdesk material. |
The product distinctions matter most when a customer replies, when an agent marks work complete, and when an internal state is hidden from the requester. Zendesk Documentation Team’s article “About the ticket lifecycle and ticket statuses,” edited May 1, 2026, describes Zendesk’s status model; Intercom and Freshdesk document different state behavior. Those definitions should not be generalized to every help desk.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Why a ticket may reopen after a reply
Many workflows treat a requester’s new message as a signal that someone needs to act again. A reply can return a waiting ticket to active work, or reopen a solved ticket before the system has closed it. The names differ: Zendesk describes Pending moving to Open, Intercom describes Waiting on customer moving to the default In progress state, and Freshdesk describes Pending moving to Open after the customer responds.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →If a reply does not appear to reopen a ticket, check whether it has already reached the platform’s closed state. In Zendesk, a requester cannot reopen a closed ticket; use the available new-request path if further help is needed. For a still-active or waiting ticket, the platform’s configured rules and the specific ticket type may determine which active label appears.
How to interpret a status in practice
- Look for the next actor: Is the agent expected to work, the requester expected to answer, or another party expected to provide something?
- Separate the internal state from the customer view: A requester-facing label may not expose the exact internal status, as Zendesk’s On-hold handling demonstrates.
- Check reply behavior: Find out whether a reply reopens the existing ticket, changes it to another active state, or requires a new request after closure.
- Distinguish resolution from closure: A “solved” ticket may still have a later system transition, depending on the platform.
- Account for configuration: Custom statuses, defaults by ticket type, and automation can change the labels or transitions from the default workflow.
Frequently Asked Questions
Does “Open” mean a specific agent has already started working on the ticket?
Not necessarily. Zendesk defines Open as assigned and in progress, but a status by itself is not a universal record of which person is currently handling the next action. Check the ticket’s assignee or team field for ownership.
Can a ticket go straight from New to Solved?
The documented Zendesk example separates active work from the solution stage, but the available documentation does not establish one mandatory sequence for every help desk. Workflows and custom states can vary by platform and configuration.
Frequently Asked Questions
Does “Open” mean a specific agent has already started working on the ticket?
Not necessarily. Zendesk defines Open as assigned and in progress, but a status by itself is not a universal record of which person is currently handling the next action. Check the ticket’s assignee or team field for ownership.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Can a ticket go straight from New to Solved?
The documented Zendesk example separates active work from the solution stage, but the available documentation does not establish one mandatory sequence for every help desk. Workflows and custom states can vary by platform and configuration.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
