How to Resolve and Close an Incident in ServiceNow
Recommended Learning Path
Resolve and Close an Incident in ServiceNow
resolve incident servicenow
Table of Contents
Resolving an Incident is not simply changing its State.
Before an Incident should be completed, the support team needs to confirm that the affected service is working again, document what fixed the issue, select the appropriate resolution information, and make sure the record contains enough detail for future reference.
If you are learning how to resolve incident ServiceNow records correctly, understanding the difference between Resolved and Closed is especially important.
Quick Answer: How Do You Resolve an Incident in ServiceNow?
The basic process is:
Open Incident → Verify Fix → Complete Resolution Information → Resolve → Validate → Close
In ServiceNow’s current documented workflow, an agent opens the Incident, completes the Resolution Information section, and selects Resolve. The Incident then enters the Resolved state. Closure can follow according to the organisation’s permissions and configuration.
What Is the Difference Between Resolved and Closed?
These states are related but not identical.
State | Meaning |
Resolved | A satisfactory solution has been provided |
Closed | The Incident lifecycle has been completed after resolution |
ServiceNow’s Incident state model places Resolved before Closed. A Resolved Incident may remain in that state for a configured period before being closed automatically.
This gives users and support teams an opportunity to confirm that the solution actually worked before the record becomes fully closed.
Start Your ServiceNow Learning Journey
Step 1: Open the Incident
For the documented standard interface flow, navigate to:
All → Incident → Open
Open the Incident you want to resolve.
Before changing the State, review the Incident history.
Check:
- Short Description
- Description
- Caller
- Assignment Group
- Assigned To
- Work Notes
- related Problem or Change records
- troubleshooting already completed
This helps ensure you are resolving the correct issue for the correct reason.
Step 2: Verify That the Service Is Restored
Do not mark an Incident Resolved simply because a technical action was performed.
Verify the outcome.
For example, if the issue was:
“Employee cannot connect to corporate VPN.”
and you reset the VPN profile, test whether the employee can now connect successfully.
A useful distinction is:
Action completed: VPN profile reset.
Outcome verified: User successfully connected to VPN.
The second statement provides better evidence that the Incident can actually move toward resolution.
Step 3: Complete the Resolution Information
ServiceNow’s current Incident resolution workflow includes a Resolution Information section.
Important information includes:
- Resolution Code
- Resolution Notes
- Resolved By
- Resolved date/time
ServiceNow describes Resolution Code as information used to categorize resolved cases and Resolution Notes as documentation of how the Incident was resolved.
Some fields may be populated automatically depending on your instance configuration.
Step 4: Select the Correct Resolution Code
The Resolution Code explains the general type of resolution.
The available values can depend on your ServiceNow configuration and implementation.
The important learning point is not to select a random value simply because the field is mandatory.
The code should accurately describe how the Incident reached resolution.
For example, an organisation may distinguish between situations such as a solution being provided, a known error being used, or another related process resolving the issue.
Always follow the values configured in your training or production instance.
Step 5: Write Clear Resolution Notes
Good Resolution Notes should answer:
What was wrong?
What action was taken?
What was the final result?
For example:
User could not connect to the corporate VPN because the local VPN profile was corrupted. The existing profile was removed and recreated. User tested the connection successfully and confirmed access to internal applications.
A weak Resolution Note would be:
Fixed.
That tells future support agents almost nothing.
Useful Resolution Notes improve the historical value of the Incident record.
Step 6: Move the Incident to Resolved
Once the service is restored and the resolution information is complete, select Resolve in the documented standard workflow.
ServiceNow then moves the Incident into the Resolved state.
At this point, the Incident is not necessarily permanently closed.
That distinction matters because the resolution may still need confirmation.
Step 7: Validate the Resolved Incident
After resolving the Incident, reopen or refresh the record.
Verify that:
- State shows Resolved
- Resolution Code is correct
- Resolution Notes were saved
- Resolved By information is appropriate
- Resolved date/time was recorded
- related Work Notes remain available
- any Problem or Change relationship is correct
If your instance uses notifications, SLAs, Business Rules, Flows, or customer confirmation, verify that those processes also behaved as expected.
This is especially important in training because administrators can customize ServiceNow behaviour.
Step 8: Understand Incident Closure
ServiceNow’s current documentation allows the Incident to move from Resolved to Closed through the configured closure process.
The standard documentation also provides a Close Incident action for users with the required permissions.
However, many organisations do not close Incidents immediately.
A Resolved Incident may remain available for user confirmation first.
ServiceNow also supports automatic closure after a configurable number of days. Administrators can determine the auto-close period through Incident properties.
Therefore, beginners should not assume:
Resolved = automatically Closed immediately.
The actual timing depends on instance configuration.
What Happens If the User Says the Issue Is Not Fixed?
A Resolved Incident may need to return to active investigation.
In Service Operations Workspace, ServiceNow currently provides a Reopen option for Resolved Incidents when the appropriate access conditions are met.
When reopened, the Incident returns to In Progress.
This is useful when the fix appears successful initially but the problem returns.
For example:
Resolution: VPN profile recreated.
User response: Connection failed again after ten minutes.
That Incident may need to be reopened rather than treated as successfully completed.
Can a Closed Incident Be Reopened?
ServiceNow’s current Service Operations Workspace documentation states that a Closed Incident cannot be reopened using the normal Reopen action.
In supported notification workflows, replying to a resolution message after closure can result in a new Incident being created with selected information copied from the closed record.
This reinforces why validation during the Resolved stage is valuable.
Practical Example: Resolving a VPN Incident
Suppose an Incident contains:
Short Description: Unable to connect to corporate VPN
Assignment Group: Network Support
Assigned To: Ravi
The agent investigates and finds that the VPN profile is corrupted.
The profile is deleted and recreated.
The user connects successfully and verifies access to internal applications.
The agent records Resolution Notes such as:
“VPN profile corruption identified. Existing profile removed and recreated. User successfully connected to VPN and confirmed access to internal services.”
The correct Resolution Code is selected according to the organisation’s configured options.
The agent selects Resolve.
The record is then checked to confirm:
State: Resolved
Resolution information: Complete
User access: Verified
The Incident can later move to Closed according to the organisation’s closure workflow.
Get Ready to Crack ServiceNow Interviews
Explore the ServiceNow Interview Guide
Common Resolution and Closure Mistakes
One common mistake is resolving an Incident without verifying the user’s service.
Another is writing vague Resolution Notes such as “completed” or “fixed.”
Avoid selecting a Resolution Code that does not match what actually happened.
Do not confuse a workaround with confirmation that the underlying technical cause has been permanently eliminated. If recurring investigation is required, a related Problem may be more appropriate.
Finally, do not assume every ServiceNow instance closes Incidents the same way. Auto-close periods, mandatory fields, roles, Business Rules, and workflows can all be configured.
Build Your Learning Plan Around Practice
Practise the complete lifecycle instead of learning resolution separately.
Start with:
Create → Assign → Investigate → Resolve → Validate
Then practise a second scenario where the user says the issue still exists.
Use:
Resolve → Reopen → Investigate → Resolve Again
Finally, test how your training instance moves a Resolved Incident to Closed.
The current FLM ServiceNow training includes Incident Management lifecycle practice using forms, UI Policies, Business Rules, and workflow customization.
FLM Perspective: Resolve with Evidence
Use this simple framework:
Fix → Test → Explain → Resolve → Confirm
Fix: What action corrected the issue?
Test: Did the service actually work afterwards?
Explain: Are the Resolution Notes clear?
Resolve: Is the record ready for Resolved status?
Confirm: Did the workflow, fields, and user outcome behave correctly?
This prevents Incident resolution from becoming a simple status-change exercise.
Related Career Guides
- How to Create an Incident in ServiceNow Step by Step
- How to Assign and Reassign Incidents in ServiceNow
- What Is Incident Management in ServiceNow?
- What Is Problem Management in ServiceNow?
- What Is Change Management in ServiceNow?
Conclusion
Resolving an Incident in ServiceNow means more than changing its State.
First confirm that the service has actually been restored. Then document the solution with the appropriate Resolution Code and useful Resolution Notes. Move the Incident to Resolved and verify the saved information and workflow behaviour.
Closure comes after resolution and may happen manually or automatically depending on the organisation’s ServiceNow configuration.
Learning this final stage correctly helps beginners understand the complete Incident lifecycle from creation through closure.
Frequently Asked Questions
1. How do I resolve an Incident in ServiceNow?
A. Open the Incident, complete the Resolution Information section, verify that the service has been restored, and select Resolve in the documented standard workflow.
2. What are Resolution Notes?
A. Resolution Notes document how the Incident was resolved and should explain the action taken and final outcome.
3. What is a Resolution Code?
A. It categorizes the way the Incident was resolved. The available values may depend on the organisation’s configuration.
4. What is the difference between Resolved and Closed?
A. Resolved means a satisfactory fix has been provided. Closed is the later lifecycle state after the resolution has been confirmed or the configured closure process has completed.
5. Does ServiceNow automatically close Resolved Incidents?
A. It can. ServiceNow provides configurable Incident auto-close settings that determine how many days a Resolved Incident remains open before automatic closure.
6. Can a Resolved Incident be reopened?
A. Yes. Service Operations Workspace provides a Reopen action for eligible Resolved Incidents, returning them to In Progress.
7. Can a Closed Incident be reopened?
A. ServiceNow’s current SOW documentation states that Closed Incidents cannot be reopened through the normal Reopen action.
8. What should I check before resolving an Incident?
A. Verify that the service works, troubleshooting is complete, the Resolution Code is appropriate, Resolution Notes explain the fix, and any relevant related records are updated.
Build Your Career in ServiceNow