Vor Kurzem aufgerufene Suchen
Keine vor kurzem aufgerufene Suchen

Kai Schmitte
Beigetreten 16. Okt. 2021
·
Letzte Aktivität 08. Jan. 2024
Folge ich
0
Follower
0
Gesamtaktivitäten
106
Stimmen
56
Abonnements
20
AKTIVITÄTSÜBERSICHT
BADGES
BEITRÄGE
POSTS
COMMUNITY-KOMMENTARE
BEITRAGSKOMMENTARE
AKTIVITÄTSÜBERSICHT
Neueste Aktivität von Kai Schmitte
Kai Schmitte hat einen Kommentar hinterlassen
Dear Walter Bellante,
thanks for the quick answer.
I need to be able to report for myself on different topics. Like: How does product x perform? Or how many tickets does my team b gets per week?
Dashboard restrictions don't help at all with this task.
To be honest, the current bookmark feature is already not enough, I would like to be able (and enable viewers) to set their own bookmarks without the need to edit the dashboard.
Kai
Kommentar anzeigen · Gepostet 31. Okt. 2023 · Kai Schmitte
0
Follower
0
Stimmen
0
Kommentare
Kai Schmitte hat einen Kommentar hinterlassen
Dear Agnieszka Czajka,
thanks a lot for the notification!
Currently all planned developments will need Bookmarks to show data filtered to different teams, different languages or different products. And switch between them easily.
Means: before I start to work with the Beta Builder, this ability need to be implemented. (Already added my feedback in the respective thread)
Best Regards
Kai
Kommentar anzeigen · Gepostet 31. Okt. 2023 · Kai Schmitte
0
Follower
0
Stimmen
0
Kommentare
Kai Schmitte hat einen Kommentar hinterlassen
Same here.
This would show how efficient our Guide articles and proposals are...
Kommentar anzeigen · Gepostet 09. Okt. 2023 · Kai Schmitte
0
Follower
0
Stimmen
0
Kommentare
Kai Schmitte hat einen Kommentar hinterlassen
Rather short test as the main needed features to even create a dashboard are not there:
- No Tabs
- No Bookmarks
These two features are the main reason to use a dashboard and not a report. Means: Currently the Beta is of no practical use.
As a side comment: I expect to be able to all filters to a dashboard that are available in the report.
Kommentar anzeigen · Gepostet 15. Sept. 2023 · Kai Schmitte
0
Follower
1
Stimme
0
Kommentare
Kai Schmitte hat einen Post erstellt
There should be a possibility to switch on/off the use of the "Explosion" in a report from within the Dashboard view.
Use case:
Report (columns) with 2 different Attributes in the "rows" section. Stacked is on.
Columns is year and month.
This gives a nice view of the full amount of tickets by month, with the correct combination of attributes.
Now I would like to allow the user to change this view into a split view where I get a single graph for each of the chosen Attribute values.
My example:
- Attribute 1: B2B / B2C
- Attribute 2: Ticket Status
The full view shows nicely the ticket status by B2B/B2C. Now I would like to drill down into the graph to show one graph each for 1. B2B and 2. B2C.
The latter can be easily reached by adding the B2B/B2C attribute to the "Explosion" of the report.
But I can't dynamically switch between "with explosion" and "without explosion". With the current features the dashboard will be messy - 2 (or 3) reports needed to show the data.
With my proposal the user can have 1 report in the dashboard and the viewer will be able to toggle between the full view and the "explosion" view.
Gepostet 13. März 2023 · Kai Schmitte
1
Follower
1
Stimme
0
Kommentare
Kai Schmitte hat einen Kommentar hinterlassen
Dane,
thanks for the reply.
The aim is to have a stacked column with the top 5 ticket subjects for the last 14 months to see if the distribution of ticket subject changes.
I just want to be able to see and read the full legend - and to show the graphics to management without the need to copy&paste the missing parts from the legend...
Means: as soon as I need a table, Zendesk Explore will be completely useless and I need to switch to a real business analysis tool.
KS
Kommentar anzeigen · Gepostet 25. Nov. 2022 · Kai Schmitte
0
Follower
0
Stimmen
0
Kommentare
Kai Schmitte hat einen Kommentar hinterlassen
No ability to search for a specific mail domain?
I'm looking for all ticket requestors that use a mail address with a specific mail domain - to identify users which should belong to the company (organization), but are currently not assigned to the organization.
Currently the search for phrase (" ") operator does not ensure that the format domain.tld is used, but it searches for the two words next to each other.
It would be needed to
1) Have a search that will only look into the mail addres of the user
2) Have a phrase search that works letter by letter - means that no altering of the search phrase is done, no fuzzy search
Kommentar anzeigen · Gepostet 17. Okt. 2022 · Kai Schmitte
0
Follower
0
Stimmen
0
Kommentare
Kai Schmitte hat einen Kommentar hinterlassen
Dane: How would I report on data with a long "name"?
Currently I need a 14-month review of Ticket Subjects (they have long, descriptive names) as a stacked bar. Even the Top5 version cuts 2-3 descriptions...
Kommentar anzeigen · Gepostet 07. Okt. 2022 · Kai Schmitte
0
Follower
0
Stimmen
0
Kommentare
Kai Schmitte hat einen Kommentar hinterlassen
The real problem is when the data is used outside of Zendesk.
Like an export or the need to show the data in a presentation.
Here the scrolling possibility can't be used.
Please take the need to have more legend options into consideration.
Kommentar anzeigen · Gepostet 07. Okt. 2022 · Kai Schmitte
0
Follower
2
Stimmen
0
Kommentare
Kai Schmitte hat einen Kommentar hinterlassen
Dane:
Thanks for the explanation. Many of our customers start entering a question before the agent joins, so it is probable that the first reply time is included in most chats - and thus the parallel lines happen - especially since the first reply is usually the longest reply time. We know that we would need more agents to handle incoming chats.
Is there any way to get a "clean" view on average reply times during a chat? Without the first answering time?
So that we can see if the agents are efficiently working - and to see if the amount of chats one agent is assigned is neither too small nor too big?
Thanks!
Kai
Kommentar anzeigen · Gepostet 16. Sept. 2022 · Kai Schmitte
0
Follower
0
Stimmen
0
Kommentare