# Customer

> Source: Courseiva IT Certification Glossary — https://courseiva.com/glossary/customer

## Quick definition

A customer is someone who wants a service and agrees to pay for it. They decide what the service should do, but they might not be the actual person using the service. For example, a company that buys a cloud backup service is the customer, even if the IT team is the one using it every day.

## Simple meaning

Think of a customer like a person who orders a pizza delivery for a group of friends. The customer is the one who calls the pizza place, picks the toppings, and pays for the pizza. The friends are the ones who actually eat the pizza. The pizza place is the service provider, and the pizza itself is the service. The customer wants the pizza delivered hot and with the right toppings. They might not be the one eating it, but they are the one who decides what is needed and who pays. In IT service management, this idea is very important. The customer is not always the end user. An end user is the person who uses the service day to day, like logging into a software program. The customer might be a department head who buys the software for the whole team. That department head sets the requirements: the software must have reporting, must be secure, and must be available during business hours. The service provider, perhaps an internal IT team or an external vendor, then designs and delivers the service to meet those requirements. The customer also pays for the service, either directly through a budget or indirectly through organizational cost allocations. Understanding this distinction helps everyone stay clear about who makes decisions and who is responsible for payment. It also helps avoid confusion when things go wrong: if the service fails, the customer might ask why, and the provider must explain. The user might be frustrated too, but the formal relationship is between the customer and the provider. In ITIL 4, this customer role is central to service management because services must be designed around the customer's needs, not just the user's needs. This ensures the service delivers real value to the organization that pays for it.

## Technical definition

In IT service management, specifically within the ITIL 4 framework, a customer is defined as a role that authorizes the budget for a service and defines the service requirements. The customer is distinct from the user, who uses the service, and the sponsor, who authorizes the budget. The customer may be an individual, a department, or an entire organization. The customer's primary responsibilities include defining the outcomes that the service should achieve, agreeing on service level targets, and authorizing the expenditure for the service. In a formal service management system, the relationship between customer and service provider is often governed by a service level agreement (SLA). The SLA documents the agreed service targets, such as availability, performance, and response times. The customer also participates in service reviews to assess whether the service continues to meet requirements. In ITIL 4, the customer role appears in several key practices. In service level management, the customer negotiates and agrees on service level agreements. In relationship management, the provider maintains a positive relationship with the customer to understand changing needs. In supplier management, the customer may act as the point of contact for external suppliers. In business relationship management, a dedicated manager ensures the provider understands the customer's business context. In the service value system, customer feedback is a key input for continual improvement. The customer can also be internal, such as a business unit within the same organization that consumes IT services. In that case, the relationship is still managed formally, often with internal chargeback or showback models. In real IT environments, the customer role is implemented through processes like demand management, where the customer submits requests for new services or changes, and portfolio management, where the customer helps prioritize which services to invest in. The customer may also approve major incidents or changes that affect service delivery. In DevOps and Agile contexts, the customer is sometimes represented by a product owner who defines user stories and priorities. However, in ITIL terms, the product owner is a specific role that may act on behalf of the customer. The technical implementation of customer management often involves customer relationship management (CRM) tools, service catalogs, and portal systems where customers can view services, submit requests, and track progress. Authentication and authorization mechanisms ensure that only authorized customers can approve expenditures or change requirements. In regulated industries, audit trails of customer approvals are critical. Overall, the customer role is a cornerstone of service management because it aligns IT services with business needs and ensures that resources are spent on what the organization truly requires.

## Real-life example

Imagine a public library. The library offers services like borrowing books, using computers, and attending reading programs. The customer of the library is not necessarily the person who sits down to read a magazine. The customer is the city government that funds the library. The city council decides on the budget, sets the hours of operation, and determines which services the library should offer. The city council is the customer because it defines the requirements and authorizes the money. The people who walk into the library and borrow books are the users. They benefit from the service but they do not pay directly for it. Now inside the library, there is also a separate customer relationship for specific services. For example, the library might have a children's reading program. The children's program coordinator might be the customer for the IT department's e-book lending service. The coordinator decides that the library needs to offer e-books for children, negotiates with the IT department for the software, and approves the budget from the library's operating funds. The children who borrow the e-books are the users. This analogy maps directly to IT service management. In an organization, the IT department is like the library staff. The business unit that funds the IT services, such as the marketing department, is like the city council. The marketing manager is the customer who defines what the marketing automation software should do and approves the spending. The marketing team members who use the software daily are the users. If the software goes down, the users complain to the IT help desk, but the customer, the marketing manager, wants to know why the service failed and what is being done to restore it. The manager also wants to know how the outage affected the department's ability to meet its goals. This relationship ensures that IT services are aligned with business outcomes, not just user convenience. The library example also shows that one person can play multiple roles. A city council member might also borrow books from the library, making them both a customer and a user at different times. In IT, a department head might use the email system as a user but also be the customer for a new billing system. Understanding these roles helps everyone communicate clearly and assign responsibility correctly.

## Why it matters

In real IT work, clearly identifying the customer is essential for delivering services that actually meet business needs. Without a clear customer, IT teams might build services based on what they think users want, only to find that the business leaders who control the budget are not satisfied. This leads to wasted resources, rework, and frustrated stakeholders. For example, a system administrator might set up a file server with high-speed storage because users ask for fast performance, but the customer, the finance director, might care more about cost control and compliance with data retention policies. If the administrator does not understand the customer's priorities, the service may be too expensive or non-compliant. In cloud infrastructure, the customer role is critical for cost management. The customer approves the budget for cloud resources, so they need to understand the trade-offs between performance and cost. A cloud architect must present options to the customer, such as using reserved instances versus on-demand instances, and get a decision. In cybersecurity, the customer defines the security requirements. They might mandate that all data must be encrypted at rest and in transit. The security team then implements those controls. Without customer input, security measures might be too weak or too restrictive, both of which are bad for the business. In system administration, the customer often submits requests through a change management process. For example, a customer might request a new virtual machine for a project. The system administrator provisions the VM according to the customer's specifications, such as operating system, memory, and storage. The customer then accepts the service and pays for it through internal chargeback. This formal process ensures accountability. In service management, the customer is also the point of escalation for major issues. If an incident affects multiple users, the service desk might communicate with the customer about business impact and recovery plans. This helps the organization manage its reputation and prioritize recovery efforts. In regulated industries, the customer must approve any changes that affect compliance, such as modifying audit logs or access controls. Understanding the customer role helps IT professionals communicate more effectively with business leaders, justify budgets, and demonstrate the value of IT services. It also supports continual improvement because customer feedback provides direction for where to invest next.

## Why it matters in exams

In ITIL 4 and related certification exams, the term customer appears frequently, especially in the ITIL 4 Foundation exam and the ITIL Managing Professional modules. The ITIL 4 Foundation exam tests the candidate's understanding of the four dimensions of service management, the service value system, and key roles including customer, user, and sponsor. A typical question might ask: Which role is responsible for defining the requirements for a service and authorizing the budget? The answer is customer. Another common question presents a scenario where a department head agrees to a service level agreement for a new application. The candidate must identify the role as customer. The Linux Plus exam (CompTIA Linux+ XK0-005) does not directly test service management roles, but the term customer may appear in the context of IT operations and support. For example, in Linux system administration, a customer might be an internal department that requests a new server or application. The administrator must understand the customer's requirements to configure the system correctly. Exam questions might ask about service management practices or incident management where the customer role is relevant. In CompTIA IT Fundamentals (ITF+), the concept of customer versus user is tested in basic IT concepts. The Cisco CCNA and CompTIA Network+ exams do not focus on service management roles, but they may reference customer in the context of network service agreements or support contracts. For the ITIL 4 exam, candidates should memorize the official definitions: customer is the person who defines the requirements and agrees to pay; user is the person who uses the service; sponsor is the person who authorizes the budget. These definitions are strict, and exam questions often test the differences. A typical exam trap is when a question describes a person who uses the service and also approves the budget. Many candidates choose user, but the correct answer is that the person is acting as both user and customer if they also define requirements and authorize budget. In the ITIL 4 Foundation exam, there is usually at least one question that presents a scenario with multiple actors and asks to identify the customer. In the ITIL 4 Direct, Plan and Improve (DPI) module, the customer role is discussed in the context of strategy and planning. Understanding the customer helps in defining value and in designing service level agreements. In all cases, exam questions are scenario-based and require careful reading to distinguish between roles.

## How it appears in exam questions

In certification exams like ITIL 4 Foundation, questions about customer often appear in scenario-based formats. A common pattern is to describe a situation with three people: Alice defines the service requirements and approves the budget, Bob uses the service daily, and Carol is the IT manager who builds the service. The question then asks: Who is the customer? The answer is Alice. Another pattern is a question that lists activities and asks which activity is the responsibility of the customer. Options might include: fixing a service outage, using the service, defining service requirements, or installing software. The correct answer is defining service requirements. In more advanced ITIL exams like Service Transition or Service Operation, questions may ask about the customer's involvement in change management or incident management. For example: During a major incident, who should be updated on the business impact? The customer. In service level management questions, the customer is the party that agrees to the SLA targets. A question might ask: Who approves the service level agreement? The customer and the service provider. In configuration management questions, the customer might be the requester of a new configuration item. The candidate must understand that the customer specifies the requirements, but the provider configures the actual item. In Linux Plus questions, the term customer may appear in troubleshooting scenarios. For example: A customer reports that a Linux server is running slowly. What should the administrator check first? The question tests the technician's ability to gather information from the customer and then diagnose the issue. The customer here is the person who reported the issue, and the technician must distinguish between customer reports and actual system metrics. In scenario questions, candidates may be given a description of an organization and asked to identify who the customer is for a specific service. For example: A school district purchases a student information system. The district's IT director defines the requirements, the superintendent approves the budget, and teachers use the system to record grades. Who is the customer? The IT director might seem like the customer because they define requirements, but the superintendent authorizes the budget. According to ITIL, the customer is the one who defines requirements and agrees to pay, so both the IT director and the superintendent could be customers depending on the exact definitions. However, in most official ITIL questions, the customer is the person who defines requirements and authorizes the budget. So the superintendent would be the customer, and the IT director would be a user or a technical liaison. The exam may also present a trick where the same person plays multiple roles, and the candidate must choose the best answer for the role being asked. Another pattern is a question about the service value system: What role does the customer play in the service value chain? The customer triggers demand for services and provides feedback on value. These questions test the candidate's understanding of the customer's position in the overall framework.

## Example scenario

A medium-sized company, GreenLeaf Landscaping, wants to implement a new time-tracking system for its field workers. The CEO, Maria, decides that the company needs a mobile app that workers can use to log hours from their phones. Maria tells the IT manager, James, what features are needed: clock in and out, GPS location, and integration with payroll. Maria approves a budget of ten thousand dollars for the project. James then works with a software vendor to build and configure the app. After the app is deployed, the field workers, like Tom the gardener, use it every day to record their hours. In this scenario, Maria is the customer because she defined the requirements and authorized the budget. James is the service provider (or part of the provider team). Tom is the user. When the app has a bug that prevents clocking in, Tom reports it to James. James fixes the bug, but he also notifies Maria that the bug has been resolved. Maria is the customer, so she needs to know that the service is running correctly because the company's payroll depends on it. If James had only fixed the bug without telling Maria, she might not know that the issue was resolved, which could affect her trust in IT. By recognizing Maria as the customer, James ensures that business communication is complete and that the service continues to deliver value to the organization. This scenario shows how the customer role drives requirements, budget, and service review, while the user role focuses on daily interaction with the service.

## Common mistakes

- **Mistake:** Thinking the customer is always the person who uses the service.
  - Why it is wrong: In IT service management, the customer is the person who defines requirements and pays, not necessarily the end user. Users are a separate role.
  - Fix: Always ask: Who defines what the service should do and who approves the money? That person is the customer. The person who clicks buttons in the software is the user.
- **Mistake:** Believing the customer and the sponsor are the same role.
  - Why it is wrong: In ITIL 4, the sponsor authorizes the budget, while the customer defines requirements and agrees to pay. They can be the same person but are distinct roles with separate responsibilities.
  - Fix: If a question asks for the role that sets requirements, choose customer. If it asks who approves funding, choose sponsor. If one person does both, they are acting as both roles.
- **Mistake:** Mistaking the service desk for the customer.
  - Why it is wrong: The service desk is part of the service provider, not the customer. The service desk interacts with users and customers, but it does not define requirements or pay for services.
  - Fix: Remember: The service desk is like the pizza delivery driver. The customer is the one who ordered and paid. The driver delivers, but does not define the pizza toppings.
- **Mistake:** Assuming that an internal department cannot be a customer.
  - Why it is wrong: In ITIL, the customer can be internal to the same organization. For example, the HR department is the customer for the IT team that provides HR software. Internal customers are very common.
  - Fix: Treat internal departments exactly like external customers. They define requirements, agree on service levels, and have a budget. Do not underestimate their role just because they are inside the company.
- **Mistake:** Confusing the customer with the project manager.
  - Why it is wrong: The project manager coordinates the delivery of a project but does not define the service requirements or authorize the budget. The customer does that.
  - Fix: Think of the customer as the boss who says 'I need this service by this date with these features.' The project manager takes that input and plans the work.

## Exam trap

A scenario describes a person who uses a service and also approves the budget. The question asks: Who is the user? The candidate picks that person, but the correct answer is that the person is both user and customer, and the question may require identifying the user role specifically, leading to confusion. Read the question carefully. If it asks 'Who is the user?', look for the person who actually uses the service, regardless of other roles they may have. If it asks 'Who is the customer?', look for the person who defines requirements and agrees to pay. In exam scenarios, one person can hold multiple roles, so answer based on the specific role the question asks for, not on the combination of roles.

## Commonly confused with

- **Customer vs User:** The user is the person who uses the service on a daily basis. The customer is the person who defines requirements and pays for the service. A user may never pay for the service, and a customer may never use it. For example, a school buys a learning management system: the school administration is the customer, and the students are the users. (Example: In a company, the sales team uses the CRM software (they are users). The sales director approved the budget and chose the CRM features (they are the customer). They could be the same person if the director also uses the CRM, but the roles are distinct.)
- **Customer vs Sponsor:** The sponsor is the person or group that authorizes the budget for a service. The customer defines the requirements and agrees to pay. In many organizations, the sponsor and customer are the same person, but they can be different. For instance, a department head (customer) defines what is needed, and the CFO (sponsor) approves the funding. (Example: A marketing manager wants a new email marketing tool (customer). The company's finance director approves the purchase order (sponsor). The marketing team uses the tool (users).)
- **Customer vs Provider:** The provider is the person or organization that delivers the service. The customer is the one who receives the service and pays for it. The provider could be an internal IT department or an external vendor. The provider's job is to meet the customer's requirements. (Example: An IT company, TechServe, provides cloud storage to a law firm. TechServe is the provider. The law firm's managing partner is the customer. The lawyers are the users.)
- **Customer vs Service Owner:** The service owner is a role within the provider organization who is accountable for the end-to-end delivery of a specific service. The customer is external to the provider and defines requirements. The service owner manages the service to meet the customer's expectations. (Example: For an email service, the service owner at the IT department ensures uptime and performance. The customer is the business unit that pays for the email service and sets requirements like mailbox size and retention policies.)

## Step-by-step breakdown

1. **Identify the service need** — The customer recognizes a business need that can be addressed by an IT service. For example, the sales department needs a customer relationship management (CRM) system to track leads. The customer defines the high-level outcomes required, such as better lead conversion and reporting.
2. **Define requirements** — The customer specifies the functional and non-functional requirements for the service. This includes features, performance, security, and availability. In the CRM example, requirements might include integration with email, mobile access, and 99.9% uptime. The customer documents these in a service request or requirements document.
3. **Authorize budget** — The customer or sponsor approves the budget for the service. The customer agrees to pay for the service either through a direct budget allocation or an internal chargeback model. This step ensures that resources are committed and the service can be designed and delivered.
4. **Agree on service level agreement** — The customer works with the service provider to agree on a service level agreement (SLA). The SLA documents the agreed targets for availability, performance, response times, and other metrics. Both parties sign the SLA, making it a formal commitment.
5. **Service design and transition** — The provider designs the service based on the customer's requirements and SLA. During transition, the service is built, tested, and deployed. The customer may review and accept the service during user acceptance testing (UAT) before it goes live.
6. **Service delivery and support** — The service is delivered to users. The customer monitors the service against SLA targets. If issues arise, the customer may escalate to the provider. The customer participates in regular service review meetings to assess performance and value.
7. **Continual improvement** — Based on feedback from users and the customer, the provider makes improvements to the service. The customer may request changes to the service, such as new features or increased capacity. The customer approves any changes that affect the budget or service scope.

## Practical mini-lesson

In IT service management, the customer role is foundational because it connects IT services to business value. As a professional, you must always know who your customer is for each service you support. This is not always obvious. In a typical organization, the customer might be a department head, a project sponsor, or a procurement manager. When you start a new project or service, the first step is to ask: Who defines the requirements and who pays? That is your customer. Once you know the customer, you need to establish a relationship. In practice, this means scheduling regular meetings to understand their business goals and pain points. You should document their requirements in clear, measurable terms. For example, instead of 'the system should be fast', agree on 'the system should respond in under two seconds for 95% of requests'. This becomes the basis for your SLA. In real IT environments, you will often manage multiple customers simultaneously. For instance, a cloud administrator might support a marketing department customer and a finance department customer. Each has different requirements and budgets. The marketing customer might prioritize uptime for campaign tools, while the finance customer might prioritize security for financial data. You must configure services differently for each. When things go wrong, such as a server outage, you need to communicate with the customer appropriately. Do not just tell them technical details like 'the SQL server crashed'. Instead, tell them the business impact: 'The invoice generation service will be unavailable for two hours, which may delay payments to suppliers.' This shows that you understand their priorities. In change management, the customer must approve changes that affect their service. For example, if you need to apply a security patch that requires a server reboot, you must get approval from the customer who owns that server. They may have to schedule the reboot outside business hours to minimize impact. In DevOps environments, the customer is often represented by a product owner who sits in the same team. But the product owner's role is to prioritize the backlog, not necessarily to approve budgets. In that case, the true customer might be a senior manager who funds the product. So even in Agile teams, understanding the difference between the product owner and the actual customer helps in making financially informed decisions. A common mistake is to treat every request as equal. Requests from customers carry more weight because they have authority over the budget. If a user asks for a new feature, you might implement it only if the customer confirms it is a priority. This prevents scope creep and keeps the service aligned with business goals. In summary, to apply the customer concept in practice: identify the customer, establish clear agreements, communicate in business terms, and always align service delivery to customer-defined outcomes.

## Memory tip

Remember: Customer Commands and Cash. The Customer Commands (sets requirements) and provides Cash (budget). The User Uses. The Sponsor Signs the check.

## FAQ

**Can one person be both a customer and a user?**

Yes. For example, a department head may use the company email system (user) and also be the customer for a new billing system. In ITIL, roles are fluid. The important thing is to identify which role the person is playing in a given context.

**Is the customer always external to the IT department?**

No. The customer can be internal, such as another department within the same organization. Internal customers are common. They still define requirements and have a budget, even if the money is not exchanged directly.

**What is the difference between customer and client?**

In ITIL, customer is the preferred term. Client is more commonly used in business or legal contexts. They are essentially the same concept: the party that receives services and pays for them.

**Does the ITIL Foundation exam test the customer role?**

Yes. The ITIL 4 Foundation exam includes questions about the roles of customer, user, and sponsor. You need to know the official definitions and be able to apply them in scenarios.

**How do I identify the customer in a complex organization?**

Ask two questions: Who decides what the service should do? Who pays for the service? The answer to both is usually the customer. If different people answer each question, the person who decides on requirements is the customer, and the person who pays is the sponsor.

**What happens if the customer is not clearly identified?**

Service delivery can become confused. Requirements may come from multiple people with conflicting priorities, and budget may not be secured. This often leads to project delays, wasted effort, and user dissatisfaction.

**Can a customer also be a provider?**

Yes, in the sense of a service relationship chain. For example, the IT department is a provider to the marketing department, but IT itself might be a customer to an external cloud vendor. Organizations often play both roles depending on the service.

## Summary

The term customer in IT service management refers to the person or organization that defines the requirements for a service and agrees to pay for it. This is a distinct role from the user, who uses the service, and the sponsor, who authorizes the budget. Understanding the customer is critical for aligning IT services with business needs, managing budgets, and ensuring that services deliver real value. In certification exams like ITIL 4 Foundation, you will encounter scenario questions that test your ability to identify the customer, distinguish them from users and sponsors, and understand their role in processes like service level management, change management, and continual improvement. Common mistakes include confusing the customer with the user or the sponsor, or assuming that only external parties can be customers. To remember the role, think of the customer as the person who holds the requirements and the purse strings. In practice, always identify your customer early, establish clear agreements, and communicate in business terms. This will help you deliver services that meet organizational goals and succeed in both your job and your certification exams.

---

Practice questions and the full interactive page: https://courseiva.com/glossary/customer