Study guide, not an experience claim. I wrote these notes while studying this tool for IT support and service desk work. I have not administered it in production. Everything here is summarized in my own words from public documentation and lab-style thinking. Confirm details in the current official documentation, because these products change often.
What it is
ServiceNow is a cloud platform widely used for IT service management (ITSM). The service desk uses it to log, route, track and close work: incidents (something is broken), requests (someone needs something), problems (the root cause behind repeated incidents) and changes (planned modifications). It also hosts the knowledge base and the self-service portal. The ideas below come from ITIL-style practice and apply to other ticket tools as well.
Why organizations use it
- One record of every issue, so nothing is lost in email or chat.
- Routing to the right assignment group automatically.
- SLAs and priority make response times measurable.
- Reporting shows trends, e.g. the same printer failing every week → a problem record.
- Knowledge articles let users and new staff solve common issues.
How it works
The incident lifecycle:
Priority example
| High urgency | Low urgency | |
|---|---|---|
| High impact (department down) | P1 Critical | P2 High |
| Low impact (one user) | P3 Moderate | P4 Low |
An example matrix only; every organization defines its own.
Common service desk tasks
- Log and categorize tickets from calls, emails and walk-ups.
- Fulfill catalog requests (new account, software, hardware) following approvals.
- Write clear work notes so anyone can pick up the ticket.
- Escalate to tier 2 with evidence; keep the user informed.
- Search and suggest knowledge articles; flag outdated ones.
Writing a good ticket
- Summary line:
Outlook prompts for password – single user – Finance. - Who/where: user, location, device name, contact method.
- What exactly: error text, screenshot, when it started, what changed.
- Impact: how many users, can they work?
- Steps taken and their result, in order.
- Next action and who owns it.
Glossary
- Incident
- Unplanned interruption or reduction in service quality.
- Service request
- A standard request, e.g. access or software.
- Problem
- The underlying cause of one or more incidents.
- Change
- A planned modification, reviewed for risk.
- SLA
- Agreed target time to respond or resolve.
- Assignment group
- Team responsible for a ticket.
- KB article
- Documented solution or how-to.
- CMDB
- Database of configuration items such as servers and apps.