Open vs. pending and on-hold tickets and why you should care Follow

One of the major benefits to using an online customer support software to handle your customer interactions is that unlike an email inbox, the interactions in a ticketing system have a defined end-point: you mark a ticket solved.  This closed loop process is important for both your company and your customers; it puts you both on the same page - an agreement that the issue or question has been resolved and ultimately closed.

But of course, there are a few steps between a customer sending a ticket and you marking it solved.  To handle these various stages, all tickets can be in one of five states (or, as you'll see on all tickets, five statuses ): New , Open , Pending , On-hold , or Solved . New and Solved might be self-explanatory -- they mark the beginning of the interaction and the end -- but what about Open, Pending, and On-Hold? By understanding and making use of these statuses, you can stay on top of your support workload and bring any outstanding tickets to solved in an efficient manner.

Ticket Status can be manually set within each ticket via the Status Dropdown, located at the bottom of the ticket.

An Open ticket is defined as a ticket assigned to an agent. Open tickets are the heart of your support workload -- they indicate those issues that you're working on. Once a ticket's status has been changed from New, it can never be set back to New.

Where this begins to be important is when you set up Views , Triggers , and Automations based on a ticket's status.  It is probably useful, for instance, to see a grouping of all your Open tickets; all your tickets that need to be solved.

But, of course, oftentimes to solve a ticket, you need to collect more information from the requesting customer, e.g. you need the specific text of the error that they are seeing, or you need their account number, etc.  So you write them back.  In those cases, you want to be able to move the ticket off the list of things that need your attention but at the same time not forget about it. This is why the Pending status is so useful; it's like saying: "This ticket is not yet solved but I'm waiting on information from the requester before I can work on it further."

The On-hold status is similar to Pending, and used to indicate that you are waiting for information or action from someone other than the requester, for instance one of your supervisors or an internal developer. On-hold is an optional, internal status. It can be enabled by an administrator, and if it isn't enabled, you will not see it in your status options. Ticket requesters do not see this status -- On-hold tickets appear as Open to your customers.

To see how these states might be useful, let's take a look at how you could set up a View that shows you all your unsolved tickets but groups them according to whether they are Open or Pending.  (Views are collections of tickets that you can customize according to your support workflow.)

To set up a new View , go to Manage > Views on your Zendesk Support admin page. Click on "add view" in the upper right. We'll keep this simple and just collect all our tickets that are not solved, or in this case "Less than Solved":

Next, we'll set the Format Options to display by Table , and then choose to Group the tickets by Status:



Now, when we update and return to this view, we'll see our tickets grouped according to whether they are New, Open, Pending, or On-hold.  This way, we can see those tickets where we've written back to the customer or internal expert for more information but they are separate from those that require our active attention.



When our customer or internal expert replies to us with the information we requested -- the error message or account info -- Zendesk Support will automatically change the status from Pending or On-hold to Open.  So the next time we look at our "All Unsolved Tickets" view, then, that ticket will appear in our Open list, and hopefully closer on its way to Solved!

Have more questions? Submit a request

Please sign in to leave a comment.

Powered by Zendesk