The ITIL service requests fulfillment is usually for small changes or additions which have low risk, and low-cost, and occur quite frequently. Because of this, it would not be wise to club these requests along with high-risk ones, which is why it has been made into a separate process being handled by a dedicated team. The process of fulfilling the requests made is called request fulfillment.<\/p>\n
Objectives of ITIL Service Request Fulfillment<\/strong><\/h2>\nThe objectives of ITIL service request fulfillment are as follows:<\/p>\n
\n- \n
Make the users aware of the availability of existing services and the procedure to request them<\/p>\n<\/li>\n
- \n
To create a separate channel through which users can request and receive the required service that has been granted prior approval<\/p>\n<\/li>\n
- \n
Obtain and deliver the requested standard services on time<\/p>\n<\/li>\n
- \n
To provide assistance with general information requests and complaints.<\/p>\n<\/li>\n<\/ul>\n
![\"ITIL](\"https:\/\/www.invensislearning.com\/blog\/wp-content\/uploads\/2020\/11\/ITIL-4-Foundation-864x90-2.jpg\")
<\/a><\/p>\nScope of ITIL Service Request Fulfillment<\/strong><\/h2>\nA company will have several hundred service requests per day. It becomes tough to manage all of them unless there is a standardized model to outline and classify the request. The service request model should be built in such a way so as to consider the parameters mentioned below.<\/p>\n
\n- \n
The person or team who will be in charge of handling the request needs to be appointed<\/p>\n<\/li>\n
- \n
The process used to deliver the service should be determined.<\/p>\n<\/li>\n
- \n
The service request should be fulfilled quickly and on time according to the predetermined time window or a service level agreement<\/p>\n<\/li>\n
- \n
If the response team is unable to fulfill the service request, an alternate path to escalate the request further should be taken<\/p>\n<\/li>\n<\/ul>\n
Activities of ITIL Service Request Fulfillment<\/strong><\/h2>\n![\"activities](\"https:\/\/www.invensislearning.com\/blog\/wp-content\/uploads\/2021\/07\/service-request-fulfillment-activities.png\")
<\/strong><\/p>\n\n- \n
Menu Selection<\/strong><\/h3>\nUsually, in an organization, service desks are used to raise requests. But present technology allows users to raise the requests themselves using self-help tools that are linked to the service management. A menu-like interface can be offered to users to select the details of the service request from a previously defined list.<\/p>\n<\/li>\n
- \n
Financial Approval<\/strong><\/h3>\nCertain service requests need another step after raising the requests to get the required financial approval. The user will have to get the necessary approval from the concerned superiors in charge of the financial activities of the company.<\/p>\n<\/li>\n
- \n
Other Approval<\/strong><\/h3>\nSometimes the user may need to seek further approvals from a specific department to ensure that the request is in accordance with certain laid down standards or parameters. There should be an option in request fulfillment to define and check the necessity of such approvals.<\/p>\n<\/li>\n
- \n
Fulfillment<\/strong><\/h3>\nThe fulfillment of the service request is dependent on the type of request that is raised. Certain requests can be fulfilled by the service desks<\/a><\/span> themselves whereas some requests may need to be forwarded to specific departments.<\/p>\n<\/li>\n- \n
Closure<\/strong><\/h3>\nAfter the service has been fulfilled, it needs to be referred back to the service desk so that the request can be closed and the request can be marked as solved. The service desk needs to ensure that the user is satisfied with the way the request has been solved before it can be marked as closed.<\/p>\n<\/li>\n
- \n
Metrics<\/strong><\/h3>\nIn order to judge the efficiency and effectiveness of request fulfillment by the concerned departments, we need to analyze the following metrics to get an accurate picture of the whole process.<\/p>\n
\n- \n
Total service requests<\/p>\n<\/li>\n
- \n
Breakdown of service requests at every stage<\/p>\n<\/li>\n
- \n
Present backlog of outstanding service requests<\/p>\n<\/li>\n
- \n
Mean time for handling each type of request<\/p>\n<\/li>\n
- \n
Percentage and exact number of requests completed within the agreed time frame<\/p>\n<\/li>\n
- \n
The average cost of each service request<\/p>\n<\/li>\n
- \n
Level of customer satisfaction with the handling of their requests<\/p>\n<\/li>\n<\/ul>\n<\/li>\n<\/ol>\n
Make the users aware of the availability of existing services and the procedure to request them<\/p>\n<\/li>\n
To create a separate channel through which users can request and receive the required service that has been granted prior approval<\/p>\n<\/li>\n
Obtain and deliver the requested standard services on time<\/p>\n<\/li>\n
To provide assistance with general information requests and complaints.<\/p>\n<\/li>\n<\/ul>\n
A company will have several hundred service requests per day. It becomes tough to manage all of them unless there is a standardized model to outline and classify the request. The service request model should be built in such a way so as to consider the parameters mentioned below.<\/p>\n The person or team who will be in charge of handling the request needs to be appointed<\/p>\n<\/li>\n The process used to deliver the service should be determined.<\/p>\n<\/li>\n The service request should be fulfilled quickly and on time according to the predetermined time window or a service level agreement<\/p>\n<\/li>\n If the response team is unable to fulfill the service request, an alternate path to escalate the request further should be taken<\/p>\n<\/li>\n<\/ul>\n Usually, in an organization, service desks are used to raise requests. But present technology allows users to raise the requests themselves using self-help tools that are linked to the service management. A menu-like interface can be offered to users to select the details of the service request from a previously defined list.<\/p>\n<\/li>\n Certain service requests need another step after raising the requests to get the required financial approval. The user will have to get the necessary approval from the concerned superiors in charge of the financial activities of the company.<\/p>\n<\/li>\n Sometimes the user may need to seek further approvals from a specific department to ensure that the request is in accordance with certain laid down standards or parameters. There should be an option in request fulfillment to define and check the necessity of such approvals.<\/p>\n<\/li>\n The fulfillment of the service request is dependent on the type of request that is raised. Certain requests can be fulfilled by the service desks<\/a><\/span> themselves whereas some requests may need to be forwarded to specific departments.<\/p>\n<\/li>\n After the service has been fulfilled, it needs to be referred back to the service desk so that the request can be closed and the request can be marked as solved. The service desk needs to ensure that the user is satisfied with the way the request has been solved before it can be marked as closed.<\/p>\n<\/li>\n In order to judge the efficiency and effectiveness of request fulfillment by the concerned departments, we need to analyze the following metrics to get an accurate picture of the whole process.<\/p>\n Total service requests<\/p>\n<\/li>\n Breakdown of service requests at every stage<\/p>\n<\/li>\n Present backlog of outstanding service requests<\/p>\n<\/li>\n Mean time for handling each type of request<\/p>\n<\/li>\n Percentage and exact number of requests completed within the agreed time frame<\/p>\n<\/li>\n The average cost of each service request<\/p>\n<\/li>\n Level of customer satisfaction with the handling of their requests<\/p>\n<\/li>\n<\/ul>\n<\/li>\n<\/ol>\n<\/a><\/p>\nScope of ITIL Service Request Fulfillment<\/strong><\/h2>\n
\n
Activities of ITIL Service Request Fulfillment<\/strong><\/h2>\n
<\/strong><\/p>\n\n
Menu Selection<\/strong><\/h3>\n
Financial Approval<\/strong><\/h3>\n
Other Approval<\/strong><\/h3>\n
Fulfillment<\/strong><\/h3>\n
Closure<\/strong><\/h3>\n
Metrics<\/strong><\/h3>\n
\n