Issue Auto Resolution diagnostic chat
Summarize
Summary of Issue Auto Resolution Diagnostic Chat
The Issue Auto Resolution diagnostic chat feature allows admin users to troubleshoot and resolve issues related to the functionality of the Issue Auto Resolution tool within ServiceNow's AI Platform. It enables a structured conversation to identify and resolve problems when incidents or cases do not behave as expected.
Show less
Key Features
- Enabling Diagnostic Chat: Admin users must update specific Restricted Caller access records to Allowed in the Restricted Caller Access Privileges table to enable the diagnostic tool.
- Conversation Flows: Admin users can initiate a chat by entering "IAR" and selecting from two main issues: incidents or cases not being assigned to the bot user or not progressing through Issue Auto Resolution.
- Diagnostic Analysis: The tool conducts health checks on configurations, ensuring that the prediction server is operational and configurations are active.
- Detailed Checks: For incidents, the tool verifies configuration activity, language settings, response channels, and intent topic maps. For cases, it checks AI Search activation.
- Further Analysis: If initial checks do not resolve the issue, users can enter the incident or case number for deeper analysis of trigger conditions and business rules.
Key Outcomes
By using the Issue Auto Resolution diagnostic chat, ServiceNow customers can quickly identify and address configuration issues, ensuring that the auto-resolution process operates effectively. This tool enhances operational efficiency and improves incident management by providing actionable insights and solutions during troubleshooting.
Admin users can initiate a chat conversation to troubleshoot the settings and functionality of Issue Auto Resolution if an issue arises that wasn't addressed as expected.
Enabling diagnostic chat
To enable the Issue Auto Resolution diagnostic tool, an admin user must set certain Restricted Caller access records to Allowed on the Restricted Caller Access Privileges table.
- Navigate to .
- Filter the records by
Source=76fec17dc0e1d5d0f877e9d0ea777a12(Script Include: IARIssueNotAssignedDiagnostic). - Navigate to each record and change the status to Allowed.
Diagnostic conversation flows
- An Incident or case isn’t getting assigned to the Bot user.
- An Incident or case isn’t going through Issue Auto Resolution.
Conversation flow: Incident or HR case is not getting assigned to bot user
- Confirm your selection, return to search, or search KB articles.
- Select the type of case or Incident with which you need help, or choose to search all Issue Auto Resolution configurations.
- The diagnostic tool performs an analysis on Issue Auto Resolution configuration and settings and displays the results. The diagnostic confirms the following conditions:
- The prediction server is up.
- There are existing Issue Auto Resolution configurations.
- The configurations are active.
A health check for the selected configuration type also runs to determine if the Incident or case is properly configured for Issue Auto Resolution. The diagnostic for an Incident checks the following conditions:- Issue Auto Resolution configuration is active.
- Language configuration is active.
- There is an active response channel.
- There is an active intent topic map for the Incident configuration.
- Enter the Incident or case number and confirm it’s correct.
The bot asks you to confirm the number you entered.
- The diagnostic tool analyzes the issue to determine if the following conditions are met:
- The trigger condition on the configuration matches the Incident or case values.
- The business rule order is the highest.
- There’s only one trigger business rule for Issue Auto Resolution on the Incident or case table and it’s active.
Conversation flow: An Incident or case is not going through Issue Auto Resolution
- Confirm your choice to proceed diagnosing a functionality issue with Issue Auto Resolution.
- The diagnostic tool checks the following conditions:
- The intent prediction was successful (Incidents only).
- The criticality is correct and AI Search is active (cases only).
- A notification was sent.
- The end user responded to the notification.
If any of these checks reveal an issue, the diagnostic tool displays a possible solution. Indicate whether these solutions resolved the issue, or choose to perform further analysis.