
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-24-2019 06:44 AM
we have contextual search enabled on our Service Portal "report an issue" incident record producer. Is there something OOB that will track/measure incident deflection. we would like to know how many users went to the record producer (in service portal) to report an incident and got presented with a Knowledge Article that possibly helped them and ended up in NOT reporting an issue. I am not sure if there is something OOB that can provide this metric.
Solved! Go to Solution.
- Labels:
-
Incident Management
- 4,036 Views

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-20-2020 08:18 AM
I did more research on this and I found the solution that can help track deflection from the Report and issue record producer based on the contextual search macro inside the widget (ex. search results that the end user will be presented with):
OOB tables that track Session/User/Article deflection from record producer:
- cxs_relevant_doc_task
- Relevant Document [cxs_relevant_doc]
- Relevant Document Detail [cxs_rel_doc_detail]
Tables will provide data point for deflection success Knowledge Articles relevance.
I sort of answered my own question but if this helps you, mark this as correct Answer 🙂
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-14-2024 02:15 AM
Here is mine follow up question, I wanna make report in HRSD, On the ESC portal, to make report on user satisfaction
1) By viewing which KB article, which HR case has been raised?
2) KB articles viewed but still HR case has been raised?
Please help me with this. Is it possible?
Thanks.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-07-2024 02:27 AM
Hi @SagarBhadke , I think that should be doable. See my blog for more details about the table structure and data in it: How to report on Contextual Search usage .
To know which KB Articles were viewed before the HR Case has been raised:
- Relevant Document.Relevant to - this stores the HR Case
- Relevant Doc Detail.Relevant document - stores the KB article (or Catalog item)
- Relevant Doc Detail.Relevancy type - stores the action - you focus here on "Preview"
--> so you can build a report on "Relevant Doc Detail" where "Relevancy type" is "Preview", "Relevant doc table" is "KB Article" and "Relevant Document.Source doc table" is HR Case table(s). Then in the list report you can add needed columns, and you would see exactly which articles were previewed for which HR case.
I hope this helps.
Dominik
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-15-2021 02:48 PM
this is very helpful. but any chance that you get this reported out? I looking for a similar report. but not sure how to merge these tables and take them out. any help will be highly appreciable.
PaulSylo
Kindly mark "helpful", if this helps, or Mark as "Accepted " if it solves your issues !
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-08-2024 01:04 AM
In case it helps anybody, I was also interested in reporting on contextual search usage, and I wrote a blog about my findings How to report on Contextual Search usage .
There is a lot of interesting data there stored and incident deflection can be measured roughly by finding all records in "cxs_relevant_doc" displayed in a record producer (if end users use record producer to raise an incident) where there is no "relevant_to" value as it means no incident got created by that session. Obviously, it might mean also that the user simply left the form, so there might be false positives. For more precise measurement, you could report on "cxs_relevant_doc" records that have only "cxs_rel_doc_detail" records of "relevance" of "This helped" without incident created at the end ("relevant_to" is empty).