Ticket Status

5 min read

Also known as: Ticket state, Case status, Request status

Ticket status is the workflow state of a support request — open, pending, resolved, closed — that tells your team what action is needed next.

Definition

Ticket status is the label that describes where a support request sits in your resolution workflow. Common values include New, Open, Pending, On Hold, Solved, and Closed, and each one signals who owns the next action — your agent, the customer, or a third party.

Support teams use status to route work, trigger SLA timers, and build queue views. An agent picks up tickets marked New, moves them to Open while working, switches to Pending when waiting on the customer, and lands on Solved once the issue is resolved and the customer has confirmed.

Status is different from priority and type. Priority tells you how urgent a ticket is, type tells you what kind of issue it is, and status tells you what stage of the workflow it's currently in — three independent dimensions every helpdesk needs.

Why It Matters

Clean status hygiene is the difference between a 4-hour first response and a 4-day one. Status drives every automated SLA clock, escalation rule, and CSAT survey trigger in your helpdesk, so when statuses are accurate your reporting and routing actually reflect reality.

When teams treat status casually, tickets get stuck in Open while waiting on the customer, SLA timers run on requests that should be paused, and managers can't tell which queue is actually behind. The result is missed response targets, agents working the wrong tickets first, and customers chasing updates that should have been automated.

Examples in Practice

A SaaS support team uses five statuses: New, Open, Pending Customer, Pending Engineering, and Solved. When an agent asks for a screenshot, they switch to Pending Customer, which pauses the SLA clock and triggers a 48-hour auto-reminder if the customer goes silent.

A 30-person agency running client support sets any ticket to On Hold when work is blocked by a third-party vendor. The On Hold status excludes those tickets from the agent's daily queue view so they focus on actionable work, while a weekly report surfaces On Hold tickets that have aged past seven days.

An ecommerce brand auto-closes any ticket left in Solved for more than four days without customer reply. The Closed status locks the ticket from edits, fires the CSAT survey, and removes it from the active queue — keeping the agent dashboard focused on tickets that still need attention.

Frequently Asked Questions

What is ticket status and why does it matter?

Ticket status is the workflow state of a support request, like Open, Pending, or Solved. It matters because it controls SLA timers, queue routing, automation triggers, and reporting. Without accurate status, your team can't tell which tickets need work, managers can't measure performance, and customers fall through the cracks.

How is ticket status different from ticket priority?

Status describes where a ticket is in the workflow — is anyone working on it, waiting on the customer, or done. Priority describes how urgent the ticket is — low, normal, high, or urgent. A single ticket has both: it might be High priority and Pending Customer status. They're independent attributes that answer different questions.

When should I use Pending versus On Hold?

Use Pending when you're waiting on the customer to respond — for a screenshot, confirmation, or more detail. Use On Hold when the ticket is blocked by something outside both you and the customer, like a vendor fix, engineering deploy, or scheduled maintenance. The distinction matters because Pending typically pauses SLA while On Hold often has a separate reporting bucket.

What metrics measure ticket status performance?

Track time in each status (average time in Open, Pending, etc.), aging reports for stuck statuses, status transition rates, and reopen rate from Solved to Open. Also monitor the ratio of New to Open tickets to spot triage backlogs, and flag tickets that sit in Pending Customer longer than your follow-up window.

What's the typical cost of implementing a ticket status workflow?

Status workflows ship with every helpdesk platform, so the software cost is bundled. The real investment is in configuration and training — typically a few hours of admin setup for the workflow itself, plus an hour of agent training. Mid-market teams often spend a week of part-time work refining statuses and automations after launch.

What tools handle ticket status?

Any helpdesk or customer support platform manages ticket status as a core feature, including dedicated ticketing systems, CRM-integrated support modules, and IT service management tools. Look for platforms that allow custom statuses, automated transitions based on rules, SLA pausing on specific statuses, and reporting on time-in-status by agent and queue.

How do I implement ticket status for a small team?

Start with five statuses: New, Open, Pending Customer, On Hold, and Solved. Document when each one applies in a one-page guide. Set automations to auto-close Solved tickets after four to seven days, and auto-remind customers when Pending Customer tickets age past 48 hours. Review status accuracy weekly for the first month, then monthly.

What's the biggest mistake teams make with ticket status?

Creating too many statuses. Teams add a custom status for every edge case — Pending Billing, Pending Manager, Pending Legal — until agents can't remember which to use and reporting fragments across a dozen buckets. Keep your status list under seven, and use tags or custom fields for sub-categorization instead of new statuses.

Should ticket status pause the SLA timer?

Yes for Pending Customer and On Hold — you shouldn't be penalized for response time while waiting on someone else. No for Open and New — those are squarely your team's responsibility. Configure your SLA policy explicitly per status so the timer reflects what's actually in your control.

Can AI agents update ticket status automatically?

Yes. AI agents in a modern support stack can read incoming customer replies, detect intent, and update status accordingly — moving a ticket from Pending Customer back to Open when the customer responds, or from Solved to Open if they say the issue isn't fixed. This eliminates the manual status hygiene burden that drags down most support teams.

The AMW Suite