Recherches récentes
Pas de recherche récente

Brandon Tahquette
Adhésion le 25 févr. 2022
·
Dernière activité le 15 févr. 2023
Suivis
0
Abonnés
0
Activité totale
38
Votes
29
Abonnements
4
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 Brandon Tahquette
Brandon Tahquette a ajouté un commentaire,
Julio R. is there an update on your last comment? I'm also interested in showing the linking rate per agent but I am seeing the same issue that Bobby has reported above.
Afficher le commentaire · Publication le 15 févr. 2023 · Brandon Tahquette
0
Abonnés
0
Votes
0
Commentaire
Brandon Tahquette a ajouté un commentaire,
We have a lot of articles already built but we're looking to grow our ability to deflect with smaller and more direct articles. We don't want agents creating and then publishing the article without it going through a review first. If they create the article and copy the unpublished link, will Explore capture that as a linked article?
Afficher le commentaire · Publication le 05 janv. 2023 · Brandon Tahquette
0
Abonnés
0
Votes
0
Commentaire
Brandon Tahquette a ajouté un commentaire,
Lou We use that but the organization structure is one where we report data up to a corporate structure that is indirectly related in Zendesk. Each Franchisee is their own organization connected to the greater Corporate organization that meets with us and is asking for this information to prevent the case from going to a resolved status that results from bump bump solve. They are a demanding client, but the data is there. The problem is that explore only allows us to see total time in each status for the lifecycle of the case.
Afficher le commentaire · Publication le 26 juil. 2022 · Brandon Tahquette
0
Abonnés
0
Votes
0
Commentaire
Brandon Tahquette a créé une publication,
Example:
A client wishes to know long it has been since one of their users has had a case in pending w/out having to look directly at individual cases or to try to do the math by reviewing multiple "last response" columns to determine how long since the agent placed the case in a pending status.
Their end goal is to know how and when to press their end user to respond.
Currently, the system does not allow reporting on that metric.
More details can be found in my case with Support found here
Publication le 26 juil. 2022 · Brandon Tahquette
2
Abonnés
3
Votes
3
Commentaires
Brandon Tahquette a ajouté un commentaire,
My KCM needs to be able to leverage the templates that he's created without having to find/copy/paste every time he or one of his cross-functional partners needs to create new content. He works outside of the Support app and I'd like to keep it that way since he has very little need to work in/on Support cases. Even if he was more involved with tickets, giving him the ability to use those templates in both places makes the UX that much better and would give us the ability to be more efficient/scaled in his process.
Afficher le commentaire · Modification le 14 mars 2022 · Brandon Tahquette
0
Abonnés
3
Votes
0
Commentaire