How to Avoid Response SLA Breach for Incidents Assigned to ServiceNow Run Support Group?

nameisnani
Giga Sage

yesterday

Hi Experts,

 

We are a ServiceNow Run Support team, and most of our work involves handling incidents.

 

One recurring challenge is that whenever an incident gets assigned to our support group, the Response SLA is sometimes breached before an engineer reviews or acknowledges the ticket. We are looking for automation options within ServiceNow to ensure we don't miss the Response SLA.

 

Current Situation

  • Incidents are assigned to the ServiceNow Run Support group.
  • Due to workload, off-hours assignments, or missed notifications, some incidents are not picked up on time.
  • This results in Response SLA breaches.

 

Auto Assignment Rules

If tickets remain in the group queue for a defined duration, automatically assign them to:

  • On-duty engineer
  • Round-robin assignment
  • Assignment Workbench rules

This reduces dependency on manual assignment.

 

 

Please provide configuration steps and if possoble please provide configuration scrrenshots 

 

 

0 Helpfuls
  • 88 Views
1 REPLY 1

sachinvic
Giga Guru

an hour ago

@nameisnani 

Hi,

For this scenario, I would recommend exploring ServiceNow On-Call Scheduling before building a custom round-robin assignment mechanism. It is designed to manage support rosters, identify available engineers, and escalate incidents when they are not acknowledged.

 

Here is how I would approach the configuration.

1. Configure the on-call schedule

Navigate to:

All > On-Call Scheduling > Create/Edit Schedule

  • Select the ServiceNow Run Support group.

  • Define shifts and add engineers to the roster.

  • Configure primary and secondary on-call coverage.

  • Define the escalation policy for each shift.

2. Configure acknowledgement-based escalation

ServiceNow provides an OOTB workflow called On-Call: Assign by Acknowledgement.

This is particularly relevant to your requirement because it:

  • Notifies the on-call engineer.

  • Waits for acknowledgement.

  • Escalates to the next person according to the configured escalation policy if there is no acknowledgement.

  • Records the escalation details.

Configure the appropriate trigger rules and notification preferences so the escalation process starts for the required incidents.

 

3. Configure SLA notifications

Navigate to:

All > Service Level Management > SLA Definitions

Review the Response SLA and configure notifications before the breach threshold. For example, alert the support lead when the SLA reaches 50% and 75% of its duration.

 

4. What about round-robin and Assignment Workbench?

  • Round-robin: Can be implemented through custom Flow Designer logic or assignment automation, with appropriate tracking to maintain rotation and avoid assigning work to unavailable engineers.

  • Assignment Workbench: Provides agent recommendations based on criteria such as skills and availability. However, validate its applicability to your Incident table and licensing before considering it for this requirement.

My recommendation: Start with On-Call Scheduling and acknowledgement-based escalation. This addresses the actual problem more directly than simply assigning an incident to the next engineer in the queue.

 

One important point: ensure that the Response SLA stop condition represents an actual acknowledgement or response, according to your organisation's SLA definition. Assignment alone should not automatically be treated as a response.

 

Official references (configuration guides with UI walkthroughs):

1. Configure or update an On-Call schedule:

https://www.servicenow.com/docs/r/it-service-management/on-call-scheduling/create-update-schedule-on...

2. On-Call Scheduling workflows:

https://www.servicenow.com/docs/r/it-service-management/on-call-scheduling/workflows-oncall.html

3. On-Call Scheduling:

https://www.servicenow.com/docs/r/it-service-management/on-call-scheduling/c_OnCallScheduling.html

4. SLA notifications:

https://www.servicenow.com/docs/r/it-service-management/service-level-management/c_SLANotifications....

 

Helpful? Please mark the response as Accepted Solution ✅ and close the thread  — this helps future readers find the solution faster.

 

Regards,
Sachinvic
✨ ArchX Certified | ✨ 16x ServiceNow AI MVP

0 Helpfuls