Service Request Management
Service request management is the practice of receiving, tracking, approving, and fulfilling predefined user requests for services, information, access, or equipment. It turns repeatable needs into visible workflows with clear ownership, status, and completion criteria.
itIT service management and support | OpenSkills.info
Course pathWalk it in order
Look it upDip in anytime
Go furtherLeaves this page
Don't Panic
Don't Panic - Service Request Management
Service request management handles predefined, user-initiated requests for services, information, access, or resources. A request might ask for a software license, a new device, access to a shared system, or an answer that is not already available through self-service. The practice gives each request a known path from intake to fulfillment while keeping the requester informed.
Predefined is the boundary that matters. A service provider designs a request offering before users need it. The offering states what can be requested, who may request it, what information is required, which approvals apply, who fulfills it, and what completion means. The submitted request is one instance of that design.
A service request is not an incident merely because both arrive at the service desk. An incident reports an unplanned interruption or reduction in service quality. A request asks for something to be provided. Mixing those queues hides fulfillment targets inside restore metrics and delays true outages. Classify at intake against the catalog.
A durable path looks like intake through a portal or channel, validation of required data, approvals where needed, fulfillment by the owning team, notification to the requester, and closure only when the outcome is delivered. Self-service and knowledge articles reduce volume when they actually answer the question. Metrics should include time to fulfill, reopen rate, and aging in approval states, not only ticket volume closed.
Read the Intro for the offering-versus-instance model. Use the Cheatsheet when you need the path and classification map. Landscape places service desks and ITSM platforms beside each other; Updates tracks the ITIL 4 Service Request Management practice overview this course uses as the practice scope.
Where this skill leads
Relevant careers
See how this topic contributes to broader role-level skill maps.
Sources
- https://www.peoplecert.org/browse-certifications/it-governance-and-service-management/ITIL-1/itil4-practices-service-request-management-3690
Supports
- Official purpose of handling predefined, user-initiated requests in an effective and user-friendly manner
- Practice concepts, processes, roles, information, partners, success factors, metrics, and continual improvement
- https://www.atlassian.com/itsm/service-request-management
Supports
- Service requests for access, equipment, information, and other predefined user needs
- Distinctions among service requests, incidents, problems, and changes
- Intake, assessment, approval, fulfillment, closure, self-service, automation, knowledge, and measurement guidance
- https://www.atlassian.com/software/jira/service-management/product-guide/getting-started/service-request-management
Supports
- Request fulfillment lifecycle and service-desk contact role
- Portal, request type, workflow, queue, service target, automation, knowledge, reporting, and requester-feedback capabilities
- Jira Service Management Landscape role
- https://www.servicenow.com/docs/r/it-service-management/request-management/c_RequestManagement.html
Supports
- Requests for services, products, or information through self-service
- Fulfillment workflow, reduced manual effort, and status visibility for users and agents
- https://www.servicenow.com/products/request-management.html
Supports
- Published service catalog, workflow, approvals, service levels, notifications, dashboards, and self-service channels
- ServiceNow Request Management Landscape role
- https://www.iso.org/standard/70636.html
Supports
- Service management system governance, operation, measurement, review, maintenance, and improvement context
- https://www.freshworks.com/freshservice/features/
Supports
- Freshservice service catalog, portal, workflow automation, knowledge, routing, service-level management, and reporting
- Freshservice Landscape role
- https://www.bmc.com/it-solutions/bmc-helix-itsm-capabilities.html
Supports
- BMC catalog request types, self-service, approval rules, service targets, automated standard requests, and linked ITSM work
- BMC Helix ITSM Landscape role
- https://www.manageengine.com/products/service-desk/itsm/service-request-management-software.html
Supports
- ServiceDesk Plus portal, catalog, visual workflows, routing, automation, notifications, service targets, knowledge, and reporting
- ManageEngine ServiceDesk Plus Landscape role
- https://www.manageengine.com/products/service-desk/customizations/
Supports
- Structured and conditional request forms that capture fulfillment information at ticket creation
- Custom workflow actions, tasks, notifications, automation, and webhooks
- https://www.ivanti.com/products/ivanti-neurons-itsm
Supports
- Ivanti request intake, self-service, no-code workflow, automation, reporting, asset context, and deployment options
- Ivanti Neurons for ITSM Landscape role
- https://docs.topdesk.com/en/service-catalogue-in-topdesk.html
Supports
- TOPdesk service catalog, self-service portal, knowledge, service discovery, and direct service requests
- TOPdesk Landscape role
- https://docs.topdesk.com/en/services-and-other-modules.html
Supports
- TOPdesk links from services to service levels, self-service, knowledge, orders, forms, changes, assets, and actions
- https://www.solarwinds.com/web-help-desk/use-cases/service-request-management
Supports
- Central request intake, request forms, routing, workflow, escalation, portal, knowledge, service targets, dashboards, and asset context
- SolarWinds service desk Landscape role
- https://github.com/sindresorhus/awesome
Supports
- Starting point for discovery of qualifying curated awesome lists
- https://github.com/awesome-selfhosted/awesome-selfhosted#ticketing
Supports
- Discovery of Frappe Helpdesk, OTOBO, Request Tracker, and Zammad in the curated Ticketing section
- https://frappe.io/helpdesk
Supports
- Frappe email, form, and portal intake, assignment, service-level rules, escalation, knowledge, workflow, and reporting
- Frappe Helpdesk Awesome Link rationale
- https://doc.otobo.org/manual/admin/11.0/en/content/administration-area/processes-automation/process-management.html
Supports
- OTOBO process tickets, required fields, approval activities, queue movement, responsibilities, transitions, and completion
- OTOBO Awesome Link and Landscape roles
- https://docs.bestpractical.com/rt/5.0.8/working_with_rt.html
Supports
- Request Tracker queue-based ticket creation, configurable fields, attachments, comments, replies, and daily agent work
- Request Tracker Awesome Link and Landscape roles
- https://admin-docs.zammad.org/en/latest/manage/overviews.html
Supports
- Zammad filtered worklists, role and user visibility, ticket attributes, sorting, and grouping
- Zammad Awesome Link rationale
