Which of these is/are TRUE? 1. Functional escalation is an essential part of the Incident Management process 2. All calls to the Service Desk should…

Statement 1 is true because functional escalation is a fundamental component of the Incident Management process. It ensures that an incident is passed to a team with the appropriate technical skills when the initial support level cannot resolve it, thereby facilitating a timely restoration of service. Statement 3 is also true as a primary function of the Service Desk is to act as the single point of contact for users. This includes fulfilling routine, pre-approved Service Requests like password resets or software access, which are distinct from incidents. Statement 2 is false because the Service Desk handles various types of user interactions, including service requests and general inquiries, not just incidents (unplanned service interruptions).

B. All three of them: This is incorrect because statement 2 is false. Not all contacts with a Service Desk are classified as incidents.

C. Only 1: This is incorrect because statement 3 is also a true and standard practice in service management.

D. 1 and 2: This is incorrect because statement 2 is false; conflating all user contacts as incidents is a procedural error.

1. AXELOS. (2019). ITIL® Foundation: ITIL 4 Edition. TSO (The Stationery Office).

Section 5.2.5, Incident Management: This section details the purpose of incident management, which includes resolving incidents efficiently. It implicitly and explicitly covers the need for escalation paths (both functional and hierarchical) to route incidents to the correct resolution group.

Section 5.2.14, Service Desk: This practice is described as the entry point and single point of contact for the service provider with all of its users. It clarifies that the service desk handles both incidents and service requests.

Section 5.2.16, Service Request Management: This section defines service requests and notes that simpler requests are often fulfilled by the service desk team directly.

2. University of Washington. (n.d.). ITIL Key Concepts: Incident vs. Service Request. UW-IT, IT Connect. Retrieved from https://itconnect.uw.edu/work/services-and-processes/itil/itil-key-concepts-incident-vs-service-request/

This university documentation clearly distinguishes between an incident ("something is broken") and a service request ("a request for something new or different"). It supports the reasoning that not all calls are incidents (refuting statement 2) and that service requests are a distinct category of work handled by IT support (supporting statement 3).

3. Iden, J., & Langeland, L. (2010). Setting the stage for a successful ITIL adoption. International Journal of Information Management, 30(1), 69-77. https://doi.org/10.1016/j.ijinfomgt.2009.09.001

This academic paper discusses the implementation of ITIL processes. It reinforces the distinct nature and purpose of Incident Management and Request Fulfillment, highlighting that a Service Desk is structured to handle both types of user interactions, which aligns with the correct answer.