SkarpChapter 10 of 14
Key ITIL 4 Practices III: Service Desk, Request Management, and Support Practices
Step into the front line of IT support and see how service desks, request handling, and supporting practices work together to keep users productive.
Step 1: Where We Are In ITIL 4
Link to Earlier Modules
You have already seen core ITIL 4 practices like service level, incident, problem, change, release, deployment, and configuration. Now we add more high-yield operational practices.
New Focus Practices
This module focuses on three practices: service desk (user-facing front door), service request management (handling standard user requests), and monitoring and event management (watching services and reacting).
Exam Connection
A key exam trap is confusing incidents with service requests. All explanations here use ITIL 4’s current definitions, which you should apply in Foundation-level questions.
Step 2: Service Desk – Purpose and Key Characteristics
Service Desk Purpose
Service desk is a practice whose purpose is to capture demand for incident resolution and service requests, and to act as the single point of contact between users and the service provider.
Key Characteristics
It is a single point of contact, focused on communication and user experience, using multiple channels such as phone, email, chat, portal, and chatbots.
Modern Emphasis
Compared with older ITIL versions, ITIL 4 emphasizes value, experience, and collaboration over just logging calls. Automation and self-service are now central.
Step 3: Service Desk in Action – Channels and Scenarios
Service Desk Channels
Service desks use multiple channels: phone, email, self-service portal, chat/chatbots, and sometimes a walk-up bar. All of these are part of the service desk practice.
Typical Flow
The desk listens, records the contact, classifies it as incident or service request, resolves if possible or escalates, and keeps the user updated until closure.
Automation Still Counts
Chatbots and automated portals are still part of the service desk practice if they handle user contact and communication, even without a human agent.
Step 4: Service Request Management – What It Is (and Is Not)
Purpose of Service Request Management
This practice handles predefined, user-initiated requests in a standard, efficient, and user-friendly way, supporting the agreed quality of services.
What Counts as a Service Request
Typical service requests include access to existing apps, standard devices, approved software installs, or requests for information and advice.
Not Incident Management
Service requests are about getting something standard. If something is broken or not working as expected, that is an incident and belongs to incident management.
Step 5: Quick Sort – Incident or Service Request?
Decide for each scenario whether it is an incident or a service request in ITIL 4 terms. Think before you peek at the suggested answers.
- A user cannot log in because the authentication server is down.
- A new employee needs an email account and access to Teams.
- A student reports that Wi‑Fi has suddenly stopped working in one building.
- A lecturer asks for a new plugin to be added to an already-approved teaching tool.
- A researcher asks, "How do I set up multi-factor authentication on my phone?" and nothing is broken.
Think it through, then check:
- Incident – Something that used to work now fails.
- Service request – Standard onboarding access.
- Incident – Service disruption.
- Service request – If the plugin is in the approved catalog, this is a request; if not, it may trigger change enablement as well.
- Service request – Request for information; no failure has occurred.
Step 6: Monitoring and Event Management – The Early Warning System
Purpose of Monitoring and Event Management
This practice observes services and components, records events, and decides on appropriate responses. It is like an early warning system for IT services.
Monitoring and Events
Monitoring collects data. An event is a significant change of state. ITIL 4 commonly distinguishes informational, warning, and exception events.
Support to the Value Chain
Monitoring and event management supports Plan, Design & Transition, Obtain/Build, Deliver & Support, and Improve by providing data, alerts, and automated triggers.
Step 7: How These Practices Work Together
Story Setup
In a university email service, monitoring detects warning events and exception events. These events can create tickets before or after users are impacted.
During an Outage
When email goes down, monitoring creates an incident, on-call staff are paged, and the service desk handles user calls and portal contacts, linking them to a major incident.
Parallel Service Requests
At the same time, new staff may request email accounts via the portal. Those standard requests follow service request management workflows, independent of the outage fix.
Step 8: Identify the Practice
Match the description to the correct ITIL 4 practice: service desk, service request management, incident management, or monitoring and event management.
A tool detects that a web service is unreachable and automatically creates a ticket. Which practice is MOST directly described?
- Service desk
- Service request management
- Monitoring and event management
- Incident management
Show Answer
Answer: C) Monitoring and event management
Automatically detecting that a service is unreachable and creating a ticket is primarily monitoring and event management. Incident management will handle resolving the incident, and the service desk may communicate with users, but the key action described is automatic detection and ticket creation.
Step 9: Incident vs Service Request (Exam-Style)
Foundation exams love this distinction. Try this scenario.
A user submits a portal form asking for access to an existing CRM system, following a standard approval workflow. Nothing is broken. Which practice is MOST involved in fulfilling this?
- Incident management
- Service request management
- Problem management
- Monitoring and event management
Show Answer
Answer: B) Service request management
This is a predefined, user-initiated request for access to an existing service, with a standard workflow. That is exactly what service request management is for in ITIL 4.
Step 10: Flashcard Review
Use these flashcards to quickly review key ITIL 4 terms from this module.
- Service desk (purpose)
- To capture demand for incident resolution and service requests, and to be the single point of contact for the service provider and its users.
- Service request
- A user’s request for something that should normally be available, often pre-approved and handled via a standard workflow (request model).
- Service request management (purpose)
- To support the agreed quality of a service by handling all predefined, user-initiated service requests in an effective and user-friendly manner.
- Incident (ITIL 4)
- An unplanned interruption to a service, a reduction in the quality of a service, or a failure of a configuration item that has not yet impacted a service.
- Monitoring and event management (purpose)
- To observe services and service components, record and report events, and determine the appropriate response to those events.
- Event (ITIL 4)
- Any change of state that has significance for the management of a service or other configuration item.
- Exception event
- An event indicating that something has gone wrong, such as a service outage or a resource exceeding a defined threshold.
- Warning event
- An event signaling that a threshold is approaching and that action may be needed to prevent an incident.
- Informational event
- An event that records normal operation, such as a successful backup or a user login, usually requiring no action.
- Single point of contact (SPOC)
- The role of the service desk as the main channel through which users interact with the service provider for incidents and service requests.
Key Terms
- Event
- Any change of state that has significance for the management of a service or other configuration item.
- Incident
- An unplanned interruption to a service, a reduction in the quality of a service, or a failure of a configuration item that has not yet impacted a service.
- Service desk
- ITIL 4 practice whose purpose is to capture demand for incident resolution and service requests and to be the single point of contact for the service provider and its users.
- Warning event
- An event indicating that a threshold is approaching and that intervention may be needed to prevent an incident.
- Exception event
- An event indicating that a service or component is operating outside normal parameters, often meaning something has gone wrong.
- Service request
- A user’s request for something that should normally be available, often pre-approved and handled via a standard workflow.
- Incident management
- ITIL 4 practice focused on minimizing the negative impact of incidents by restoring normal service operation as quickly as possible.
- Informational event
- An event that indicates normal operation and usually requires no action, such as a successful backup.
- Service request management
- ITIL 4 practice that handles all predefined, user-initiated service requests in an effective and user-friendly manner.
- Single point of contact (SPOC)
- The main channel through which users interact with the service provider, usually implemented via the service desk practice.
- Monitoring and event management
- ITIL 4 practice that observes services and components, records and reports events, and determines the appropriate response.