Prioritizing unassigned tickets that have multiple updates/responses from end user

2 Comments

  • Official comment
    Barry Neary
    Zendesk Product Manager

    Hi, If you are using omnichannel routing engine you could change the priority of the ticket each time the ticket is updated by the end user - that would have the affect of moving the ticket up the queue order

  • Lightricks Ltd.
    Community Moderator

    Hery Aaron O'Connor

    If you do not have omnichannel, the following recipe has worked us when tackling the same issue:

    • User field: Create a Dropdown User Field called 'Active Tickets'. The dropdown choices are One or Multiple. 
    • Trigger # 1: 
      Meet ALL of the following conditions:
      Ticket | is | Created
      Active tickets | Not present

      Actions:
      Active tickets | One
      Add tags | active_tickets-one
      Remove tags | active_tickets-reset

       

    • Trigger # 2: 
      Meet ALL of the following conditions:
      Ticket | is | Created

      Meet ANY of the following conditions:
      Active tickets | is | One
      Active tickets | is | Multiple

      Actions:
      Active tickets | Multiple
      Add tags | active_tickets-multiple
      Remove tags | active_tickets-reset

      Trigger # 3: 

    • Meet ALL of the following conditions:
      Ticket | is | Updated

      Meet ANY of the following conditions:
      Status | Changed to | Solved
      Status | Changed to | Closed

      Actions:
      Active tickets | -
      Add tags | active_tickets-reset
      Remove tags | active_tickets-multiple
      Remove tags | active_tickets-one

       

    Once you set this up, you can create an SLA policy for these tickets, a dedicated View for them, etc. 

    0

Please sign in to leave a comment.

Powered by Zendesk