Plan requirement
| Subscription | Any plan |
| Access | Admin |
Custom statuses let you use your own words while Zendesk keeps reporting on the six underneath. Both things at once.
How they work
Every custom status sits under one of the standard categories, though not all of them are open to you: Open, Pending, On-hold and Solved are, and New and Closed are not. Agents pick your wording; rules and reports read the category.
So "Waiting for supplier" and "Scheduled for next release" can both sit under On-hold. Your team sees a meaningful difference; your reporting still just sees on-hold time.
What they solve
Teams outgrow six statuses. The usual symptom is a tag doing the job badly: agents adding "waiting-parts" by hand, forgetting half the time, and nobody able to see the state at a glance.
A custom status puts that information where people already look, and cannot be forgotten because it replaces the status rather than adding to it.
What they do not change
- The categories are fixed. You cannot invent a seventh.
- Behaviour follows the category. Anything under Pending still returns to Open when the customer replies.
- Reporting is by category by default. Reporting on your own statuses individually is possible but needs building.
Restraint pays
Three or four extra statuses tell a story. Twelve turn the status field into a taxonomy nobody agrees on, and you are back to guessing. If two statuses would be chosen inconsistently by two agents looking at the same ticket, you have one too many.
The system is more generous than that and it is not a recommendation: an account holds up to 100 ticket statuses, of which only the first 10 appear in the picker without the agent going looking. So the eleventh status you add is one your team will not see, which is a more concrete argument for restraint than any principle.
Comments
0 comments
Article is closed for comments.