This article contains a reference list of our ticket trigger recipes. For a complete list of ticket trigger resources, see Triggers resources.
Ticket triggers recipes from Zendesk:
- Allowing original group and assignee on follow-up tickets
- Can I configure a trigger to add a comment to a ticket?
- How can I route tickets to groups based on the support address they are received at?
- Notifying external email addresses
- How do I prevent email notifications from being sent out on SMS tickets?
- How can I prevent agents from reassigning tickets to other agents?
- How do I create a trigger based on a ticket subject?
- Sending holiday notifications using triggers
- Automatically tagging tickets from specific users and orgs
- Adding comments and notes to tickets using triggers (Advanced AI add-on)
- Automatically closing tickets created by abandoned calls
- Using triggers to manage requests from important customers (custom org fields)
- Using triggers to manage requests from important customers (multiple organizations)
- How can I send automated replies from a specific support address?
1 comment
Chris Smith
We have a very nuanced business with about 100 triggers in play. A small number of triggers capture the bulk of the volume while the remaining triggers capture the most nuanced volume. Is it best to place the high capture triggers at the front of the progression or place the lower, nuanced triggers at the front? Does it matter?
0