Recherches récentes
Pas de recherche récente

Aaron Schweitzer
Adhésion le 15 avr. 2021
·
Dernière activité le 22 oct. 2021
Suivis
0
Abonnés
0
Activité totale
17
Votes
12
Abonnements
2
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 Aaron Schweitzer
Aaron Schweitzer a ajouté un commentaire,
+1 for this feature.
Being able to remove cc's on ticket creation (vs update as indicated in the HTTP target workaround) as well as adjust specific cc's would be ideal.
Given that all other notifications are Trigger - driven, it seems intuitive to do the same with these.
Afficher le commentaire · Publication le 21 juin 2018 · Aaron Schweitzer
0
Abonnés
1
vote
0
Commentaire
Aaron Schweitzer a ajouté un commentaire,
@Nicole-
The use cases are pretty clear in this thread. Organizations which have high volumes of tickets or email need a visual and/or auditory notification to allow them to identify relevant new tickets in the midst of a torrent of emails. It's about easy of use in separating what's important from the noise of day to day work.
Teams are often stretched and must balance multiple priorities within and outside of Zendesk. Push notifications are a global UX trend in many businesses, websites and SaaS platforms for good reason.
Ideally, I would like to see some control over which notifications are pushed by group/agent/org..etc... perhaps with trigger rules.
Afficher le commentaire · Publication le 26 avr. 2018 · Aaron Schweitzer
0
Abonnés
6
Votes
0
Commentaire
Aaron Schweitzer a ajouté un commentaire,
+1 This needs to be built-in to Zendesk.
Afficher le commentaire · Publication le 04 mai 2017 · Aaron Schweitzer
0
Abonnés
9
Votes
0
Commentaire