To apply service-level agreement (SLA) to your tickets, you must set the Priority field on the ticket first. Use the process below to automate that action using triggers.
The workflow includes the steps below:
- Step 1: Create a trigger that sets priority for all tickets for your SLA
- Step 2: Modify this trigger to set priority based on tags
- Step 3: Verify that you set up the trigger correctly
Step 1: Create a trigger that sets priority for all tickets for your SLA
Triggers can look for keywords to set ticket priority and SLAs. In the example below, the trigger will set all tickets at the same priority.
To create a trigger that set priority for all tickets
- Create a trigger
- Add the conditions below under Meet ALL of the following conditions
- Object > Ticket > Ticket | Is | Created
- Object > Ticket > Priority | Is | -
- Add the action below under Actions
-
Object > Ticket > Priority | Normal
-
Object > Ticket > Priority | Normal
- Select Create trigger
Step 2: Modify this trigger to set priority based on keywords
You can use any ticket properties, such as custom fields, to set priority on tickets. In this example, we will demonstrate how to use keywords as trigger conditions. The trigger will set the priority based on the keywords found in the ticket.
To create a trigger that sets priority for all tickets with a tag
- Create a trigger
- Add the conditions below under Meet ALL of the following conditions
- Object > Ticket > Ticket | Is | Created
-
Object > Ticket > Comment Text | Contains at least one of the following words |
sales
- Add the action below under Actions
-
Object > Ticket > Priority | Normal
-
Object > Ticket > Priority | Normal
- Select Create trigger
Step 3: Verify that you set up the trigger correctly
View the ticket events to verify that your trigger is running correctly. The ticket events include all triggers applied to your ticket and reflect changes in ticket priority. For instructions on how to view ticket events, see this article: Viewing all events for ticket updates.
For other questions about the ticket priority field, see the articles below:
3 comments
Shweta Gupta
Hi Tiann,
This is helpful.
I have a follow-up question - Based on the above, how can I keep on assigning tickets to agents (round robin or any fashion). I tried the Round Robin app on marketplace and Play Mode on Zendesk and they are not really helpful and my usecase is not solved with them.
Thanks.
Regards,
Shweta
0
Austin Killey
Really great question @.... Is there anything in particular about the Round Robin app or Play/Guided Mode for our ticket views that hasn't been working out as you expected?
Beyond those 2 methods, our next option could be to use either an Assignee or Group action in a trigger that's added to the very bottom of your trigger firing order, which would help assign any received tickets if they haven't already been assigned to an Assignee or Group by other triggers.
In that setup, you'd be able to assign a ticket to a group as a whole (where agents in that group could assign themselves individually to tickets) or you could choose a specific agent, where things might get a bit hairy once that particular agent starts getting more tickets assigned to them than other agents.
Beyond trigger usage though, we could also look at another 3rd-party app like Playlist Ticket Assignment, which also happens to have its own round-robin routing, along with a few other bells and whistles. Looks promising!
0
Beth
Hi! Is there a way to trigger the SLA only when a ticket is assigned to an agent? Currently, the SLA starts as soon as the ticket is created based on the ticket priority, but for better efficiency and time management (for us), I’d like to know if it can be triggered only when an assignee is added.
0