- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
yesterday
Hello,
I have to create a report showing the following:
1. Incidents that have been closed with a category of First Call Resolution
2. The number of redirects per incidents.
3. The origination of the incident.
4. If the incident was manually assigned or by predictive intelligence.
The screen shot below shows the additional filter conditions I entered so far, but I am not sure which filter conditions to choose to get the number of redirects per incidents and if the was manually assigned or by predictive intelligence. Any assistance is appreciated.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
yesterday
Hi Buddy,
You’ve got the right filters in place for identifying closed incidents with an FCR category — that part looks good.
Where it gets tricky is the rest of what you’re trying to report on, because those details aren’t stored as simple fields on the Incident record.
For redirects, there isn’t a direct “number of redirects” field. Redirects are really just assignment group changes, and those are tracked in the incident’s history/audit records. Because of that, you can’t get an accurate redirect count using Incident filters alone. To do this properly, you’d need to report off the assignment history (audit data) or use Performance Analytics to calculate reassignment counts per incident.
For the origination of the incident, that one’s much easier. You can typically use Contact type (portal, email, phone) and include it as a column or group by, depending on how you want to display it.
For manual vs Predictive Intelligence assignment, there also isn’t an out-of-the-box field that explicitly tells you how the assignment was done. ServiceNow doesn’t flag incidents as “assigned by PI” vs “manually assigned,” so this usually has to be inferred from timing and assignment history, or tracked via a custom field or rule if that distinction is important.
So in short, you’re not missing a filter — some of what you’re asking for simply isn’t available directly on the Incident table.
For a single clean report:
Keep your Incident report for:
Closed
Category = FCR
Assignment group not empty
Contact type (origination)
Then add:
A secondary report or drill-down for:
Assignment group changes (redirects)
Optional documentation explaining:
Predictive vs manual assignment determination is inferred, not explicit
@DeIvory Gordon - Please mark Accepted Solution and Thumbs Up if you found Helpful 🙂
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
yesterday
For 1st point : use OOTB
% First call resolution
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/dratulgrover [ Connect for 1-1 Session]
****************************************************************************************************************
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10 hours ago
Hello! Thank you for your reply, but I cannot open the link you sent me.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
yesterday
Hi Buddy,
You’ve got the right filters in place for identifying closed incidents with an FCR category — that part looks good.
Where it gets tricky is the rest of what you’re trying to report on, because those details aren’t stored as simple fields on the Incident record.
For redirects, there isn’t a direct “number of redirects” field. Redirects are really just assignment group changes, and those are tracked in the incident’s history/audit records. Because of that, you can’t get an accurate redirect count using Incident filters alone. To do this properly, you’d need to report off the assignment history (audit data) or use Performance Analytics to calculate reassignment counts per incident.
For the origination of the incident, that one’s much easier. You can typically use Contact type (portal, email, phone) and include it as a column or group by, depending on how you want to display it.
For manual vs Predictive Intelligence assignment, there also isn’t an out-of-the-box field that explicitly tells you how the assignment was done. ServiceNow doesn’t flag incidents as “assigned by PI” vs “manually assigned,” so this usually has to be inferred from timing and assignment history, or tracked via a custom field or rule if that distinction is important.
So in short, you’re not missing a filter — some of what you’re asking for simply isn’t available directly on the Incident table.
For a single clean report:
Keep your Incident report for:
Closed
Category = FCR
Assignment group not empty
Contact type (origination)
Then add:
A secondary report or drill-down for:
Assignment group changes (redirects)
Optional documentation explaining:
Predictive vs manual assignment determination is inferred, not explicit
@DeIvory Gordon - Please mark Accepted Solution and Thumbs Up if you found Helpful 🙂
