Recherches récentes
Pas de recherche récente

Noom
Adhésion le 16 avr. 2021
·
Dernière activité le 27 oct. 2021
Suivis
0
Abonnés
0
Activité totale
10
Votes
0
Abonnements
7
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 Noom
Noom a ajouté un commentaire,
Hi!
I'd like to see which agents viewed certain articles so we can analyze who's following our protocol and who isn't. Is that possible? I'm missing the agent attributes in all 3 data sets.
Afficher le commentaire · Publication le 08 mars 2021 · Noom
0
Abonnés
2
Votes
0
Commentaire
Noom a ajouté un commentaire,
Unfortunately, Graeme's suggestion doesn't do the trick.
I'm running into the exact same issue of not being able to report on true agent productivity because ZD automations e.g., moving a ticket from solved --> closed, are counting as 'public agent replies'. I also noticed that even internal comments would count as 'public replies' if you do a deep dive and look at every single ticket ID from your look. Reporting on agent productivity shouldn't be faulty IMO since that's the core of agent performance evaluation.
If I find a solution to this problem I will follow up on this thread.
Afficher le commentaire · Publication le 04 avr. 2020 · Noom
0
Abonnés
0
Votes
0
Commentaire
Noom a ajouté un commentaire,
+1000 - I very much agree with the above and I'm so surprised that the follow-ups do not inherit the previous tickets group and assignment by default. Like other people have mentioned already, with a high agent count creating 3 triggers per agent is just too much. Excited for the new PM and hopeful that this will be triaged soon!!!
Afficher le commentaire · Publication le 15 mai 2019 · Noom
0
Abonnés
1
vote
0
Commentaire