The Zurich release has arrived! Interested in new features and functionalities? Click here for more

On Hold SLA Best Practices

RimaC
Tera Contributor

Looking for some suggestions or guidance on timelines for On Hold ticket status. Any examples or ideas for different types of On Hold reasons you can share? Thanks in advance!

1 ACCEPTED SOLUTION

Robbie
Kilo Patron
Kilo Patron

Hi @RimaC,

 

Adding on to what @Dr Atul G- LNG has provided re potential 'On Hold reasons', I would say the duration (as well as the reasons) depend on the process you're referring or applying this to.

For example, working on internal Incidents vs external Customer Service cases would differ.

Using CSM (Customer Service Management) cases as a good example to help your thought process, similar to ServiceNow's own support process, I have implemented something for a customer whereby once the Case is placed On Hold, and it's 'Awaiting response from customer', this in turn triggers a workflow.

At 3, 6, and 9 day intervals an email is sent to the customer advising the customer that we're waiting for a response.... if no response is received after the end of 9 days (So 10 days from the time the ticket was placed on hold), the ticket is then moved to the Resolved state. 

This means the SLA stops, and then using standard out of box process, the customer is advised due to no action their case is placed into Auto Resolved for which they have a further 7 days to respond. If by the end of that period, the ticket is closed.

During any time from initially being placed on hold or Resolved, if the customer responds either via email or on the ticket/via portal etc, the ticket will go back into 'In Progress'

 

Does that help?

 

To help others (or for me to help you more directly), please mark this response correct by clicking on Accept as Solution and/or Helpful.

 

Thanks, Robbie

View solution in original post

4 REPLIES 4

Dr Atul G- LNG
Tera Patron
Tera Patron

Hi @RimaC 

 

OOTB SN provide 4 on hold reason on incident

- Awaiting Caller

- Awaiting Change

- Awaiting Vendor

- Awaiting problem

 

If you want you create more but my experience say these 3 are sufficient to use

*************************************************************************************************************
If my response proves useful, please indicate its helpfulness by selecting " Accept as Solution" and " Helpful." This action benefits both the community and me.

Regards
Dr. Atul G. - Learn N Grow Together
ServiceNow Techno - Functional Trainer
LinkedIn: https://www.linkedin.com/in/dratulgrover
YouTube: https://www.youtube.com/@LearnNGrowTogetherwithAtulG
Topmate: https://topmate.io/atul_grover_lng [ Connect for 1-1 Session]

****************************************************************************************************************

Robbie
Kilo Patron
Kilo Patron

Hi @RimaC,

 

Adding on to what @Dr Atul G- LNG has provided re potential 'On Hold reasons', I would say the duration (as well as the reasons) depend on the process you're referring or applying this to.

For example, working on internal Incidents vs external Customer Service cases would differ.

Using CSM (Customer Service Management) cases as a good example to help your thought process, similar to ServiceNow's own support process, I have implemented something for a customer whereby once the Case is placed On Hold, and it's 'Awaiting response from customer', this in turn triggers a workflow.

At 3, 6, and 9 day intervals an email is sent to the customer advising the customer that we're waiting for a response.... if no response is received after the end of 9 days (So 10 days from the time the ticket was placed on hold), the ticket is then moved to the Resolved state. 

This means the SLA stops, and then using standard out of box process, the customer is advised due to no action their case is placed into Auto Resolved for which they have a further 7 days to respond. If by the end of that period, the ticket is closed.

During any time from initially being placed on hold or Resolved, if the customer responds either via email or on the ticket/via portal etc, the ticket will go back into 'In Progress'

 

Does that help?

 

To help others (or for me to help you more directly), please mark this response correct by clicking on Accept as Solution and/or Helpful.

 

Thanks, Robbie

RimaC
Tera Contributor

Thank you Robbie, that is helpful insight on how to handle On Hold timelines, and auto-Resolve.

No worries at all @RimaC - glad to help.

 

Robbie