ServiceNow Incident Management Interview Questions 2026
What is an incident? explain few examples which can be considered as Incident?
An incident is an unplanned interruption to a service, or reduction in the quality of a service.
Below are some common issues which can be considered as Incidents :
1. Outlook is not working : Not able to recieve/send an email.
2. Printer is not working.
3. VDI is running very slow.
What is primary goal of Incident Management?
Incident Management restores normal service operation while minimizing impact to business operations and maintaining quality.
What is difference between incident, major incident and security incident?
Major Incident : A major incident (MI) is an incident that results in significant disruption to the business and demands a response beyond the routine Incident Management.
Incident : An incident is an unplanned interruption to a service, or reduction in the quality of a service. We could say it has less impact or urgency as compare to Major Incident.
Security Incident : An Incident which is related to security of an Organisation can be considered as Security Incident. Example : Phishing attack email - > When you report phishing emails, many organisation automate to generate Security Incident in the backend.
What are the main stages of the incident management process?
The goal of Incident Management is to restore normal service as quickly as possible. In ServiceNow the process follows these stages:
1. Identification and logging: the incident is reported through the Service Portal, email, phone, chat or Virtual Agent, or raised automatically by monitoring (event management). An incident record is created with the caller, short description and affected service or CI.
2. Categorization: category and subcategory are set (for example Network, VPN). They drive reporting, routing and the knowledge suggested to the agent.
3. Prioritization: Impact and Urgency are set, and ServiceNow calculates Priority from the priority matrix (for example High impact and High urgency gives P1). Priority decides the SLA and how fast the incident must be handled.
4. Assignment: the incident is assigned to the right support group, manually or through assignment rules or predictive routing, often based on category, CI or location.
5. Investigation and diagnosis: the assigned agent (state In Progress) investigates, checks knowledge articles and known errors, and applies a fix or a workaround. If the agent is waiting on the caller, a vendor or a change, the incident goes On Hold with a reason, which pauses the SLA.
6. Escalation: if it can't be solved at this level, it is escalated functionally (to a more specialised team such as L2 or L3) or hierarchically (to management, for example a P1 or an SLA about to breach). A critical outage can be promoted to a major incident with its own communication process.
7. Resolution: once service is restored, the incident is set to Resolved with resolution code and resolution notes, and the caller is notified.
8. Closure: the caller can confirm or reopen it. If nobody reopens it, the incident closes automatically after a set period (by default a few days) and becomes read only. If the same issue keeps coming back, a problem record is raised to find the root cause.
ServiceNow incident states: New (1), In Progress (2), On Hold (3), Resolved (6), Closed (7), Canceled (8).
Note: In the interview, separate the two goals: Incident Management restores service fast, even with a workaround, while Problem Management removes the root cause. Mentioning On Hold pausing the SLA and the automatic closure after resolution shows hands-on experience.
How to associate multiple Business Services or CI's to one incident?
When you populate the ‘Business Service’ and the ‘Configuration Item’ fields on the incident form and save the record, the selected values appear on the “Impacted Services/CIs” and “Affected CIs” related lists respectively.
If we want to add multiple affected CIs or impacted services, we can do it by adding multiple records in related lists.
How to close incident after 3 days of resolution?
OOTB there is system property "Number of days (integer)", this property stores integer value, based on the value resolved incidents are automatically closed after those many days. We can set this property value to 3 to close it after 3 days of resolution.
There is OOTB scheduled job "Autoclose Incidents" which runs every hour and uses this property to auto close resolved incidents.
What is Urgency and Impact in Incident Management, how it is measured?
Impact is a measure of the extent of the issue and of the potential damage caused by the incident before it can be resolved. This can be based on several factors including the number of affected users, potential financial losses, and criticality of affected services.
Urgency is a measure of the business criticality of an incident, when there is an effect upon business deadlines. The urgency reflects the time available to restore service before the impact is felt by the business.
How is the Priority of an Incident populated in ServiceNow? Explain Impact, Urgency, the priority matrix and where it is stored.
On the incident form, Priority is read-only by default. Agents don't pick it: ServiceNow calculates it from two fields they do set.
Impact: how widely the business is affected, for example one user, a department or the whole company. Values: 1 - High, 2 - Medium, 3 - Low.
Urgency: how quickly it needs to be fixed, for example whether there is a workaround or a business deadline. Values: 1 - High, 2 - Medium, 3 - Low.
Priority is the result: 1 - Critical, 2 - High, 3 - Moderate, 4 - Low, 5 - Planning. The base system uses this 3 x 3 matrix:
| Impact \ Urgency | 1 - High | 2 - Medium | 3 - Low |
|---|---|---|---|
| 1 - High | 1 - Critical | 2 - High | 3 - Moderate |
| 2 - Medium | 2 - High | 3 - Moderate | 4 - Low |
| 3 - Low | 3 - Moderate | 4 - Low | 5 - Planning |
Where the matrix is stored: in a Data Lookup table, not in code. The rows live in the dl_u_priority table (System Policy > Rules > Priority Lookup Rules), one row per Impact and Urgency combination with its resulting Priority. A Data Lookup Definition on the incident table matches the incident's Impact and Urgency against those rows and writes the Priority.
When it runs: the definition can run on form change (Priority updates as soon as the agent changes Impact or Urgency) and on insert and update on the server, so incidents created by email, imports, REST or scripts get the right Priority as well.
Changing the matrix: edit the rows in dl_u_priority, for example so that Medium Impact with High Urgency becomes Critical for your organisation. No Client Script or Business Rule is needed, and the rule then applies everywhere incidents are created.
Changing an incident's priority: change its Impact or Urgency, not Priority directly. In scripts, set impact and urgency for the same reason, otherwise the lookup can recalculate Priority and overwrite your value.
Why it matters: Priority drives the SLA that attaches, the response and resolution targets, assignment and escalation, notifications, and whether the incident becomes a major incident candidate.
Note: A strong answer names the dl_u_priority Data Lookup and explains why Priority is calculated instead of chosen: it stops everyone from marking their own ticket as Critical and keeps priorities consistent across the service desk.
When should we raise an Incident vs. a Request?
Raise an incident when there is any unplanned interruption or degradation in the quality of an existing IT service and create a request when you want to put a formal request to the IT service desk to provide something. A request can be for a new hardware or application, information, training etc.
Example: If the existing RAM in your system is malfunctioning, then raise an incident but if you want a new RAM for your system, raise a request.
Incident Requests are requests that denote the failure or degradation of an IT service. For example, unable to print, unable to fetch mails and so on.
Service Requests on the other hand are requests raised by the user for support, delivery, information, advice or documentation. Some examples are installing software in workstations, resetting lost password, requesting for hardware device and so on.
Interviewers forget your perfect answer in 5 minutes. They remember how confidently you delivered it.
Confidence comes from repetition, not luck. The Job Switch Kit is where you build it.
🔒 Secure payment via Razorpay · Instant access after payment
Real Interview Questions & Answers
Questions shared by ServiceNow professionals and reviewed for clarity, relevance, and interview usefulness.
🚀 Power Up Your ServiceNow Career
Join a growing community of smart ServiceNow professionals to stay ahead in interviews, sharpen your development skills, and accelerate your career.