Búsquedas recientes
No hay búsquedas recientes

Shane Skeens
Incorporación 18 ene 2022
·
Última actividad 18 ene 2022
Seguimientos
0
Seguidores
0
Actividad total
6
Votos
2
Suscripciones
2
RESUMEN DE LA ACTIVIDAD
INSIGNIAS
ARTÍCULOS
PUBLICACIONES
COMENTARIOS DE LA COMUNIDAD
COMENTARIOS DE ARTÍCULOS
RESUMEN DE LA ACTIVIDAD
Última actividad de Shane Skeens
Shane Skeens hizo un comentario,
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.
Ver comentario · Editado 18 ene 2022 · Shane Skeens
0
Seguidores
0
Votos
0
Comentarios
Shane Skeens hizo un comentario,
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!!!
Ver comentario · Publicado 18 ene 2022 · Shane Skeens
0
Seguidores
4
Votos
0
Comentarios