Recherches récentes
Pas de recherche récente

Shane Skeens
Adhésion le 18 janv. 2022
·
Dernière activité le 18 janv. 2022
Suivis
0
Abonnés
0
Activité totale
6
Votes
2
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 Shane Skeens
Shane Skeens a ajouté un commentaire,
Thanks for the reply, Benjamin! For our purposes, simply passing (replicating) the same information that is included on the ticket created from an email. "From", "To" and all Cc's, as well as any information included in the email itself (subject, body, attachments, etc).
Without understanding your new "endpoint" better, it's hard to say exactly how it could be optimally designed.
Afficher le commentaire · Modification le 18 janv. 2022 · Shane Skeens
0
Abonnés
0
Votes
0
Commentaire
Shane Skeens a ajouté un commentaire,
Agreed. This is a significant limitation that is causing us to re-evaluate the use of Zendesk in our Multi-brand environment, in which every brand has a unique email address. If a user sends it to one brand and Cc's another, the second will never hear of it. Even suspending the tickets would give some visibility into the issues received.
Please revisit this issue for us multi-brand customers!!!
Afficher le commentaire · Publication le 18 janv. 2022 · Shane Skeens
0
Abonnés
4
Votes
0
Commentaire