When you deal with a lot of customers, it's very easy for some of the more upset ones to fall through the cracks. More often than not, you can prevent upsetting customers by keeping track of your escalated tickets. This support tip will help you create triggers to escalate your tickets more effectively.
Custom triggers are only available on the Team, Professional, and Enterprise plans.
Creating your group
- In Admin Center, click
People in the sidebar, then select Team > Groups.
- Click Add group.
- Name the group Escalations, then select agents you want to handle escalated tickets.
- When you're finished, click Save.
Creating your triggers
You can manage your escalated tickets with three types of triggers. For more information on creating custom triggers see, Streamlining workflow with ticket updates and triggers.
Escalation triggers
Your first trigger will escalate tickets based on the text your requester uses in their ticket.
- In Admin Center, click
Objects and rules in the sidebar, then select Business rules > Triggers.
- Click Add trigger.
- Name your trigger.
- Under Meet ALL of the following conditions, select Ticket: Status>Less than>Solved.
- Click Add condition.
- Select Ticket: Tags>Contains none
of the
following>Escalated_Customer.Note: It is important to add this trigger, so you create a nullifying condition to prevent the trigger from running over and over again.
- Under Meet ANY of the following
conditions, select Ticket: Comment
Text>Contains at least one of the
following words. You will want to insert
common words and phrases found when customers are
upset.
- Under Actions, select Ticket: Add Tags>Escalated_Customer.
- Add a new condition and select Ticket: Priority>Urgent.
- Add a new condition and select
Ticket:Group>Escalations.
- Click Create.
Bad CSAT triggers
Your second set of triggers will escalate tickets with poor satisfaction ratings both with and without comments.
Without comments
- Click Add trigger.
- Name the trigger Bad without comment.
- Under the Meet ALL of the following conditions, select Ticket: Status>Less than>Solved.
- Click Add condition.
- Select Ticket: Satisfaction>is>Bad.
- Add a new condition and select Ticket:
Tags>Contains none of the
following>Bad_CSAT_no_comment.
- Under Actions, select Ticket: Add tags
>Bad_CSAT_no_comment.
- Click Create.
With comments
- Click Add trigger.
- Name the trigger Bad with comment.
- Under the Meet ALL of the following conditions, select Ticket: Status>Less than>Solved.
- Click Add condition.
- Select Ticket: Tags>Contains none of the following>Bad_CSAT_with_comment.
- Add a new condition and select Ticket:
Satisfaction> Is>Bad with
comment.
- Under Actions, select Ticket: Add
tags>
Bad_CSAT_with_comment.
- Click Create.
Agent touches
- Click Add trigger
- Under Meet ALL of the following conditions, select Ticket: Status>Less than>Solved.
- Click Add condition.
- Select Ticket: Tags>Contains none of the following>3touch_or_more.
- Add a new condition and select Ticket: Agent
replies>Greater
than>3.
- Under Actions, select Ticket:Group>Escalations.
- Add a new condition and select Ticket: Add
Tags>3touch_or_more .
- Click Create.
Creating your view
You can now create a view for your Escalations group. Creating a view will enable your agents to easily identify the tickets that need their attention.
- In Admin Center, click
Workspaces in the sidebar, then select Agent tools > Views.
- Click Add view.
- Call it Escalations.
- Under Meet ALL of the following conditions, select
Ticket: Tags>Escalated_Customer,
3touch_or_more, Bad_CSAT_no_comment, Bad_CSAT_with
comment.
- Under Group by select Latest Update.
- Under Order by, select ID.
- In Available for, select Agents in group:
Escalations.Note: You want to select this group to prevent agents who do not handle escalations from having access to the tickets.
- Click Save.
This process is going to solve many of your escalations from wasting your time, the customer's time, and everyone's sanity. You can prevent customers from falling through the cracks, by placing an urgent status on them, as well as escalating them to a specific group of agents trained to solve escalated tickets.
2 Comments
The Escalation Triggers match criteria appears to be incorrect based on the way the "Comment" text condition matches (matches based on space, not commas). See here: https://support.zendesk.com/hc/en-us/articles/4408823778458-How-does-the-Comment-text-condition-work-in-business-rules-
Also confirmed this with independent testing.
Thanks for bringing this to our attention! We flagged this article to be updated by our documentation team so they will get this fixed as soon as possible.
Cheers!
Please sign in to leave a comment.