Best Practices for Escalating to a level 2 or 3 team.

[Steven Lees-Smith]

Hi there,

I have been reading posts and articles and can see that we can add a workflow status of escalated to a ticket workflow.

Basically we have a global triage team who will assign a ticket to a Support team in Sydney or Vancouver.

BUT if the support team need to escalate the ticket I am not sure what has to happen then about team ownership.

If we have an escalated workflow step, is it a matter of having an automation process that will look for a status change to escalated and then it will remove the assigned group from and then assign it to the systems team?

There is also a conversation about having a Sydney and Vancouver systems team.  So I would imagine we can have a location of incident and when something is escalated it can look at the location and assign the systems team at that location?

We are trying to see what is potentially going to be the best workflow for escalations as it's a tad unclear currently.

[Benjamin]

Hi @Steven Lees-Smith ,

It depends on how the organization is structure and metrics used. What I've seen is that the support is seen as one team. So, depending on your timezone coverage, that team takes it up.  For example Vancouver teams takes care of tickets the first 12 hours of the day and the Sydney team takes the last 12 hours of the day. If the escalation happen during the end of the shift of one team, the other team takes over the response. The issue I see with being entirely separate is the like the example above, the shift ends for one team and the escalated ticket needs to wait. 

As a guideline, keep the workflow simple as possible and organize the support team instead to optimize coverage. 

Hope this helps.

-Ben