Zendesk offers a set of standard ticket statuses to help you manage your ticket workflows. When custom ticket statuses are activated, you can create additional ticket statuses that are more meaningful to your business and end users.
With form ticket statuses, you can define which ticket statuses should appear in certain ticket forms. Associating ticket statuses to forms allows you to only show ticket statuses that are relevant to the ticket an agent is working on. This results in a shorter list of ticket statuses in the status picker for agents to choose from and can help them select the appropriate status more quickly.
Understanding form ticket statuses
Form ticket statuses are the standard and custom statuses you associate with your ticket forms.
Associating ticket statuses to forms allows you to only show ticket statuses that are relevant to the ticket an agent is working on. For example, say you have a ticket form for Customer Returns and an internal ticket form for Agent Onboarding. You can create custom ticket statuses that are relevant to each form, such as Refund issued or Training in process. By associating statuses to relevant forms, agents can quickly find the appropriate status.
About the agent experience with form ticket statuses
Agents can select the appropriate status from the status picker in the Zendesk Agent Workspace. When agents switch the form applied to a ticket, the status picker updates the statuses associated with the form. Agents benefit from form ticket statuses because they can quickly find the status relevant to a ticket and don’t have to scroll through a long list of statuses.
Associating ticket statuses to forms
Your default ticket statuses – initially, New, Open, Pending, On-hold (if activated), and Solved – are automatically associated with every form. If you’ve changed your default ticket status names, then those statuses appear on your forms.
Define which custom ticket statuses should appear on ticket forms so that only relevant statuses are displayed. You can also associate ticket statuses to one or more forms when you create a new ticket status.
To associate ticket statuses to a form
-
In Admin Center, click
Objects and rules in the sidebar, then select Tickets > Ticket statuses.
A list of your active ticket statuses appears on the All Ticket Statuses tab. If you haven’t created any custom ticket statuses yet, see Creating custom ticket statuses.
Tip: To view your default statuses, click the options menu icon () at the top of the table and select Default.
- Click the Ticket statuses by form tab.
A list of your forms displays.
- Click the name of the form you want to associate ticket statuses with.
- Click the arrow next to each status category and select the
statuses you want to associate with the form.Note: Both active and inactive statuses appear. You can select only active statuses. See Activating and deactivating a ticket status.
As you add statuses to the form, the status picker Preview updates.
- Continue to add or remove statuses, then click
Save.
The number of statuses associated with the form update on the Ticket statuses by form tab and in the status picker in the agent interface. Learn more about the agent experience with form ticket statuses.
Managing form ticket statuses
On the Ticket statuses by form tab, you can edit which ticket statuses appear on your forms, view the number of standard and custom ticket statuses associated with each form, view which brands are assigned to the forms, search for forms, and filter forms by active status and brands.
Searching and filtering forms
Search for and filter forms on the Ticket statuses by form tab to help quickly find the form whose statuses you want to manage.
To search and filter your forms
- In Admin Center, click
Objects and rules in the sidebar, then select Tickets > Ticket statuses.
- Click the Ticket statuses by form tab.
- Take one of the following actions:
- To search for a specific form, enter a term in the search box.
- To filter forms by active status or brands,
click Filter.
Select Active or Inactive in the Form status menu, or click the Forms associated with brands menu and select the brands you want to filter by.
See Activating and deactivating ticket forms and Assigning brands to a ticket form to make changes to your forms.
Click Apply filters.
6 comments
Scott Tynan
Cool, Now can we have channel-based ticket statuses, please?
0
Thomas Littler
Amazing. Is there any news on if we can get custom coloured ticket statuses? I.e Create a ticket status under a system status category with optional colour selector.
1
Patrick Beebe
Now to only get Zendesk to do the process properly. Would this not be more simple if: When creating a new Ticket Status, allowing the Admin to choose which Forms (from a drop-down menu) to associate the new status? Instead of creating the New Status then having to go into each Form and Deselect. Working smarter, not harder should be the goal…
6
test.zendesk
It will be nice to have the ticket statuses visible by group, as not all statuses are being used by every team, so it will be nice to make them visible only to certain groups. Is this feature being worked on? Else I want to request this feature. Also, the option to hide default status at least pending and on hold.
4
Nathan Seber
Is there a way to move around the order of the status? I would like to have Solved at the very bottom and the two I created under the Solved Category to be just above it.
I also would like to see the ability to do this by group, we have the same webform from our guide for 3 different groups, but not all 3 groups do the same thing, so the custom statuses are different.
3
Sam
It defeats the purpose of having custom statuses if we are unable to hide the default statuses for a given form. It makes sense for the default statuses to be applied to all forms, but once a ticket form has a custom status applied to it, there has to be a way to explicitly remove the defaults statuses, otherwise it convolutes the list of custom statuses….there are way too many!
Of course, on the offchance the admin switches back to remove custom status, since each custom status has an associated “status category,” this would effectively replace the relevant default status.
1