Macha
Helpdesk Concepts

Ticket Status

Definition

Ticket status is the field on a support ticket that shows where it is in the resolution process — common values are new, open, pending, on-hold, solved, and closed.

Also known as: ticket statecase status

How it works

When a ticket arrives it's typically new; once an agent picks it up it becomes open. If the agent is waiting on the customer it moves to pending, and if it's waiting on an internal party it may go on-hold. When the issue is resolved it's marked solved and, after a set period with no reactivation, closed.

Different help desks name these states slightly differently, but the shape is the same: a small, ordered set of values that everyone on the team reads the same way, so reporting and automation can act on them.

Why it matters

Status is the backbone of nearly every workflow and metric a help desk runs. SLA timers, routing rules, and dashboards all key off it — which is why an accurate, disciplined use of status directly shapes how reliable your reporting and automation are.

It's also what lets a queue stay manageable: filtering to just open and pending tickets tells an agent exactly what needs attention right now.

  • Drives SLA timers (an open ticket is on the clock; pending often pauses it)
  • Feeds backlog, aging, and resolution-time reporting
  • Triggers automations when a ticket changes state

Frequently asked

What is the difference between solved and closed?

Solved means the agent believes the issue is resolved but the ticket can still be reopened by the customer; closed is a final, archived state that usually can't be reopened — a new ticket would be created instead.

Does pending status pause SLA timers?

In most help desks, yes. Pending (waiting on the customer) typically pauses response and resolution SLA clocks, since the delay is outside the agent's control.

Put these ideas to work

Macha is an AI agent layer that sits on top of the help desk you already run — Zendesk, Freshdesk, Front, Intercom, or Gorgias.

Start Trial