Customer Satisfaction

What Is Customer Satisfaction?

Customer Satisfaction (CSAT) is a metric that measures how well IT services, support interactions, or service desk experiences meet or exceed the expectations of end users—whether employees, customers, or external stakeholders. In ITSM and ESM contexts, CSAT is typically captured through post-interaction surveys that ask users to rate their experience on a numerical scale (often 1–5 or 1–7) immediately after a ticket is resolved, a request is fulfilled, or a service is delivered. The resulting score reflects the user's perception of service quality, responsiveness, and resolution effectiveness at a specific moment in time, making it a transactional measure rather than a longitudinal one. Unlike Net Promoter Score (NPS), which gauges long-term loyalty and likelihood to recommend, or Customer Effort Score (CES), which measures ease of resolution, CSAT focuses narrowly on satisfaction with a single service event.

Why Customer Satisfaction Matters

Customer Satisfaction directly influences service desk performance, user adoption of self-service portals, and the credibility of IT as a business enabler. High CSAT scores correlate with lower ticket escalation rates, reduced repeat contacts, and stronger trust between IT and business units—critical factors when extending service management to HR, Facilities, Finance, or other ESM domains. Low CSAT, conversely, signals friction in workflows, inadequate knowledge base content, poor communication during incidents, or misaligned SLAs, all of which erode productivity and increase operational costs. For organizations running ITIL-aligned processes, CSAT serves as a key performance indicator (KPI) for Incident Management, Service Request Management, and Continual Improvement, providing actionable feedback that informs process tuning, agent training, and automation priorities. In incident response and on-call scenarios, CSAT also reflects stakeholder confidence in transparency and communication quality during outages, directly impacting business continuity perception.

How Customer Satisfaction Works

CSAT measurement begins when a service interaction concludes—typically triggered automatically by an ITSM platform when a ticket status changes to "Resolved" or "Closed." The system sends a brief survey to the requester, usually via email or in-app notification, asking a single question such as "How satisfied were you with the resolution of your issue?" accompanied by a rating scale. Responses are collected in real time and aggregated into a percentage score (the proportion of respondents selecting "satisfied" or "very satisfied" ratings) or an average score across all responses. Modern ITSM platforms often embed CSAT collection directly into ticket workflows, allowing service desk managers to filter scores by agent, category, priority, or time period to identify trends and outliers. Advanced implementations use AI-driven sentiment analysis on optional free-text comments to surface recurring pain points—such as slow response times, unclear communication, or incomplete resolutions—that numeric scores alone may not reveal. CSAT data feeds into dashboards alongside MTTR, First Contact Resolution (FCR), and SLA compliance metrics, enabling service owners to correlate satisfaction with operational performance and prioritize improvements that deliver measurable impact on user experience.

Examples of Customer Satisfaction

-  Enterprise IT Service Desk : A global manufacturing company uses CSAT surveys after every password reset, software installation, and hardware request. When scores drop below 80% for a specific request type, the service desk manager reviews ticket notes and discovers that users are frustrated by a lack of proactive status updates. The team implements automated notifications at each workflow stage, and CSAT for that category rises to 92% within two months.

-  SaaS Platform Incident Response : A cloud software provider tracks CSAT after every major incident by surveying customers who subscribed to status page updates. Following a database outage, CSAT scores reveal that customers appreciated the transparency of real-time incident timelines but were dissatisfied with the lack of estimated resolution times. The SRE team adjusts their incident communication playbook to include ETAs in all status updates, improving post-incident CSAT by 15 percentage points.

-  HR Service Management (ESM) : A multinational corporation extends ITSM practices to HR by deploying a service catalog for onboarding, benefits enrollment, and policy inquiries. CSAT surveys sent after each HR case closure show that new hires rate onboarding requests highly (95% satisfaction) but benefits inquiries score only 68%. Analysis reveals that benefits cases frequently require multiple back-and-forth emails. HR implements a guided self-service form with conditional logic, reducing effort and raising CSAT to 89% within one quarter.

Related Terms

- First Contact Resolution
- Service Level Agreement
- Incident Management
- Service Request Management
- Knowledge Management

---

Frequently Asked Questions

• What's the right survey response rate threshold before CSAT scores become statistically meaningful for decision-making?
  Most service desk teams treat response rates below 20% as unreliable for category-level decisions, since low volume amplifies the impact of outlier scores and skews trend analysis. Segment your CSAT data by ticket volume first—high-volume categories like password resets can tolerate lower response rates than low-volume categories like executive support, where even five negative responses can misrepresent actual performance. Increase response rates by shortening survey delivery windows to within one hour of ticket closure rather than end-of-day batch sends.
• Who should own CSAT targets and accountability—the service desk manager, the process owner, or the business unit being served?
  CSAT targets work best when the process owner sets the baseline threshold and the service desk manager owns operational accountability for hitting it, but business unit leads should co-sign targets for ESM domains like HR or Facilities where IT has limited control over resolution quality. Without business unit buy-in, IT absorbs blame for satisfaction gaps caused by upstream policy decisions or staffing constraints outside its control. Establish a shared governance cadence—monthly at minimum—where both parties review scores and agree on improvement actions.
• Can CSAT scores actually go negative in terms of impact—where collecting them makes satisfaction worse?
  Survey fatigue is a real failure mode: users who receive a CSAT survey after every single interaction, including trivial ones like notification acknowledgments, begin ignoring or resenting the surveys, which depresses response rates and skews scores toward only the most frustrated respondents. Limit survey triggers to interactions with meaningful resolution effort—set ticket complexity or time-to-resolve thresholds below which surveys don't fire. Audit your survey trigger logic quarterly to ensure you're measuring service quality, not just generating noise.
• How should teams handle CSAT scores for tickets that were resolved correctly but the user is unhappy with the outcome—like a denied software request?
  Policy-driven dissatisfaction—where the resolution was technically correct but the user wanted a different outcome—contaminates your CSAT signal if you don't tag and segment it separately from process-driven dissatisfaction. Create a ticket category flag for "policy denial" or "out-of-scope request" and exclude or isolate those CSAT responses when evaluating agent performance or workflow quality. Use the free-text comments from those tickets to feed a separate review loop with business stakeholders who own the underlying policy, not the service desk team.
• When extending CSAT measurement into new ESM domains like Legal or Finance, what's the biggest mistake teams make in the rollout?
  Teams routinely import the same survey scale and question wording from IT without adapting it to the domain's service norms, which produces scores that don't reflect the actual drivers of satisfaction in that department—Legal users, for example, weight confidentiality and precision far more heavily than speed. Conduct a brief stakeholder interview with the domain lead before launching surveys to identify the two or three satisfaction drivers most relevant to that function, then validate that your survey question captures them. Launch with a 60-day pilot and compare CSAT trends against ticket reopen rates to confirm the survey is measuring what actually matters to that business unit.