You have a Feedback/Ideas Community: One of your customers is having a Community discussion about new features that they would like to see in your product. In this case you want to pass their feature request on to another department, in your Zendesk, because you found their idea interesting.

You have a Support Community: In this scenario your customers post in the Community to help each other out, but you see a specific post/comment that requires further assistance and you want to convert it into a ticket for your support team.

In both of the scenarios described above, you need to create a new trigger to notify the requester (the customer who created a post or comment in your Help Center), then modify existing triggers that check through tickets created to avoid multiple triggers firing at the same time for the same purpose.

Create Different Workflows

You can even create multiple types of notifications by adding a specific string of text to the ticket title or body, when you are converting the end-user contribution into a ticket.

This is how you do it:

Make sure you exclude the string from other similar triggers first by adding: “Ticket comment text: does not contain the following string”.

Create a new trigger and use under all conditions: “Ticket comment text: contains the following string” and specify what you are going to add in the ticket title/body.

Create a ticket from an end-user post/comment. Once you get the pop-up (shown below in the screenshot) add this string of text by typing it in. This is a manual process, but it will allow you to set different workflows for different request types, like you can do with ticket fields.