Vor Kurzem aufgerufene Suchen
Keine vor kurzem aufgerufene Suchen

Shane Skeens
Beigetreten 18. Jan. 2022
·
Letzte Aktivität 18. Jan. 2022
Folge ich
0
Follower
0
Gesamtaktivitäten
6
Stimmen
2
Abonnements
2
AKTIVITÄTSÜBERSICHT
BADGES
BEITRÄGE
POSTS
COMMUNITY-KOMMENTARE
BEITRAGSKOMMENTARE
AKTIVITÄTSÜBERSICHT
Neueste Aktivität von Shane Skeens
Shane Skeens hat einen Kommentar hinterlassen
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.
Kommentar anzeigen · Bearbeitet 18. Jan. 2022 · Shane Skeens
0
Follower
0
Stimmen
0
Kommentare
Shane Skeens hat einen Kommentar hinterlassen
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!!!
Kommentar anzeigen · Gepostet 18. Jan. 2022 · Shane Skeens
0
Follower
4
Stimmen
0
Kommentare