Question
When I create a ticket on behalf of my client, with a public comment, and submit the ticket to Solved the recipient is not receiving the email. How can I solve that?
Answer
If an agent creates a ticket on behalf of the end-user and submits the ticket to solved with the first public comment there is no default trigger that notifies the requester with the public comment.
In this case, you need to create a new trigger to make sure the message is sent.
Example Trigger:
- On the Triggers page, click Add trigger.
- Enter a title for your trigger.
- Add the conditions and actions for your trigger, see an example of conditions/actions below:
- Click Create trigger.
For your convenience, here's an example in text in case it helps.
Email Subject:
{{ticket.title}}
Email Body:
The ticket was created on your behalf.
{{ticket.comments_formatted}}
To add additional comments, reply to this email.
Your new trigger is added to the end of the list of triggers. You can reorder the list of triggers.
Note: This is one possible reason for issues with ticket creation while using the default triggers. If you checked the ticket events and you see that the trigger fired but the messages weren't still received by the requester, contact the Zendesk support team for further investigation.
13 Comments
HI there, I am trying to follow these instructions however, in our account, "current user is (agent)" is not there. The only ones available are Status, Assignee, Requester, Ticket, Privacy and Comment. Thanks for your help
Hi Gaetano,
The Current User option should show up if you scroll down when selecting the drop-down option. If you don't see this would you be able to provide is with a screenshot of what exactly you see on your end?
Thanks in advance!
Thank you Brett.
I've attached the screen shot as requested.
Hi Gaetano,
Can you confirm what plan level you're on? Customizable triggers is only available on the Team, Professional, and Enterprise plans. It's possible you're on the *Essential plan which doesn't have access to this functionality.
Let me know!
HI Brett, yes we are on Essential plan, though I would have thought that for such essential settings one didn't need to be on an upgraded plan. In the end, we are just trying to have the basic communication with our customers set up correctly and that's what Zendesk is supposed to be about, first and foremost.
Hi Gaetano,
The Essential plan includes the Default Triggers which will allow for you to communicate back and forth with your customers. However, if you want to create custom triggers to help automate some of your processes then you would need to be on at least the Team plan to do so.
I would recommend taking a look at our Plan Comparison Page to get a better understanding of what's included on your existing plan.
Let me know if you have any other questions!
Hello,
We are also having issues sending outbound tickets to end users. Could you please assist asap?
Hi Anna,
Can you tell us more about your situation? i.e. plan type, whether you've adjusted the triggers as suggested in the article above, what the issue you're having with outbound tickets is, etc.?
Wanted to let you know that {{ticket.comments_formatted}} is not an option on our end. We got the desired effect by using {{ticket.description}}. You may want to update this particular article! :)
Hello Ashley,
Appreciate you sharing your tip with us and glad you were able to find a solution to this issue, and we'll be sure to update our article for future use.
Hi,
We are also facing a similar issue. When we are sending a new email (public reply) to the customers, they are not receiving it. Either we submit the new ticket as Open or Pending, in any case, they are not being notified about the message we sent them. We are on a regular support plan.
Our customers have already missed too many of our emails until we found out about the issue today. Please help us in resolving this ASAP.
Hey Ahsan! Sorry to hear this is happening. It sounds like perhaps you're missing a trigger to notify your end users of proactively-created tickets. We recently added a default trigger for just this - I'd recommend making a version of Notify requester of new proactive ticket as outlined in this article! The default Notify requester of received request trigger doesn't work on proactive tickets, and the default Notify requester of comment update ticket doesn't work on brand new tickets! Let us know if that doesn't do the trick.
Madison,
Yes, it worked. Thanks a lot for the help. Additionally, I had to add a condition in another trigger "Notify requester of received request" that current user is not agent, as 2 triggers were being sent with the new ticket. Anyways, thanks for the help.
Please sign in to leave a comment.