Recherches récentes
Pas de recherche récente

Ben Kroes
Adhésion le 22 oct. 2021
·
Dernière activité le 01 nov. 2024
Suivis
0
Abonnés
0
Activité totale
16
Votes
5
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 Ben Kroes
Ben Kroes a ajouté un commentaire,
+1
Afficher le commentaire · Publication le 18 juil. 2024 · Ben Kroes
0
Abonnés
0
Votes
0
Commentaire
Ben Kroes a ajouté un commentaire,
We've created groups and hidden them using this Account Control App. We use Zendesk messaging, and needed a way to route chat requests to the appropriate group of agents. In our use case, we have an IT group with 10 agents. However, only 5 of these agents have the skills needed to service a specific line of business that we capture with a bot during the messaging flow. We needed to create a group for these 5 agents, but this group is only needed for routing messages. As such, we don't want everyone else in our account to see and assign tickets to this group. It would be nice if this app was able to hide the group even when an agent uses the bulk "Edit ticket(s)" button. Even better, if there was a different way to assign incoming messages to a group of agents with a specific skill set (without having to create a Zendesk group) that would be ideal. I'm sure this is a unique use case, but wondering if anyone else has run into this?
Afficher le commentaire · Modification le 28 févr. 2024 · Ben Kroes
0
Abonnés
0
Votes
0
Commentaire
Ben Kroes a ajouté un commentaire,
Our organization would really like to see this feature as well.
Afficher le commentaire · Publication le 26 avr. 2021 · Ben Kroes
0
Abonnés
1
vote
0
Commentaire