Customizing Home Dashboard
Hi,
I've been trying to customize the Home Dashboard but from my understanding this is not possible on Zendesk Support
I am referring to this view (see screenshot below yo avoid confusion):
Currently, I think this view doesn't bring/add any value to our work so I was wondering whether a customization (at admin level) of shown data and stats could improve what I can see.
I work as an admin on the Support app, which means I don't directly manage or reply tickets but I overview the work of the team and organize/optmize the agent workflow. It would be helpful to have an overview of the team agents instead of my statistics, which will be always zero since I don't work on tickets.
Aside on an old thread, I cannot find any resource on this particular topic and I am wondering if customizing for admin is possible (even in the future if this is a planned to release feature).
Thanks
Giulio
-
Official comment
Hi everyone!
I'm Zac with our Product team. We're making the Dashboard better, with a focus on how it optimizes an agent's daily productivity. The vision is to make it a central, seamless space for agents to execute work, with less reliance on Views to get things done.
I'm looking forward to hearing more feedback about Dashboard customization. While customization itself is not on the roadmap in the near future, the Dashboard is due for some updates and I'd love to hear how you'd improve the it so we can make it a great experience out of the box.
In future replies to this thread, it would help me to read the following:
- What information is most useful and actionable?
- What information would you remove from today's dashboard?
- What would it take for Dashboard to replace Views in your daily work? How helpful would it be to show relevant work to an agent in one space, rather than have them navigate and choose between Views?
I'm open to conversations - just @ me here if you'd like to strike up a correspondence or jump on a Zoom.
-
At present, the Support account home screen is not customizable. I'm moving your post to our Feedback on Support topic for visibility, and so other users can upvote and add their own comments (and feel free to add more information yourself, and/or reformat your post using our template to help ensure our product team has the information they need. Thanks!
-
Hi there,
We would love to hear more about your use case! We will follow up via email. Thank you!
-
It would be great to allow the home dashboard to be configurable. As OP mentioned, different people use Zendesk in different ways and have needs for different levels of information
-
It would be perfect to permit the home dashboard to be configurable. As OP referenced, various individuals use Zendesk in various ways and have needs for various degrees of data
-
I couldn't upvote this one enough. We use Zendesk with multiple brands configured and it would be great if I could filter the dashboard view to be specific to a brand.
-
Definitely need this capability. At a minimum add columns showing such fields as Topic or add sections to further break down by Type.
-
Being able to customize each agents dashboard similarly to creating a 'view' would be very helpful.
-
Completely agree! I'll take it further, as the VP over my team, I would like to be able to see team, individual agent, and ticket statistics in real time without having to run a report or go count tickets manually. Or, let's say I have an escalation policy to make contact on bad survey tickets for my team. If I could see all bad survey tickets for my team, not just myself, be able to click that number and pull up a list of all bad survey tickets, it would save an enormous amount of time over a calendar year. The point of a home dashboard is to give you a snapshot of relevant information to inform of trends or problems. This dashboard is very lacking.
-
Same thing here,
Our issue : Requester sends a new comment, gets back to the back of the line because we can't filter from date of ticket creation vs ticket update. So some department end up having tickets unanswered for + 5 days because customer reached again on a non-answer from us.
-
Thanks for your feedback, Philippe!
-
That's correct; we'd want the ability to customize the dashboard.
-
I've had feedback from users that they would like to be able to customize the activity feed to include tickets they've been CC'd in. Is that kind of thing planned in any features?
Thanks
Alec
-
This feature is definitely needed. As the Director of Global Support I want to be able to flag region, organization, etc. I also want to be able to hide the bar on the left of the screen that shows updates as I don't need them
-
Agreed. Dashboard is not useful for any level currently. A dashboard is supposed to provide useful, actionable info at a glance. Customization of the dashboard is needed. I have to go to Views to get more useful information.
I expected a higher level of useful customization from the premiere ticketing platform.
-
Thanks to Philippe and Alec for some detailed and actionable feedback. I want to share a couple of things in response.
Philippe B. - we want to solve the problem of tickets falling to the back of the line. I'd be happy to chat some more about how we're thinking of sorting work in the new experience. How do you prefer to sort tickets? By "next SLA breach"? Last Updated by customer? Date of Ticket Creation? What's the primary efficiency metric you use in your contact center to help your team meet customer expectations?
Alec Jagosz - we plan for this experience to include CC's, as well as other relevant items for agents. I'd love to connect and talk about how your team use CC's, to make sure the experience is relevant and useful. For starters - when do you CC other agents on your team? Do recipients of a CC have an obligation to respond? If so, how do you track productivity for agents who respond to CC's, and does it factor into their performance KPIs? Do CC's need to show up indefinitely, or only until they are actioned?
Thanks for engaging here and I look forward to continuing this conversation!
Please sign in to leave a comment.
16 Comments