2.1.

Let’s now look at the concept of service relationships.

In ITIL, a service relationship is a cooperation between a service provider and a service consumer.

Service relationships include service provision, service consumption, and service relationship management.

The service provider is the organisation that provides services to consumers.

The service consumer is the organisation or individual that receives and uses services.

Service relationships are not one-way interactions.

Both the provider and the consumer play an active role in creating value.

The service provider cannot create value alone, and the consumer cannot create value alone either.

Instead, value is created through ongoing collaboration and interaction between the parties.

Effective service relationships require clear communication, trust, and shared understanding of expectations.

Managing service relationships effectively is essential for successful service management.

---

2. How this applies to TakeCars (car-rental marketplace)

This section maps directly and structurally to how TakeCars should view its ecosystem.

a) TakeCars has three service relationships, not one

ITIL describes service relationships as cooperation. In TakeCars, there are multiple overlapping ones:

1. TakeCars ↔ Customer
   • Promise: predictable mobility
   • Risk: disappointment, stress, refunds
2. TakeCars ↔ Supplier
   • Promise: demand, payments, rules
   • Risk: quality control, compliance, reliability
3. Customer ↔ Supplier
   • Facilitated by TakeCars, but never unmanaged

If TakeCars ignores any one of these, value collapses.

---

b) Service provision vs service consumption (critical distinction)

From an ITIL lens:

• Service provision (TakeCars side):
  • Platform availability
  • Supplier vetting
  • Payments
  • Support
  • Rules and enforcement
• Service consumption (Customer side):
  • Booking
  • Pickup
  • Driving
  • Returning
  • Feedback

Failures often happen when TakeCars optimises provision but ignores consumption experience.

---

c) Relationship management = marketplace moat

ITIL explicitly calls out service relationship management.

For TakeCars, this is:

• Dispute handling
• Clear communication
• Setting expectations early
• Acting fast when something breaks

A marketplace without strong relationship management becomes:

• A classifieds board
• A race to the bottom on price
• Untrusted

Strong relationship management is what allows TakeCars to charge margin.

---

3. Key ideas to read right before the exam (high-yield)

This topic is a classic ITIL Foundation exam favourite.

Core definition (must recognise instantly)

A service relationship is a cooperation between a service provider and a service consumer.

Key words:

• Cooperation
• Ongoing
• Two-way

If an option describes:

• One-way delivery → wrong
• Passive consumer → wrong

---

Service relationship components (exam list)

A service relationship includes:

• Service provision
• Service consumption
• Service relationship management

If one is missing, the answer is incomplete.

---

Exam trap to avoid

Wrong answers often say:

• “The provider creates value for the consumer”
• “The consumer receives value”

Correct answers say:

• “Both parties contribute”
• “Value is co-created”

---

One-sentence exam anchor

Services work only when providers and consumers actively cooperate.

Repeat this mentally when choosing answers.

---