Discuss ideas, submit feedback, and track what's next
Hi team! I love the new ‘Categorizing your views’ feature as doco'd here: https://support.zendesk.com/hc/en-us/articles/8009260752794-Categorizing-your-views . Thank you for bringing that into the world!! One thing that I'm still not able to get used to, is the icon showing whether the view is collapsed or not. I ALWAYS (despite now using this feature for a number of weeks) get confused by the direction of the arrow, and whether the group is actually expanded or collapsed. I don't think I'm the only one, because I've had to field a few calls from people saying ‘I’m not seeing the views under section x' and I've had to explain that they need to expand the category to see the views nested inside - and their response is ‘oh I thought it was expanded’ 😆 Finally got around to talking to my sub-conscious brain and seeing why it was always confused, and I think the issue is that (this is probably exaggeration) every other product has their arrows pointing in the opposite direction. I've found that most other products use the down arrow to show that the folder/category/etc is expanded - whereas Zendesk views use the down arrow to show that (I'm assuming) you can press down to show more items - i.e. the down arrow indicates that the category is collapsed.To illustrate: Zendesk views Collapsed category (sub-items hidden) - arrow faces down Expanded category (sub-items shown) - arrow faces up then contrast this with all the other tools which have trained my brain the other way: Gmail mail folders Collapsed folder (sub-items hidden) - arrow faces to the right Expanded folder (sub-items shown) - arrow faces down Sublime text Collapsed folder (sub-items hidden) - arrow faces to the right Expanded folder (sub-items shown) - arrow faces down Source tree Collapsed folder (sub-items hidden) - arrow faces to the right Expanded folder (sub-items shown) - arrow faces down Jira navigation Collapsed folder (sub-items hidden) - arrow faces to the right Expanded folder (sub-items shown) - arrow faces down Apple notes Collapsed section (section text hidden) - arrow faces to the right Expanded section (section text shown) - arrow faces down Apple finder Collapsed folder (sub-items hidden) - arrow faces to the right Expanded folder (sub-items shown) - arrow faces down Safari / Edge / Chrome bookmarks folders Collapsed folder (sub-items hidden) - arrow faces to the right Expanded folder (sub-items shown) - arrow faces down …. i'll stop, but in just hunting around in applications that I have easily at hand, I couldn't find any examples of an app/tool doing it the other way - all the examples (even Google and Apple seem to agree) seem to use the same unwritten convention of “arrow facing downwards = section/folder/category is expanded”. Anyway, it's not a huge thing, but it does literally confuse me every time I use them 😄 Thanks for listening!
I would like to see some improvements to the Suspended Tickets view. One of our instances has multiple teams that aren't truly related to each other, but we have to work with each team individually to have them manage their suspended tickets to recover false positives and to clear out spam. Allow the ability to see/filter the Received at address. When multiple teams need to manage suspended tickets, they have to open each suspended ticket to understand if it is theirs or not. Because the received at address is hidden, they may be looking at tickets meant for other teams, or that they've already reviewed. Provide logs/data on which tickets were recovered or deleted. Suspended tickets are still volume that comes into our teams. I would love to see more data on who is recovering or deleting these. Even if I could see the received at email, the cause, and the status (recovered, deleted, auto-deleted after 30 days) it would give me a ton of information to help me understand if there are issues with my email address or improvements I can make for my customer base. Allow for triggers to be applied to suspended tickets. I think this should be separate than standard rules, but allow me to augment suspended tickets with rules that help auto-recover or auto-delete tickets based on criteria I set. A good example of this is the Shredder app on the Marketplace. (which is a great solution for those that are allowed to install Marketplace apps in their instance). These features would help me do and understand a few things: For instances with multiple unrelated teams, they could manage their own suspended tickets without impacting other teams resulting in faster customer responses for false positives. We could automate the processing of known suspension issues that we commonly see. We can understand if there are opportunities for improvement. Suspended tickets can have high volumes for us, but once we recover or delete a ticket, we lose the ability to really learn from that. Data to help us research and improve what we have setup and integrated with Zendesk would be much easier.
It is common for tickets to have three or four agents each sending a single reply, creating a tie under the "most active" logic. In these cases, the QA is regularly assigned to whoever replied last, which is often just an agent acknowledging a customer thank-you. This undermines the integrity of QA evaluations and makes it difficult to accurately assess and coach agent performance. There is a filter available for total agent reply count on a ticket, but this is not the same as filtering by the reviewee's individual reply count. No workaround currently exists to ensure a QA is only assigned to an agent if that specific agent sent a minimum number of replies on the ticket. The ideal solution would be a filter that restricts QA assignment to a reviewee only if that specific agent sent X or more replies on the ticket (configurable threshold). This would prevent reviews from being assigned to agents with minimal participation and ensure evaluations reflect meaningful customer interactions.
With the new interface, I see the loss of functionality to move to the next ticket. Perhaps this is due to the fact that that feature was specific to the view. I don't like having to go back to the home screen each time. I would like to see the functionality to move to the next ticket and come back with this enhancement.
In my enviroment I have to create a segment and search rule for each organization (client) and I have over 100. With each AI Agent I have to duplicate these. It would be nice if I could just copy the AI agent or the segment/search rules from one to the other. If I am missing it, just let me know, thanks.
Please give a quick overview of your product feature request or feedback and note who in your org is affected by this issue [ex. agents, admins, customers, etc.]. I am using Omnichannel Routing to reassign tickets to a group when a user is in a custom Out of Office status. Currently, when Omnichannel Routing handles a ticket reassignment, the ticket events log simply lists the actor as "System" with no reference to Omnichannel Routing. This issue primarily affects Admins and Team Leads who are trying to audit ticket routing and troubleshoot assignment workflows.What problem do you see this solving? This would solve the lack of visibility and traceability in ticket routing. Right now, it is incredibly tough to research and explain to agents how or why a ticket was reassigned when the only footprint in the ticket events is a generic "System" update.When was the last time you were affected by this lack of functionality, or specific tool? What happened? How often does this problem occur and how does this impact your business? I am affected by this on a weekly basis when agents ask why a ticket was removed from their queue or assigned to someone else. When checking the ticket events to investigate, there is no explicit mention of Omnichannel Routing. This impacts our business because it forces Admins to spend excess time jumping between ticket events and analytics dashboards just to confirm that Omnichannel Routing was actually the engine that reassigned the ticket due to an Out of Office status.Are you currently using a workaround to solve this problem? (If yes, please explain) Yes, but it is manual and time-consuming. I have to find the exact timestamp of the generic "System" assignment event in the ticket, and then navigate away to the Zendesk Agent State detail dashboard. From there, I review the agent's state for that specific day and time to determine if they were in an Out of Office status. If they were, I can finally conclude that Omnichannel Routing drove the reassignment.What would be your ideal solution to this problem? How would it work or function? My ideal solution would be for the ticket events log to explicitly name "Omnichannel Routing" as the source of the assignment action, rather than just saying it was done by "System". Alternatively, adding a detailed event note explaining that the reassignment was triggered by an agent's specific capacity or Out of Office status would give us the full context we need right inside the ticket.
The schedule trigger for Action Builder has a frequency selector, but only a Daily option. Ideally this would include hourly at a minimum, but also a custom run (ie. 4 hours), minutes, etc.
Please give a quick overview of your product feature request or feedback and note who in your organization is affected by this issue [ex. agents, admins, customers, etc.] (2-3 sentences)This feedback is primarily from agents who use Zendesk tickets throughout the day. Some agents feel that moving the dropdown for other tools to the left reduces the space available for tickets, which are the main focus of their work. There are also concerns about the visual design, including the harsh black highlight on the active ticket and tabs that are not clearly separated unless hovered over.What problem do you see this solving? (1-2 sentences)Improving the layout and visual hierarchy would help agents stay focused on tickets and navigate the interface more easily. Better use of space and clearer tab separation would create a more intuitive and less distracting experience.When was the last time you were affected by this lack of functionality, or specific tool? What happened? How often does this problem occur and how does this impact your business? (3-4 sentences)This issue was noticed recently during regular day-to-day ticket handling by agents. The updated layout made the ticket area feel more cramped, and the active ticket styling felt visually distracting. The lack of clear separation between tabs also caused some confusion when navigating between them. This is an ongoing issue that affects agents daily and can slow down workflow efficiency and overall user comfort.Are you currently using a workaround to solve this problem? (If yes, please explain) (1-2 sentences)There is no real workaround for the layout and styling concerns at this time. Agents are simply adapting to the changes, but the interface remains less comfortable and intuitive than before.What would be your ideal solution to this problem? How would it work or function? (1-2 sentences)Ideally, the ticket view would be given more priority in the layout, with secondary tools taking up less space. It would also help to soften the active ticket highlight and add stronger visual separation between tabs so they are clearly distinguishable at all times.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
OKSorry, our virus scanner detected that this file isn't safe to download.
OK