Skip to content

Ticket Statuses Explained: New, Open, Pending, Solved, Closed

Reviewed on November 17, 2026

A status says where a ticket stands and whose move it is. Good statuses answer one question at a glance: is the team waiting, or is the customer?

There's no single standard list. Products use different names and different counts. The five in the title are common, so they're a fair way to learn the idea.

A common ticket pathNewOpenPendingSolvedClosed
Names vary by product, but the order is usually like this.

The five, in plain words

New. The ticket was just created and nobody has touched it. One product's documentation says this is "the default status for all new tickets"1.

Open. Someone on your team is working on it. One maker defines open as "the support team is working to resolve the request"2.

Pending. The team has asked the customer something and is waiting. The same maker describes the customer-facing version as "the support team is waiting for a reply from an end-user"2.

Solved. The team has answered the problem. Ask each product whether a customer reply reopens it.

Closed. The ticket is finished. One product says it's "locked, preventing further messages unless an agent reopens it"1.

Names differ, so read the definitions

Don't assume two products use a word the same way. One product's default list includes Open, Pending, Closed, Resolved, "Waiting on Customer" and "Waiting on third-party"3. Another uses New, In progress, On hold, Information requested, Solution offered and Closed1.

Compare the meaning of "on hold" too. One definition reads: "The ticket is awaiting an external event, and no work is being done"1. That's a different case from waiting on the customer. For example, you might be waiting on a supplier or a repair.

Why Pending and On hold matter

Many teams count open tickets as their workload. If tickets waiting on the customer stay in the "open" pile, the pile looks bigger than the real work. A separate waiting status keeps the count honest.

It also helps the customer. A person who sees that you asked a question knows the next move is theirs.

Solved first, then closed

Closing straight away has a cost. One maker's guidance says "Immediately closing a ticket can hinder communication and force requesters to create new tickets if they need further assistance"1. A step between the answer and the lock gives the customer room to reply.

Ask any vendor whether the move from solved to closed is automatic, and whether you can change the wait. Ask whether a customer reply reopens a solved ticket, and what happens after it's closed.

What customers see

The status your staff see isn't always the one the customer sees. In one product, three agent-side statuses show as plain "Open" in the customer view, and solved and closed both show as "Solved"2. Check this in any tool you're considering.

Can you add your own?

Some tools let an admin add custom statuses. One says "Admins can create custom ticket statuses using Ticket Fields and set visibility rules based on them"3. For a small team, extra statuses are rarely the first need. Start with few. Add one only when you can name the question it answers.

Sources used

  1. Ticket Status Definitions and Categories, Mojo Helpdesk
  2. What are the customer portal ticket statuses?, Zendesk
  3. Understand the Ticket Details View, Freshworks (Freshdesk Support)