Service request management is the practice of handling predefined, user-initiated requests for services.

Service requests are usually routine, low risk, and pre-approved.

The purpose of service request management is to support agreed quality of service by handling service requests efficiently and effectively.

Service requests may include requests for information, access, or standard changes.

Clear procedures and workflows help ensure service requests are fulfilled consistently.

Automation can be used to improve efficiency where appropriate.

---

2. How This Applies to TakeCars (Car Rental Marketplace)

This practice maps directly onto a large share of TakeCars’ daily operational load.

a) What a “service request” is at TakeCars

Service requests are not incidents. They are normal, expected asks such as:

• Change pickup time
• Add an additional driver
• Request child seats or extras
• Extend a booking
• Ask for invoice or receipt
• Update contact details

These are routine and predictable.

---

b) Why separating requests from incidents matters

If TakeCars treats everything as an “incident”:

• Support costs rise
• Response times slow
• True emergencies get lost

Service request management exists to:

• Standardise common requests
• Handle them quickly
• Reduce cognitive load on support staff

---

c) Predefined, low-risk, pre-approved

ITIL explicitly states service requests are:

• Known in advance
• Approved by default
• Low risk

For TakeCars this means:

• Clear rules for extensions
• Fixed pricing for extras
• Automated approval where possible

Anything that requires investigation or blame is likely an incident, not a request.

---

d) Automation as a force multiplier

High-impact automation examples:

• Self-service booking changes
• Automatic price recalculation
• Pre-approved extension flows
• Template-based responses

Automation improves:

• Speed
• Consistency
• Customer satisfaction

But only after workflows are clear.

---

e) Exam-critical insight

If the exam asks:

“What is the purpose of service request management?”

Correct logic:

• Handle predefined, user-initiated requests
• Ensure consistent, efficient fulfilment
• Support agreed service quality

Answers confusing requests with incidents are incorrect.

---

3. Key Things to Read / Remember Right Before the Exam

Service request management (high probability)

• A service management practice
• Handles predefined, routine requests
• Requests are user-initiated
• Usually low risk and pre-approved

---

Common exam traps

• Service requests are incidents → False
• Service requests require investigation → False
• Service requests are always high risk → False

---

One-line memory hook

Service request management fulfils routine user requests quickly and consistently.

---