Including {{ticket.description}} placeholder in trigger
Our team has received numerous customer complaints that the acknowledgement emails they receive via trigger do not contain any identifying information. If they submit say, 5 tickets in a row, they do not know which ticket number pertains to which request.
We tried adding the {{ticket.description}} placeholder to our trigger, as this would alleviate the issue. However, it was confirmed by Zendesk that this won't work as it is blocked when sending to the requester and CCs. The reason being issues with Spam when include the ticket description, which seems to be a very odd reasoning when spam could affect any and all tickets whether or not this placeholder is used. Zendesk seems to have pretty involved Spam filters already, so I'd hope there will be able way to update and allow this placeholder in the future.
-
Second on this request. Allowing the ticket description, even part of it, to be included in the email would be very helpful.
-
I have this exact question.
-
Agreed, we would also like to be able to send the ticket description in the automatic e-mail sent when a user opens a request.
-
Same here. No matter how many funky placeholder hacks I tried, I was honestly shocked that it's not possible to add the ticket description to the confirmation email we send out after a ticket has been created. I hope to get this functionality soon, but I don't have high hopes. It's just clear that Zendesk is not the right tool to bet on, if you want to create good CX for your customers.
-
Resurrecting this thread because it is still an issue. Not only does ticket description not work but ticket.comments doesn't either. Support confirmed that they suppress this in the initial acknowledgement email to the requestor and to the CCs.
It is highly desirable to be able to list the original comment for anyone CCed at a minimum. Our CEO is copied on some ticket submissions but due to the volume of email he receives cannot always determine what the ticket is about until an agent has replied.
-
This is an issue for us as well, for much of the same reasons Harrison described above. Can the original description be copied into a custom field that we can then add to the trigger?
-
Can Zendesk (or anyone else) comment on why the "ticket description" won't pull through on trigger emails?
I have "ticket.description" as a placeholder in a trigger email that goes to customer requesters and I did not realize this issue until a customer just brought it to my attention.
The customer is telling me that the section that should have the ticket description is blank when he includes images or attachments in his ticket, but it is not blank when there is not an attachment.
Iniciar sesión para dejar un comentario.
7 Comentarios