How to prevent auto-assign triggers from assigning tickets to OOO agents? | Community
Skip to main content

How to prevent auto-assign triggers from assigning tickets to OOO agents?

  • March 15, 2022
  • 2 replies
  • 0 views

I have never been able to make it work properly. We have triggers that auto-assign tickets in local languages to specific agents. And we use the OOO app to prevent assigning tickets to OOO agents.

When an agent turns on their "Unavailable status" and a ticket in a local language comes in, it still gets auto-assigned to that agent because the auto-assign trigger uses the condition "Ticket is created". At the moment a ticket is created, there is no `agent_ooo` tag applied to it because this tag is applied later as an update to the ticket.

We also have the feature "force unassign tickets" turned on in the OOO app but it still doesn't help because the `agent_ooo` tag never applies to tickets that are auto-assigned right away.

How can I modify the auto-assign trigger or create some additional trigger that would ensure that a ticket doesn't get auto-assigned to an OOO agent?

Thanks!

 

2 replies

  • Author
  • March 15, 2022

Also, what does this condition exactly do?

"Agent is Out? is Checked"

At what point does it check if an agent is OOO? 

I tried to create an additional trigger that would assign tickets after they had been auto-assigned, but I can't make this condition work.


Dane13
  • April 27, 2022

Hi Galina,

It seems this inquiry have been lost in our views. Upon checking, a ticket has already been submitted for this concern. Please continue to coordinate with the Advocate handling the ticket for this to be resolved.