---

Service levels are defined targets for the performance of a service.

Service levels are agreed between the service provider and the service consumer.

Service level agreements document service levels and define what is expected from the service.

Service levels should be based on business needs and customer expectations.

Monitoring service levels helps ensure that services are delivering the expected value.

If service levels are not met, improvement actions may be required.

---

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

This video explains how expectations are formalised and why ambiguity here creates disputes and dissatisfaction.

a) Service levels in TakeCars terms

Service levels answer questions such as:

• How quickly should a booking be confirmed?
• How fast should support respond?
• What reliability level is expected from hosts?
• What happens when expectations are not met?

Even if undocumented, service levels always exist. If they are not explicit, customers invent their own.

---

b) Explicit vs implicit service levels

Explicit service levels

• Confirmation within a stated time window
• Support response within X hours
• Refund processed within Y days

These reduce uncertainty and disputes.

Implicit service levels

• “I assumed the car would be there”
• “I expected immediate support”
• “I thought cancellations were impossible”

Implicit expectations are dangerous because they are invisible until broken.

---

c) Marketplace-specific service level complexity

TakeCars must manage layered service levels:

• Platform service levels (availability, support)
• Host service levels (response time, reliability)
• Third-party service levels (payments, insurance)

Failures often occur at handovers between these layers.

---

d) Exam-critical insight

If the exam asks:

“What are service levels?”

Correct logic:

• Defined targets for service performance
• Agreed between provider and consumer
• Based on business needs and expectations

Answers implying:

• Service levels are internal only
• Service levels are fixed and universal
  Are incorrect.

---

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

Service levels (high probability)

• Defined performance targets
• Agreed with service consumers
• Based on business and customer needs
• Monitored and reviewed

---

Service level agreements (SLA) nuance

• SLAs document service levels
• SLAs do not create value by themselves
• Value comes from meeting the agreed levels

---

Common exam traps

• Service levels are optional → False
• Service levels are purely technical → False
• Service levels never change → False

---

One-line memory hook

Service levels formalise expectations and make performance measurable.

---

---

Constraints are factors that limit or restrict the way a service can be used.

Constraints may be related to policies, regulations, technology, resources, or skills.

Removing or reducing constraints can increase the value of a service.

However, some constraints are necessary to manage risks or comply with legal and regulatory requirements.

Service providers should understand which constraints affect service consumers and how these constraints impact outcomes.

Balancing constraints and freedom of use is essential for effective service management.

---

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

This video explains why friction exists and how it should be handled deliberately, not accidentally.

a) Constraints in TakeCars terms

Constraints are not always failures. They are often intentional.

Common TakeCars constraints:

• Age limits
• Deposit requirements
• Mileage limits
• Geographic restrictions
• Insurance exclusions
• Time-bound pickups and returns

These constraints shape how the service can be used.

---

b) Good constraints vs bad constraints

Necessary constraints

• Protect vehicles and hosts
• Manage insurance risk
• Ensure legal compliance
• Reduce fraud and misuse

Examples:

• Minimum driver age
• Identity verification
• Damage liability rules

These constraints preserve warranty.

---

Harmful or accidental constraints

• Overly complex rules
• Hidden exclusions
• Manual approvals that delay pickups
• Poorly explained policies

These constraints destroy:

• Utility (cannot use the service as intended)
• Perceived value (frustration outweighs benefit)

---

c) Constraint removal as a value lever

Increasing value at TakeCars often means:

• Removing unnecessary steps
• Simplifying rules
• Making constraints visible and predictable

Examples:

• Clear upfront deposit explanation
• Standardised pickup instructions
• Default policies instead of case-by-case decisions

This aligns directly with ITIL’s guidance.

---

d) Exam-critical insight

If the exam asks:

“What is the role of constraints in service management?”

Correct logic:

• Constraints limit service use
• Some constraints reduce value
• Some constraints are necessary for risk and compliance
• Balance is required

Answers implying “constraints should always be removed” are incorrect.

---

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

Constraints definition (high probability)

• Factors that limit or restrict service use
• Can be technical, legal, policy-based, or resource-based

---

Exam traps

• All constraints reduce value → False
• Constraints should be eliminated → False
• Constraints are always negative → False

Look for balanced wording:

• “Remove unnecessary constraints”
• “Manage constraints appropriately”

---

One-line memory hook

Constraints shape how a service is used; the goal is balance, not elimination.

---

Utility and warranty are influenced by several factors.

Utility may be affected by whether the service supports the required outcomes and removes constraints for the service consumer.

Warranty may be affected by availability, capacity, continuity, and security.

Availability refers to whether the service is accessible when needed.

Capacity refers to whether the service has sufficient resources to meet demand.

Continuity refers to whether the service can continue to operate during disruptions.

Security refers to whether information and assets are protected.

Service providers must consider these factors to ensure that services deliver value.

---

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

This video explains what actually makes utility and warranty succeed or fail in practice.

a) Utility drivers in TakeCars

Utility depends on:

• The service supporting the trip purpose
• Constraints being removed

Examples:

• Correct car type for terrain and group size
• Location aligned with travel plan
• Clear rules that do not block usage

Utility fails when:

• Car restrictions block planned use
• Pickup location is impractical
• Terms are unclear or restrictive

---

b) Warranty drivers mapped to TakeCars

Availability

• Is the car actually available at the agreed time?
• Are backups in place if a host cancels?

Capacity

• Are there enough cars during peak season?
• Can support handle spikes in issues?

Continuity

• Can TakeCars operate during:
  • Host no-shows
  • Platform outages
  • Payment failures

Security

• Are payments protected?
• Is customer data secure?
• Are vehicles protected against misuse?

All four are explicitly named in ITIL exams.

---

c) Marketplace failure patterns

Most negative experiences come from warranty failures:

• Availability failure: host cancels
• Capacity failure: no cars during holidays
• Continuity failure: support unreachable
• Security failure: payment or data issue

Utility may be perfect, but value is still lost.

---

d) Exam-critical insight

If the exam asks:

“What influences warranty?”

Correct answers will reference:

• Availability
• Capacity
• Continuity
• Security

If any of these appear, they are almost certainly correct.

---

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

Warranty factors (must be memorised)

• Availability
• Capacity
• Continuity
• Security

Exact wording matters.

---

Utility factors

• Supports outcomes
• Removes constraints

Utility is about purpose, not reliability.

---

Common exam traps

• Warranty equals quality alone → False
• Utility is about reliability → False

---

One-line memory hook

Utility defines purpose; warranty ensures reliability through availability, capacity, continuity, and security.

Utility describes what a service does and how it meets a customer’s needs.

Utility is often described as “fit for purpose”.

Warranty describes how a service is delivered and whether it can be relied upon.

Warranty is often described as “fit for use”.

Both utility and warranty are required for a service to deliver value.

A service with utility but no warranty will not deliver value.

A service with warranty but no utility will also not deliver value.

Service providers must ensure that services deliver both utility and warranty.

---

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

This video introduces one of the most exam-tested ITIL concepts and one of the most practical lenses for judging service quality.

a) Utility vs warranty in plain TakeCars terms

Utility = fit for purpose

What the service actually enables.

For TakeCars:

• The car is the right type
• The location matches the trip
• The booking meets the travel need

If the customer needs:

• A family car
• For a road trip
• With enough luggage space

Utility fails if the car cannot meet that purpose.

---

Warranty = fit for use

How reliably the service is delivered.

For TakeCars:

• Car is available on time
• Car is roadworthy
• Insurance is valid
• Support is available if something goes wrong

A perfect car that never shows up has utility but no warranty.

---

b) Why both are required

Examples:

• Cheap car, wrong size, but always available
  • Warranty present
  • Utility missing
  • No value
• Perfect car, correct spec, but host cancels last minute
  • Utility present
  • Warranty missing
  • No value

Only when both exist does value emerge.

---

c) Marketplace-specific insight

Marketplaces often focus on:

• Utility (more listings, more options)

But customers churn because of:

• Warranty failures (cancellations, breakdowns, poor support)

This is why:

• Host reliability
• Response times
• Backup processes

Matter as much as search and pricing.

---

d) Exam-critical insight

If an exam question asks:

“What is required for a service to deliver value?”

Correct answer:

• Both utility and warranty

Any answer suggesting one alone is sufficient is incorrect.

---

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

Utility vs warranty definitions (very high probability)

• Utility: what the service does, fit for purpose
• Warranty: how the service is delivered, fit for use

Exact phrasing matters.

---

Common exam traps

• Utility alone delivers value → False
• Warranty alone delivers value → False

Look for answers that explicitly include both.

---

One-line memory hook

Utility enables the outcome; warranty ensures it can be relied upon.

---

---

Costs are the amount of money spent on a service or service component.

Risks are possible events that could cause harm or loss or make it more difficult to achieve objectives.

Services are designed to help customers achieve outcomes by reducing the need to manage specific costs and risks.

Not all costs and risks are removed by a service.

Some costs and risks remain with the service consumer, while others are managed by the service provider.

The allocation of costs and risks should be clearly understood by all parties involved.

---

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

This video completes the value–cost–risk triangle, which is fundamental to both ITIL theory and marketplace design.

a) Costs in TakeCars terms

Costs managed by TakeCars and hosts:

• Vehicle purchase and depreciation
• Maintenance and servicing
• Insurance arrangements
• Platform development and hosting

Costs still borne by the customer:

• Rental fee
• Fuel
• Fines and tolls
• Optional extras

Customers pay for outcomes, but not for ownership.

---

b) Risks in TakeCars terms

Risks reduced by the service:

• Vehicle reliability risk (screened hosts)
• Insurance complexity
• Fraud and payment risk
• Availability uncertainty

Risks retained by the customer:

• Misuse of the vehicle
• Late return
• Damage caused during use
• Rule violations

Risks retained by hosts:

• Wear and tear
• Downtime between rentals
• Behaviour of renters

This shared allocation is exactly what ITIL describes.

---

c) Why clarity of cost and risk allocation matters

Most disputes arise when:

• Customers assume all risk is removed
• Hosts assume TakeCars absorbs all loss
• Platform policies are vague

Clear allocation:

• Reduces disputes
• Simplifies support decisions
• Protects trust

---

d) Exam-critical insight

If the exam asks:

“What do services do regarding costs and risks?”

Correct logic:

• Services reduce the need to manage specific costs and risks
• They do not eliminate all costs and risks

Answers implying “complete removal” are incorrect.

---

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

Costs and risks (very high probability)

• Costs = money spent
• Risks = potential negative events
• Services reduce, but do not remove, costs and risks
• Responsibility is shared

---

Common exam traps

• All risks are transferred to the provider → False
• Customers have no remaining costs → False
• Risk management is one-sided → False

---

One-line memory hook

Services shift and reduce costs and risks, but never eliminate them entirely.

Outcomes are the results that a service consumer wants to achieve.

Outputs are tangible or intangible deliverables produced by a service.

An output may contribute to an outcome, but it does not guarantee that the outcome will be achieved.

Services are designed to enable outcomes, not just to produce outputs.

Focusing only on outputs can result in services that do not deliver real value.

Service providers should understand the outcomes that service consumers are trying to achieve.

---

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

This video addresses a classic ITIL distinction that is extremely relevant for product and operations decisions.

a) Outputs vs outcomes in TakeCars terms

Outputs (what TakeCars produces):

• Booking confirmation
• Vehicle handover
• Payment receipt
• Support response

Outcomes (what the customer wants):

• Complete a trip successfully
• Arrive on time
• Avoid stress and disputes
• Feel confident and safe

A booking confirmation does not guarantee a successful trip.

---

b) Why marketplaces often fail here

Many marketplace platforms optimise for outputs:

• Faster confirmations
• More listings
• More messages sent

But customers judge value by outcomes:

• Did the car show up?
• Did anything go wrong?
• Was the problem resolved quickly?

ITIL explicitly warns against output-only thinking.

---

c) Practical TakeCars examples

• A confirmed booking where the host cancels last minute
  • Output delivered
  • Outcome failed
• A delayed pickup but proactive support fixes the issue
  • Output imperfect
  • Outcome achieved

This is why support quality matters as much as platform features.

---

d) Exam-critical insight

If the exam asks:

“What should services focus on?”

Correct answer:

• Enabling outcomes

Incorrect but tempting answer:

• Producing outputs efficiently

---

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

Outcomes vs outputs (high probability)

• Outputs are deliverables
• Outcomes are results and benefits
• Outputs do not guarantee outcomes

Always choose answers that:

• Mention outcomes
• Mention value
• Mention customer objectives

---

Common exam traps

• Outputs equal value → False
• Services exist to produce deliverables → False

---

One-line memory hook

Outputs are what the service does; outcomes are why the service exists.

---

---

Service value is created through the interaction of service providers and service consumers.

Value is realised when services help consumers achieve their desired outcomes.

The perception of value may differ between different stakeholders.

Costs are the amount of money spent on a service, while risks are potential events that could cause harm or loss.

Services help customers achieve outcomes by reducing the need to manage specific costs and risks.

Service providers and service consumers share responsibility for managing risks.

Value is co-created throughout the service relationship, not at a single point in time.

---

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

This video deepens the value, cost, and risk concept, which is central to both ITIL theory and TakeCars’ business reality.

a) Value is realised only when the trip succeeds

For TakeCars:

• Value is not created at booking
• Value is realised when the customer completes the trip successfully

A booking that ends in:

• Cancellation
• Breakdown
• Dispute

Has destroyed or reduced value, even if revenue was collected.

---

b) Different stakeholders perceive value differently

In TakeCars:

• Guest values convenience, safety, predictability
• Host values utilisation, income, low hassle
• TakeCars values successful transactions and trust

These perceptions often conflict.
ITIL explicitly recognises this, which is why “value is subjective” appears repeatedly in the exam.

---

c) Costs and risks shifted away from the customer

Examples of costs and risks removed by TakeCars:

• Vehicle ownership costs
• Maintenance planning
• Insurance negotiation
• Depreciation risk

What remains with the customer:

• Usage-related risk
• Compliance with rules
• Care of the vehicle

This shared responsibility is exam-relevant.

---

d) Shared risk responsibility in a marketplace

ITIL is clear:

• Providers do not absorb all risk
• Consumers do not absorb all risk

For TakeCars:

• Platform manages platform risk
• Hosts manage vehicle condition risk
• Guests manage usage risk

When this balance is unclear, disputes arise.

---

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

Value, cost, and risk (very high probability)

• Value is realised through outcomes
• Value is subjective
• Services reduce the need to manage costs and risks
• Risk responsibility is shared

---

Exam trap to avoid

• “The service provider removes all risk” → Incorrect
• “Value is delivered at the point of sale” → Incorrect

Look for wording that includes:

• Outcomes
• Shared responsibility
• Co-creation

---

One-line memory hook

Value emerges over time through outcomes, with costs and risks shared between provider and consumer.

---

You have now completed video 8.5, which closes the core service relationship and value block.

Next good options:

Service relationships describe the cooperation between a service provider and a service consumer.

A service relationship includes service provision, service consumption, and service relationship management.

Service provision refers to the activities performed by the service provider to deliver services.

Service consumption refers to the activities performed by the service consumer to use services.

Service relationship management ensures that service relationships are managed effectively and that both parties understand their responsibilities.

Service relationships are based on agreed expectations, responsibilities, and trust.

Effective service relationships help ensure value is co-created and sustained over time.

---

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

This video explains how TakeCars actually functions as a relationship-based system, not just a transactional platform.

a) TakeCars runs on service relationships, not bookings

Every booking creates multiple service relationships:

• TakeCars ↔ Guest
• TakeCars ↔ Host
• Host ↔ Guest (mediated)

If these relationships are poorly defined, friction and disputes increase.

---

b) Mapping the three parts of a service relationship to TakeCars

1. Service provision (provider activities)

For TakeCars:

• Platform availability
• Booking confirmation
• Payment handling
• Rules and policies
• Support and dispute resolution

For hosts:

• Providing a roadworthy car
• Honouring availability
• Clear pickup and return process

---

2. Service consumption (consumer activities)

For guests:

• Searching and booking
• Making payments
• Collecting and returning the vehicle
• Following usage rules

For hosts (as consumers of TakeCars services):

• Listing vehicles
• Responding to bookings
• Using payout and messaging tools

---

3. Service relationship management

This is where marketplaces win or fail.

Includes:

• Clear terms and conditions
• Role clarity
• Communication standards
• Enforcement of rules
• Handling breaches fairly

TakeCars’ trust and reputation live here.

---

c) Why this matters operationally

Most TakeCars problems are not technical; they are relationship failures:

• Misaligned expectations
• Poor communication
• Unclear responsibilities

ITIL frames these as service relationship issues, not isolated incidents.

---

d) Exam insight

If the exam asks:

“What does a service relationship include?”

Correct answer must mention:

• Service provision
• Service consumption
• Relationship management

Leaving one out is incorrect.

---

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

Service relationship definition (high probability)

• Cooperation between provider and consumer
• Includes:
  • Service provision
  • Service consumption
  • Service relationship management

All three must be present.

---

Common exam traps

• Service relationships are one-way → False
• Only providers manage relationships → False
• Relationships are optional → False

---

One-line memory hook

Service relationships combine delivery, use, and management of expectations.

---

Service offerings describe what a service provider offers to service consumers.

A service offering may include goods, access to resources, and service actions.

Goods are physical items provided to the service consumer and may be consumed, transferred, or owned.

Access to resources allows the service consumer to use the provider’s resources without owning them.

Service actions are activities performed by the service provider to address a consumer’s needs.

Most services include a combination of goods, access to resources, and service actions.

Service offerings are designed to meet the needs of specific service consumers.

---

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

This video explains what exactly is being offered, which is especially important in a marketplace where value is often misunderstood.

a) TakeCars service offering is not “a car”

In ITIL terms, TakeCars offers a composite service offering, not a single thing.

Customers are not just renting a physical object; they are consuming a structured combination of elements.

---

b) Mapping the three components to TakeCars

1. Goods

Physical items provided as part of the service.

Examples:

• The vehicle itself
• Child seats
• Snow chains
• GPS units

Ownership does not transfer, but physical use does.

---

2. Access to resources

Temporary rights to use resources owned by others.

Examples:

• Access to a host’s vehicle for a defined period
• Access to insurance coverage during the rental
• Access to booking and payment infrastructure

This is the core rental concept.

---

3. Service actions

Activities performed to support the customer.

Examples:

• Booking confirmation
• Customer support
• Dispute handling
• Refund processing
• Host verification

Without service actions, access alone is insufficient.

---

c) Why this matters for TakeCars operations

Understanding the service offering helps:

• Design clearer pricing
• Explain value beyond “cheap cars”
• Resolve disputes (what was actually included)
• Avoid overpromising

Many conflicts arise when customers assume:

• Goods include unlimited support
• Access includes guarantees that were never offered

Clear service offering definition reduces this risk.

---

d) Exam insight

The exam often tests:

• Whether a service offering is one thing or multiple components

Correct logic:

• Most services combine goods, access, and actions

If an answer says:

• “A service offering consists of only one element”
  It is incorrect.

---

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

Service offering definition (high probability)

• Describes what the provider offers
• Designed to meet specific consumer needs
• May include:
  • Goods
  • Access to resources
  • Service actions

---

Goods vs access (common confusion)

• Goods: physical items
• Access: permission to use resources
• Services are usually access-based, not ownership-based

---

Common exam traps

• All services provide goods → False
• Service offerings are only intangible → False
• Service offerings exclude physical components → False

---

One-line memory hook

A service offering is a designed mix of goods, access, and actions that enable value.

---

Service providers and service consumers play different roles in service relationships.

A service provider is an organisation that provides services to one or more service consumers.

A service consumer is an organisation or person that consumes services.

There are three types of service consumer roles: customer, user, and sponsor.

The customer defines the requirements for the service and takes responsibility for the outcomes of service consumption.

The user is the person who uses the service on a day-to-day basis.

The sponsor is the person or organisation that authorises budget for the service.

A single individual or organisation may perform more than one service consumer role.

Understanding service consumer roles helps ensure that services are designed and delivered to meet the needs of all stakeholders.

---

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

This video is very important for marketplaces, because TakeCars routinely deals with multiple roles at once, often within the same booking.

a) Service provider vs service consumer in TakeCars

• Service provider
  • TakeCars as the platform operator
  • Hosts as contributing service providers
• Service consumers
  • Guests (renters)
  • Businesses booking vehicles for staff
  • Sometimes the host themselves (using platform services)

The exam expects clarity here.

---

b) The three service consumer roles mapped to TakeCars

1. Customer

Who defines requirements and is accountable for outcomes.

Examples:

• A traveller booking a car for their trip
• A company arranging rentals for employees

Customer responsibilities:

• Choosing dates and location
• Accepting terms
• Paying for the booking

---

2. User

Who actually uses the service.

Examples:

• The person driving the car
• A family member listed as an additional driver

Important nuance:

• The user may not be the person who booked or paid

---

3. Sponsor

Who authorises budget.

Examples:

• A company paying for an employee’s rental
• A parent paying for a child’s rental
• A business owner approving fleet bookings

In consumer rentals, sponsor and customer are often the same person.

---

c) One person can play multiple roles

Very common in TakeCars:

• The renter books, pays, and drives
  • Customer
  • Sponsor
  • User

The exam will explicitly test that:

• Roles are not mutually exclusive

---

d) Why this matters operationally for TakeCars

If roles are confused:

• Support talks to the wrong person
• Refunds are delayed
• Authorisations fail
• Disputes escalate unnecessarily

Correct role recognition improves:

• Communication
• Payment handling
• Accountability

---

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

Service provider vs service consumer

• Provider: offers the service
• Consumer: receives and uses the service

If an answer blurs this line, it is incorrect.

---

Three service consumer roles (must be memorised)

1. Customer – defines requirements, accountable for outcomes
2. User – uses the service
3. Sponsor – authorises budget

Exact wording matters.

---

High-probability exam traps

• Customer and user are always the same → False
• Sponsor always uses the service → False
• One person can only have one role → False

---

One-line memory hook

Customers define and own outcomes, users use the service, sponsors pay for it.