Recherches récentes
Pas de recherche récente

Dave Dyson
Adhésion le 14 mars 2024
·
Dernière activité le 07 févr. 2025
Zendesk Admin team at Samsara, Implementation Consultant at Envoy (goenvoy.co), Zendesk Community Moderator, Zendesk alum.
Suivis
0
Abonnés
0
Activité totale
25
Votes
8
Abonnements
8
APERÇU DES ACTIVITÉS
BADGES
ARTICLES
PUBLICATIONS
COMMENTAIRES DE LA COMMUNAUTÉ
COMMENTAIRES SUR L’ARTICLE
APERÇU DES ACTIVITÉS
Dernière activité effectuée par Dave Dyson
Dave Dyson a ajouté un commentaire,
Agnieszka Czajka Awesome, thanks for the update and we'll be looking forward to it!
Afficher le commentaire · Publication le 06 juin 2024 · Dave Dyson
0
Abonnés
0
Votes
0
Commentaire
Dave Dyson a ajouté un commentaire,
Agnieszka Czajka hi, is there a rough timeline on when the “next version” that will allow other (presumably custom) roles to change an agent's status?
We have the Admin role locked down to the team that controls the overall setup of our Zendesk instance, but the teams that manage the agents (including monitoring their statuses) is completely separate. So we're in the position of choosing between:
- Granting full Admin access to teams that shouldn't have it
- Increasing red tape and the admin team's workload by asking the WFM team to ask us to change agent statuses when needed
- Saying “sorry” to the WFM team and making them depend on idle timeout which affects metrics.
Thanks for any timeline you might be able to provide!
Afficher le commentaire · Publication le 06 juin 2024 · Dave Dyson
0
Abonnés
0
Votes
0
Commentaire
Dave Dyson a ajouté un commentaire,
Alina Wright Is there any update on this? We keep tight control over who can manage Zendesk settings (business rules, forms, fields, roles, etc.), but there are times when It would be very useful to allow someone to view the settings without being able to change them.
Afficher le commentaire · Publication le 24 mai 2024 · Dave Dyson
0
Abonnés
0
Votes
0
Commentaire
Dave Dyson a ajouté un commentaire,
We have a fairly complex set of SLA policies, and it would be helpful to be able to create a view showing tickets that have a specific SLA so be we make sure it's working as intented, and to create a view of tickets that have *no* SLA applied to them, so we can determine why that's the case. Thanks!
Afficher le commentaire · Publication le 08 mai 2024 · Dave Dyson
0
Abonnés
0
Votes
0
Commentaire
Dave Dyson a ajouté un commentaire,
What will the expected behavior be if the original Group has been deleted, or the original assignee is no longer an Agent?
Afficher le commentaire · Publication le 22 mars 2024 · Dave Dyson
0
Abonnés
2
Votes
0
Commentaire
Dave Dyson a créé une publication,
When the API requests breakdown dropdown selector is set to Dailly or Weekly, the Callers and endpoints dropdown can be used to select a specific day or week, and the three tables beneath will refresh to show numbers for that time period.
When the API requests breakdown dropdown selector is set to Yesterday / Hourly, the Callers and endpoints dropdown lists hourly windows, but the tables don't seem to refresh.
More strangely, when I have the API request dropdown set to "Last 7 days" / "Hourly", then select an hourly window, the table are responsive the first time I choose an hourly window. Choosing a different hourly window has not further effect - the table contents don't change. But if I choose "Last 7 days" again from "Callers and endpoints", it adds another row to the "Top 5 callers by volume" table (only that table, the other two tables are unaffected). Every time you select an hourly window after that, nothing will happen, but if you choose "Last 7 days" again it will add another row. You can repeat the process, adding more and more rows, and the extra rows don't go away until you refresh the entire browser page.
Publication le 14 mars 2024 · Dave Dyson
0
Abonnés
3
Votes
2
Commentaires
Dave Dyson a ajouté un commentaire,
I can see that choosing a time in the dropdown below the chart highlights the bar it corresponds do, but it would be more useful imho for it to work the other way -- select a bar and that chooses the value the in dropdown for you.
Afficher le commentaire · Publication le 14 mars 2024 · Dave Dyson
0
Abonnés
0
Votes
0
Commentaire
Dave Dyson a créé une publication,
Currently, when the API requests breakdown is set to Hourly, the time-axis labels are each long enough that it can be difficult or impossible to determine which vertical bar they correspond to. Conversely, the "tool tip" that appears when you hover over an individual bar shows the date (useful when the chart is set to show daily info), but not the timeframe for that bar (when set to hourly).
This makes it challenging to determine when exactly any API usage spikes are occurring.
(It'd be even better if clicking on one of the bars would immediately give you a breakdown of which endpoints and users are contributing to that time period's usage)
Modification le 14 mars 2024 · Dave Dyson
0
Abonnés
1
vote
1
Commentaire
Dave Dyson a ajouté un commentaire,
100% agree, this would be super useful:
- drill in on a specific endpoint to see which users have been calling it the most
- drill in on a specific user to see which endpoints they've been using the most
Afficher le commentaire · Publication le 14 mars 2024 · Dave Dyson
0
Abonnés
2
Votes
0
Commentaire