SLA do not work when ticket is created via email
AnsweredWe wanted our end users to open tickets by sending an email. Of course with an email the user does not have a "priority" field as exists in a form. The agent receiving this ticket would then define a priority, and the SLA policies will start to kick in.
When the SLA counter didn't work, I contacted support , and was very disappointed to hear that if an agent fills in the priority in the received ticket, the SLA will not work. For SLAs to work the user must fill the ticket priority which basically means this forces us to have our end users open tickets through a Zendesk form and leaves out the email option. I really wish Zendesk will change that , SLAs should work when an agent fills in the priority himself.
Has anyone encountered this problem as well?
-
Hi Ofer,
There is a lot of flexibility available in regard to SLA's.
In your case I would recommend having a trigger set a default priority at ticket creation.For example:
Conditions (all)
Ticket is created
Priority is -Action:
Priority is normal.You could add a channel condition as well if you only want this to apply for the email channel, but I would recommend it as is.
I hope this helps.
-
☝️ with this, SLA's should kick in from ticket creation.
-
Thanks Jacob.
So the trigger is:
Condition: Ticker is created
Action: Priority is normal
This means that a ticket will always be created with Priority normal, and so the normal SLA counter will apply.
But what if the issue for which the ticket has been created is of higher (or lower) severity?
-
With these two conditions
- Ticket is created
- Priority is -
Any tickets that already have a priority set will not be changed. You could also start with something other than "Normal", of course, agents can always change the priority if they have more information.
-
Hi Jacob,
I'm not sure I understand the comment "Any tickets that already have a priority set" will not be changed. I did a test and a ticket that opened with normal priority using the trigger I was able to change its priority to high.
Can you clarify what you meant?
-
Hi Ofer,
The trigger conditions (see below) will fire the action for all new tickets unless there already is a priority set.
-
Hi Jacob,
I created per your recommendation ( see screenshot) and the tests were successful.
Thank you for your help.
-
I'm creating a First Reply Time SLA and it appears to be firing on applicable tickets in the view, but I set the time to be 10mins, and it is showing on the view as 2 days from now. I'm new to here, can anybody give me some insight as to what's going wrong?? Thanks!
-
Hi Lester Gaddy
I suspect that what you're seeing is that you have defined your target in business hours, but the Next breach value is always displayed (as I recall) in calendar hours.
This article explains this better than I do here. Does that sound like what you're experiencing?
-
Hi @jacob I'm not sure I understand the comment "Any tickets that already have a priority set" will not be changed. I did a test and a ticket that opened with normal priority using the trigger I was able to change its priority to high.
-
Hi Haaji SB
That comment was explaining how this trigger works (at ticket creation):
You can use the same condition (Priority is -) to have the trigger skip any tickets that already have a priority set. I hope that helps.
Please sign in to leave a comment.
11 Comments