dwalby Posted May 21, 2018 Share Posted May 21, 2018 Hi all, In our instance when requests are submitted via the portal they're assigned to the 1st line service desk queue but do not have an SLA/Priority assigned until an analyst has picked up the request. These are often getting missed in the mass of requests coming into the queue, is there a way of creating an escalation trigger to alert the 1st line analysts despite the fact they do not have an SLA associated? Thanks in advance Link to comment Share on other sites More sharing options...
Steven Boardman Posted May 21, 2018 Share Posted May 21, 2018 @dwalby what is it you are looking to alert the 1st line team too? a new request has come in? has been sitting in the queue but not assigned for x period? or some other criteria? also what sort of notification do you envisage? On a separate note, is there any reason why the SLA's are not started immediately, regardless of a member of the team owning them? if they are routed from the portals via services > catalog items are you not able to to determine what the SLA should be in advance or are you awaiting an agent to review the request before setting the priority etc? Steve Link to comment Share on other sites More sharing options...
dwalby Posted May 21, 2018 Author Share Posted May 21, 2018 @Steven Boardman - yes currently the 1st line analysts are completing an impact assessment manually. Arguably this could be reviewed and an SLA determined automatically based on the prog cap results submitted by the end-user. I'll need to look into that but that'll be a long-term activity for me. In the meantime I'm looking to alert the 1st line team that there has been a request outstanding for X amount of time, via Hornbill Notification and a team e-mail if possible. Link to comment Share on other sites More sharing options...
Steve Giller Posted May 21, 2018 Share Posted May 21, 2018 I have an "Incoming" SLA that is automatically applied, this allows the normal escalations to be utilised. The Process suspends until a priority is assigned, and at that point it calculates the new SLA from the assigned Priority. This is a practical workaround for us, might be worth a try. 1 Link to comment Share on other sites More sharing options...
Steven Boardman Posted May 21, 2018 Share Posted May 21, 2018 Thanks @DeadMeatGF, @dwalby after the suspend wait for priority use the Request > Update Request > Service Level which will automatically re-evaluate your Service Level rules and invoke the correct one based on the priority chosen (if that is what you have based your SL rules around) 1 Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now