Add categories (subviews, dropdown view) function to Views
已于 2021年2月09日 发布
PLEASE VOTE IF YOU NEED CATEGORIES (SUBVIEWS, DROPDOWN VIEW IN VIEWS
Currently, the first 12 shared views are accessible in the Views list. Which might not be enough if you need more subviews/categories.
I will provide examples of the categorized Views and then explain the benefits of it.
Examples of the categorized Views
In our case, we have multiple brands added to Zendesk.
Each brand has different categorized Views, based on:
- Channels
- Language
- Topic (usually filtered by tags which work on particular keywords)
- Help Center submit forms
These first-level categories can be also categorised in their subcategories. For instance, Topic can be categorized in:
- Access issues
- Subscriptions
- Refunds
This is how our Views look in one of the apps from the marketplace (14 brands are connected here):
Depending on the product, the brand View might have multiple subfolders within it.
This is how our View of the categorized brand looks like:
So, here one brand View has multiple categories with 4 depth category levels.
Why is it beneficial to categorize?
- It helps to onboard agents faster when you allow them to start familiarizing with the product by topic;
- Some products have agents who work only with one topic, thus helping to improve efficiency.
- It helps to analyze tickets from the help centre easier when we can dedicate agents to work only with the tickets from the help centre.
- It helps to categorize tickets by issues, which require special attention from more experienced agents.
- Categorization by language also allows choosing the agents with skills needed for the language or the specification of the market.
- Agents can migrate to provide help to other products based on category.
Since Zendesk has a categorization option for macros with :: which allows creating multiple category depth levels, the same functionality could be implemented for subviews option.
Additional to it, the same function of ordering (as trigger categories) could be used in Views too. 
p.s.
We, of course, could use the third-party app but currently, it lags, has quite many glitches and not everything gets along with Zendesk (has not enough consistency).
Let's see how many of us need it, give a vote if you feel a lack of it.
Thank you!
195
106 条评论
Nathan Purcell
Salvador Vazquez can we have an update please?
1
Jeong Hyeon Woo
Hi! Zendesk team.
Is there any progress on this work?
I think it is a very, very necessary function, and I hope it will be applied soon.
I look forward to your feedback on the progress.
2
Usman Saeed
Yes, we need this!
When we can expect this feature in production?
1
Ashley M
+1 This should be a basic function within the tool.
2
Jan Urban
To be honest. We sticked with the aging Kayako... It has a wonderful tree structure. It works for us. You need to do some workarounds and stuff, but its ok. The downside: Its far away from beeing a modern ticketsystem. It lacks in terms of: reports, macros, flexibility and other channels like Facebook, Whatsapp etc.
An other option is "intercom" we looked into this, but it lacks some features we need. So maybe in 2023 we switch to "intercom".
Bye
Jan
2
Support team
hi Jan Urban! What ticketing system you are using now for support?
0
Jan Urban
Hi all,
we were a new customer, but we left because of this issue. 3rd party apps cannot replace what should be included within the core system. We could not properly handle 6 different customer support languages and several departments with Zendesk. Sad to see this being ignored and not implemented.
Bye
Jan
4
Jordan Moore
THIS ENHANCEMENT HAS BEEN OPEN FOR 603 DAYS
New customer here...limiting us to only 12 visible views is a MAJOR challenge from an administration standpoint. We have team members who are team leads / managers / directors / admins, that need to have oversight with multiple views in order to view assignee group work queue volumes.
Realistically, for each assignee group, team members need to see a view for unassigned, open, and closed. We have 9 assignee groups, so that is 27 view combinations. Worst yet, you all do not have an option to view them all in any capacity. This is a ticketing system 101 feature. You are already using navigation collapse and expand objects in the left-hand nav screen in the Admin section of Zendesk...so it exists. Just make the object available to the views section.
This enhancement already has 111 likes...how many more does it need before it will be prioritized???
Our organization is not buying another 3rd party app to replace functionality that SHOULD be in here already natively. Can we place get this prioritized. This creates a huge challenge for us to manage our span of assignee groups and severely limits the scale we can grow in Zendesk. We're halting adding other departments and another 20+ licences just because Zendesk is creating a limiting box for us to grow our enterprise in.
6
Ben Wilcox
Totally agree with Kal Bentley's remark. I would add, in addition, that the 'reliance' on third party apps to do what Zendesk should do natively has a performance impact I don't see discussed much, so I'll throw it in here. I've noticed many times that my 3rd party apps slow my instance down in screen loading time. I'd prefer to not rely on additional data transfers with external entities just to do what Zendesk should do by itself.
2
Kai B
Adding my voice to the request for this. Being able to categorise and see all the relevant views for our workflows would be absolutely invaluable for us. At the moment we are having to look for complex workarounds and custom fields to group within a view so that tickets can be worked, which decreases efficiency in both the operations and development teams. Paying for an app is not an option on top of the subscription we already have with Zendesk, and paid for apps can't be the solution for everything because it reduces the benefit of having Zendesk as a solution across our workspace.
3
登录再写评论。