Connectors

/

ServiceNow

/

ServiceNow SLA breach risk report
Report

See which ServiceNow SLAs are about to breach

For service delivery managers who want breached and at-risk SLAs across incidents, changes and problems in one view, by asking their AI assistant.

Try PopdockAI free
Get a live demo
ServiceNow SLA breach risk report
Which ServiceNow SLAs are breached or over 75 percent for the Service Desk group?
5 SLAs have breached and 12 are past 75 percent. - Next to breach: INC0012345, P2, in 40 minutes, Jordan Lee - Unassigned: 3 at-risk tasks have no assignee - Paused: 2 SLAs on hold, still shown - Most risk: Service Desk, 9 of the 17 Want the breached and at-risk tables?
ServiceNow
Sample figures. Your results come from your own account.
servicenow-get-task-sla
servicenow-get-incident
servicenow-get-change-request
servicenow-get-change-task
servicenow-get-problem
servicenow-get-problem-task

On this page

The problem

The problem

The prompt

Who it's for

How it works

Tools used

Connector

ServiceNow

ServiceNow
Run it on your own ServiceNow data.

Connect ServiceNow, pick your AI tool and paste the prompt.

Try PopdockAI free

The problem

SLA breaches spotted only after they happen

SLAs in ServiceNow sit on incidents, changes and problems, so seeing which are about to breach means opening each task type separately. By the time a breach shows on a dashboard, it is too late to act.

Without PopdockAI

  • Check SLAs on incidents, changes and problems separately
  • Work out who owns each at risk task
  • Notice the breach on a dashboard afterwards
  • Edit an SLA to make the number look better

With PopdockAI

  • Running SLAs past the threshold or breached are read
  • Each is traced to its incident, change, problem or task
  • Owner, group and unassigned tasks are shown
  • Read only, and SLAs are never edited

The prompt

Use this prompt

Copy it into any AI tool connected to PopdockAI. Swap the values in braces for your own.

Prompt
**Objective:** Report every running SLA that has breached or is at least `{threshold-percent}` percent (default 75) through its allowed time, optionally limited to incidents owned by `{assignment-group}`.

**Step 1: Pull the at-risk SLAs**

Call `servicenow-get-task-sla` with active true and actual-elapsed-percentage.min `{threshold-percent}` (75 if blank). Then call it again with active true and has-breached true, and merge the two sets by sys-id.

**Step 2: Identify the owning task**

The task field is a task number. Use its prefix to pick the read tool:

* INC: `servicenow-get-incident` with number
* CHG: `servicenow-get-change-request` with number
* CTASK: `servicenow-get-change-task` with number
* PRB: `servicenow-get-problem` with number
* PTASK: `servicenow-get-problem-task` with number

Record state, priority, assignment-group and assigned-to. If `{assignment-group}` is given, keep only tasks whose assignment-group matches it.

**Step 3: Report**

Two tables, Breached then At risk, each sorted by breach-time ascending: task number, task type, sla-definition, stage, actual-elapsed-percentage, breach-time, assignment-group, assigned-to. After the tables, list the tasks with no assigned-to, and name the assignment group carrying the most at-risk SLAs.

**Rules & Guidelines:**

* Read-only. Do not call `servicenow-update-task-sla`, `servicenow-add-task-sla`, `servicenow-update-incident` or any other add- or update- tool. SLAs are maintained by the SLA engine; editing them by hand hides the breach rather than fixing it.
* An SLA with stage Paused is still reported, marked Paused.

**Validation:**

* If nothing matches, say that no running SLA is at or above the threshold and stop.
* If a task number has a prefix not listed above, report it with its number only.

Who it's for

One answer, three teams that use it

Service desk managers

See what is about to breach

Get breached and at risk SLAs sorted by breach time with an owner for each.

Which ServiceNow SLAs are breached or over 80 percent right now?

Team leads

Protect your group's SLAs

Filter to your group and see unassigned tasks putting SLAs at risk.

Show at risk SLAs for the Network group, including tasks with no assignee.

IT operations managers

Know which team needs help

See which group carries the most SLA risk across task types.

Which group has the most at risk SLAs across incidents, changes and problems?

How it works

What PopdockAI does when you ask

You optionally set a threshold and a group, and your AI assistant lists the SLAs at risk with their owners. It never edits an SLA.

01

Ask

You optionally set a threshold, 75 percent by default, and a group.

Your AI tool

02

Read

It reads running SLAs that have breached or passed the threshold.

servicenow-get-task-sla

03

Trace

It reads the incident, change, problem or task each SLA belongs to.

servicenow-get-incident
servicenow-get-change-request
servicenow-get-change-task
servicenow-get-problem
servicenow-get-problem-task

04

Report

You get breached and at-risk tables by breach time and the group most at risk.

Your AI tool

What PopdockAI provides

The tools behind the answer

Ready made tools for ServiceNow and one secure connection to your AI tool. No code, no exports.

get-data

servicenow-get-task-sla

Returns the SLAs attached to tasks (stage, breach status, elapsed percentage and breach time) from ServiceNow. Filter by task, SLA definition, stage, whether it is active or breached, elapsed percentage and breach time range.
get-data

servicenow-get-incident

Returns incident records (number, state, priority, caller, assignment and dates) from ServiceNow. Filter by number, state, priority, caller, assignment group, assignee, short description text and opened date range.
get-data

servicenow-get-change-request

Returns change request records (type, state, risk, approval and planned window) from ServiceNow. Filter by number, type, state, risk, assignment group, assignee, short description text and planned start date range.
get-data

servicenow-get-change-task

Returns change task records, with the change request each belongs to, from ServiceNow. Filter by number, change request, type, state, assignment group, assignee, short description text and planned start date range.
get-data

servicenow-get-problem

Returns problem records (number, state, priority, known error, related incidents and dates) from ServiceNow. Filter by number, state, priority, known error, assignment group, assignee, short description text and opened date range.
get-data

servicenow-get-problem-task

Returns problem task records, with the problem each belongs to, from ServiceNow. Filter by number, problem, type, state, assignment group, assignee, short description text and opened date range.
Read only.Nothing in ServiceNow Changes

This report is built from Get data tools only. PopdockAI applies the row, field and parameter rules your admin sets, and every query is written to the audit trail.

How Popdock AI secures your data

The outcome

Act on SLAs while there is still time

Try PopdockAI free
Get a live demo

Related use cases

More ways to put this data to work

All Ramp use cases

One prompt template with infinite possibilities.

‍

Your AI assistant adapts its approach, tone, and capabilities to match each unique context while you maintain a single, manageable workflow.

Join forward-thinking companies that are transforming their operations with intelligent, secure AI automation.

Try PopdockAI Free
See Documentation