IT Service Management (ITSM) and ITIL: A Practical Introduction

IT Service Management (ITSM) is the discipline of designing, delivering, managing, and improving the IT services an organisation provides to its users and customers. Rather than viewing IT as a collection of hardware, software, and networks, ITSM treats IT as a set of services — email, printing, ERP access, network connectivity — each with defined service levels, support processes, and continuous improvement goals. This service-oriented mindset shifts the focus from technology components to business outcomes, which is exactly the language that clients want to hear from their MSP.

ITSM encompasses a wide range of processes, but the core ones that most MSPs interact with daily include incident management, problem management, change management, service request management, and asset or configuration management. Each process has defined inputs, activities, outputs, and roles. When these processes are well-implemented and supported by appropriate tooling, the result is a service desk that resolves issues faster, communicates more transparently, and continuously reduces the volume of recurring problems.

ITIL (Information Technology Infrastructure Library) is the most widely adopted framework for ITSM globally. Originally developed by the UK government in the 1980s and now managed by PeopleCert on behalf of Axelos, ITIL provides a structured set of best practices, processes, and terminology that organisations can adopt and adapt. The current version, ITIL 4, was released in 2019 and represents a significant evolution from the process-heavy ITIL v3. ITIL 4 introduces a more flexible, value-driven approach that incorporates concepts from Lean, Agile, and DevOps alongside traditional service management practices.

ITIL 4 is built around the Service Value System (SVS), which describes how all the components and activities of an organisation work together to create value. At the centre of the SVS is the Service Value Chain — six activities (plan, improve, engage, design and transition, obtain/build, deliver and support) that can be combined in flexible sequences called value streams. Rather than prescribing a rigid process flow, ITIL 4 encourages organisations to design value streams that fit their specific context. This flexibility makes ITIL 4 practical for MSPs of all sizes, from two-person shops to large national providers.

An incident is an unplanned interruption to a service or a reduction in the quality of a service. A printer that stops working, an email server that goes offline, or a VPN that drops connections are all incidents. The goal of incident management is to restore normal service operation as quickly as possible while minimising impact on the business. Key activities include logging the incident, categorising and prioritising it based on urgency and impact, assigning it to the appropriate resolver group, escalating if necessary, resolving the issue, and confirming resolution with the affected user. Effective incident management relies on clear priority matrices, defined escalation paths, and SLA targets for response and resolution times.

While incident management focuses on restoring service quickly, problem management focuses on identifying and eliminating the root cause of incidents so they do not recur. A problem is the underlying cause of one or more incidents. For example, if a client experiences repeated printer failures, the incident management process fixes each occurrence, but problem management investigates why the printer keeps failing — perhaps a faulty network port, an incompatible driver, or an overloaded print server. Problem management has two modes: reactive (triggered by recurring incidents) and proactive (triggered by trend analysis, monitoring alerts, or vendor advisories). The output is typically a known error record that documents the root cause and a workaround or permanent fix.

Change management (called "change enablement" in ITIL 4) controls the lifecycle of all changes to the IT environment — from deploying a new application to patching a firewall or migrating a mailbox. The purpose is to maximise the number of successful changes while minimising risk and disruption. Changes are typically classified as standard (pre-approved, low-risk, routine), normal (requires assessment and approval), or emergency (must be implemented immediately to restore service). A Change Advisory Board (CAB) reviews normal changes, assesses risk, and approves or rejects them. For MSPs, a lightweight CAB process — even a weekly 15-minute call — dramatically reduces the number of changes that cause unplanned outages.

ServiceNow is the dominant ITSM platform in the enterprise market and is increasingly adopted by large MSPs. Its strength lies in its comprehensive coverage of ITIL processes, powerful workflow automation (Flow Designer), and a vast ecosystem of integrations and applications on the ServiceNow Store. However, ServiceNow's complexity and cost make it a poor fit for smaller MSPs. Implementation typically requires dedicated ServiceNow administrators, and licensing is priced at the enterprise level. For MSPs managing large, complex client environments with hundreds of technicians, the investment can be justified by the operational efficiency gains.

Freshservice by Freshworks offers a more accessible entry point for SMB and mid-market MSPs. It provides ITIL-aligned incident, problem, change, and asset management out of the box, with a clean user interface that requires minimal training. The built-in workflow automator allows non-developers to create automation rules using a visual drag-and-drop editor. Freshservice integrates with popular RMM tools and offers a self-service portal that clients can brand as their own. Pricing is per agent per month on a tiered plan, making costs predictable and scalable.

HaloPSA (formerly Halo Service Solutions) is built specifically for MSPs and IT service providers. It combines ITSM capabilities with Professional Services Automation (PSA) features — contracts, SLA management, time tracking, billing, and project management — in a single platform. This eliminates the need to integrate a separate PSA tool with the service desk. HaloPSA supports ITIL-aligned processes and offers native integrations with Datto RMM, N-able, ConnectWise Automate, and other popular RMM products. For Australian MSPs looking for an all-in-one service management and billing platform, HaloPSA is a strong contender.

MSPs face unique ITSM challenges that differ from internal IT departments. An MSP manages multiple client environments, each with its own SLAs, escalation contacts, and technology stacks. The ITSM platform must support multi-tenancy — the ability to segregate data, workflows, and reporting by client — without creating unmanageable administrative overhead. SLA management must be granular enough to track different response and resolution targets for different clients and priority levels. Reporting must provide both client-facing metrics (SLA compliance, ticket volumes, resolution times) and internal metrics (technician utilisation, first-call resolution rate, backlog trends).

Adopting ITSM does not require implementing every ITIL practice on day one. Start with the three processes that deliver the most immediate value: incident management (to ensure consistent logging and prioritisation), change management (to reduce self-inflicted outages), and service request management (to separate requests from incidents and route them efficiently). Once these are stable, layer on problem management and knowledge management. This incremental approach avoids the common pitfall of over-engineering processes that technicians will resist or bypass.