What support metrics should a SaaS company track?

SaaS support metrics are measures of customer outcomes, response speed, workload, service quality, self-service performance and business impact.

If you are building one support dashboard, start with these five metrics:

1. First-contact resolution rate
2. Full resolution time
3. CSAT
4. Backlog volume and age
5. Support contact rate per active account or user

These metrics show whether customers receive effective help. First response time measures how quickly support replies, but it does not show whether the issue was solved. Zendesk separates first reply time from first and full resolution time, while Intercom separates first response time from time to close.

SaaS Support Metrics at a Glance

Metric	What it measures	Why SaaS companies should track it
First-contact resolution rate	Issues solved in one interaction	Shows whether support resolves problems efficiently
Full resolution time	Time from ticket creation to final resolution	Shows how long customers actually wait
First response time	Time until the first human response	Measures responsiveness and staffing coverage
CSAT	Customer satisfaction after a support interaction	Shows how customers rate the experience
Customer Effort Score	How easy it was to get help or solve an issue	Reveals friction in the support process
Reopen rate	Solved tickets that customers reopen	Detects incomplete or inaccurate resolutions
SLA attainment	Tickets that meet response or resolution targets	Measures performance against service commitments
Backlog volume and age	Unresolved workload and time spent open	Reveals capacity problems and neglected cases
Support contact rate	Requests relative to active users or accounts	Shows product friction independently of growth
Escalation rate	Cases sent to senior teams or engineering	Identifies complexity, defects and training gaps
Self-service success rate	Issues resolved through content or automation	Shows whether self-service reduces human demand
Cost per resolution	Fully loaded cost of each resolved issue	Connects support performance to SaaS economics

1. Which Customer Outcome Metrics Should a SaaS Company Track?

The main customer outcome metrics are first-contact resolution rate, full resolution time and reopen rate.

First-Contact Resolution Rate

First-contact resolution rate is the percentage of support issues solved without another interaction, transfer or reopen.

First-contact resolution rate =
Issues resolved in the first interaction ÷ Total resolved issues × 100

Define "first contact" in the same way across email, chat, phone and messaging. For example, a SaaS company might count a case as first-contact resolved when the customer does not reply, reopen the ticket or contact support again about the same issue within seven days.

FCR combines speed, accuracy and customer effort. A team can reply quickly and still create a poor experience if the customer needs several follow-ups.

Track FCR by:

• Product area
• Ticket category
• Customer segment
• Support channel
• Agent or team
• New and experienced customers

Full Resolution Time

Full resolution time measures the time required to solve a support issue completely.

Full resolution time =
Time from ticket creation to final resolution

Use the median as the main measure and the 90th percentile to find long-running cases. Report business hours and calendar hours separately when the support team works to a schedule.

Also decide whether the measure includes time spent waiting for:

• The customer
• Engineering
• A third-party provider
• Internal approval

Zendesk distinguishes first resolution time from full resolution time because a ticket can be marked solved and later reopened. This distinction matters for SaaS products that involve technical troubleshooting or engineering work.

Reopen Rate

Reopen rate is the percentage of solved tickets that customers reopen or return to within a defined period.

Reopen rate =
Reopened solved tickets ÷ Total solved tickets × 100

A rising reopen rate can point to:

• Incomplete answers
• Incorrect troubleshooting
• A product fix that did not solve the problem
• Unclear communication
• Tickets being closed too early

Review reopen rate alongside CSAT and resolution time. A short resolution time combined with a high reopen rate often means that agents are closing cases before the issue is settled.

2. Which Customer Experience Metrics Matter Most?

CSAT shows how customers rate a support interaction, while Customer Effort Score shows how difficult the interaction was.

Customer Satisfaction Score

CSAT measures how satisfied customers were with a specific support interaction.

CSAT =
Positive survey responses ÷ Total survey responses × 100

Set the positive-response rule before reporting the metric. For example, a five-point survey might count ratings of 4 and 5 as positive.

Report the survey response rate with the score. A CSAT result based on a small number of responses may not represent the wider customer base.

Track CSAT by:

• Issue type
• Channel
• Resolution time
• Agent or team
• Customer plan
• Product area
• Escalation status

Zendesk describes CSAT as a measure of satisfaction with support interactions and recommends reviewing it alongside response and resolution metrics.

CSAT should not carry the whole quality assessment. A customer may give a positive rating even when the underlying product problem remains. An unhappy customer may also ignore the survey.

Customer Effort Score

Customer Effort Score measures how easy it was for a customer to get help, complete a task or solve an issue.

A SaaS company might ask:

How easy was it to resolve your issue today?

Use one numerical scale and report either the average score or the percentage of low-effort responses.

CES can reveal friction in:

• Finding the right help article
• Contacting support
• Repeating information
• Following troubleshooting steps
• Escalating a technical problem
• Understanding the final answer

CSAT measures the customer's reaction to the interaction. CES measures the work the customer had to do. Use both when reviewing the support journey.

3. Which Responsiveness and Capacity Metrics Should a SaaS Company Track?

The main operational metrics are first response time, SLA attainment, backlog volume and backlog age.

First Response Time

First response time measures the time between a customer's request and the first public response from a human support agent.

First response time =
Time of first human reply − Time the customer submitted the request

Report the median and 90th percentile, then separate the results by channel. Live chat, email and phone support have different response expectations.

Track:

• Median first response time
• 90th percentile first response time
• First response time by channel
• First response time during and outside business hours
• Tickets receiving a response within the SLA

An automated acknowledgement should not count as a human first response. Zendesk defines first reply time around the first public agent response, and Intercom reports bot and teammate response behaviour separately.

A fast first reply is useful when it leads to progress. It should sit alongside FCR, full resolution time and CSAT rather than becoming the sole team target.

SLA Attainment

SLA attainment is the percentage of tickets that meet a promised response or resolution target.

SLA attainment =
Tickets meeting the SLA ÷ Tickets governed by the SLA × 100

Report response SLA and resolution SLA separately. A team may answer quickly while failing to resolve cases within the agreed period.

Segment SLA attainment by:

• Customer plan
• Severity
• Channel
• Issue type
• Business hours
• Support region

Define how pending, customer-waiting and engineering-waiting time affect the calculation. Without that rule, the metric can produce misleading comparisons.

Backlog Volume and Backlog Age

Backlog metrics show the number of unresolved cases and how long those cases have been open.

Track:

• Total open tickets
• Tickets older than 1, 3, 7 and 14 days
• Median ticket age
• Oldest unresolved ticket
• Backlog by priority
• Backlog by customer plan
• New tickets compared with resolved tickets

A growing backlog points to a capacity or process problem. An ageing backlog shows that certain customers or issue categories are waiting longer than others.

Backlog volume also needs a complexity check. Ten engineering cases do not represent the same workload as ten password-reset requests.

4. Which Demand and Product Metrics Should a SaaS Company Track?

The main demand metrics are support contact rate, ticket volume by topic and escalation rate.

Support Contact Rate

Support contact rate measures how often customers contact support relative to the number of active users or accounts.

Useful formulas include:

Contact rate per account =
Support conversations ÷ Active customer accounts

Contact rate per user =
Support conversations ÷ Monthly active users

Contact rate gives a clearer view than raw ticket volume when a SaaS company is growing. Ticket volume can rise because the customer base is larger. Contact rate shows whether each customer is generating more or fewer requests.

Compare the rate across:

• New and mature accounts
• Free, trial and paid plans
• Enterprise and self-serve customers
• Product versions
• Customer cohorts
• Features and integrations

A sudden increase after a product release can reveal friction before renewal or churn data shows a problem.

Ticket Volume by Topic and Product Area

Ticket volume by category shows which product problems, workflows and policies generate the most support demand.

Use a consistent taxonomy, such as:

• Billing
• Account access
• Onboarding
• Integrations
• API and developer tools
• Product defects
• Feature requests
• How-to questions
• Performance or reliability

Track the rate and severity of tickets by topic, rather than volume alone. A low-volume API outage may require more attention than a high-volume question about a minor interface change.

Send this data to product, engineering, documentation and onboarding teams. The value comes from the decision it supports.

Escalation Rate

Escalation rate is the percentage of support cases transferred to a senior team, specialist or engineering.

Escalation rate =
Escalated cases ÷ Total support cases × 100

A high escalation rate can indicate:

• Product defects
• Missing documentation
• Frontline training gaps
• Complex integrations
• Poor routing
• Inadequate support tools

Track the destination, time to response and outcome of each escalation. An issue answered by engineering in two hours has a different operational effect from one that remains there for ten days.

5. Which Self-Service and Automation Metrics Should a SaaS Company Track?

Self-service metrics should show whether customers solve issues without human support and whether automation produces accurate resolutions.

Self-Service Success Rate

Self-service success rate measures how often customers find an answer or complete a task without opening a human support case.

Possible measures include:

• Help-centre sessions with no related ticket afterward
• Searches that lead to article engagement and no ticket
• Product walkthroughs completed without a support contact
• Automated troubleshooting flows completed successfully
• AI conversations resolved without human escalation

Set a time window, such as no related support contact within 24 or 72 hours. A page view alone does not prove that the customer solved the problem.

Track failed searches and article exits as well. They show what customers are trying to do but cannot find or understand.

Automation Containment and Quality

Automation containment measures how often a bot or workflow handles a conversation without human involvement.

Containment needs quality checks. Pair it with:

• Reopen rate
• Escalation rate
• CSAT
• CES
• Repeat contact rate
• Resolution accuracy

Zendesk recommends reviewing resolution, satisfaction, effort, trust, cost per resolution and agent impact when measuring AI service quality. Speed and containment alone do not show whether customers received the right answer.

A bot can increase containment by making it harder for a customer to reach an agent. The useful question is whether the customer's issue was resolved.

6. Which Support Business Metrics Should a SaaS Company Track?

The main business metrics are cost per resolution and support activity linked with account retention and expansion.

Cost per Resolution

Cost per resolution estimates the fully loaded cost of solving one support issue.

Cost per resolution =
Total support operating cost ÷ Total resolved issues

Include relevant costs such as:

• Support salaries and benefits
• Contractor costs
• Support software
• Telephony and messaging
• Outsourced support
• Training
• Quality assurance
• Knowledge-base maintenance

Segment the result by customer plan, channel and issue type. This can show that a supposedly low-cost segment creates a high amount of support work.

Lower cost is useful only when resolution quality holds. Review cost per resolution with FCR, CSAT and full resolution time.

Support Activity Linked to Churn and Expansion

A SaaS company should connect support data with retention, expansion and churn without treating support activity as proof of cause.

Useful account-level indicators include:

• Unresolved high-severity cases before renewal
• Repeated contacts about the same issue
• A sudden increase in ticket volume
• Declining CSAT or CES
• Product areas linked to complaints
• Cases involving decision-makers or strategic accounts
• Resolution time for renewal-related issues

Review these indicators with product usage, account health, renewal dates and customer success activity. That creates a support-informed risk model instead of treating ticket volume as a churn forecast on its own.

The Recommended SaaS Support Scorecard

A monthly scorecard can group the metrics into four views:

Customer Outcomes

• First-contact resolution rate
• Full resolution time
• Reopen rate
• CSAT
• Customer Effort Score

Responsiveness and Capacity

• Median first response time
• SLA attainment
• Open backlog
• Backlog age
• Tickets resolved per support employee

Product and Demand

• Support contact rate per active account
• Ticket volume by category
• Escalation rate
• Repeat contact rate
• Failed self-service searches

Business Impact

• Cost per resolution
• Support cost per account
• High-risk accounts with unresolved cases
• Churn and renewal outcomes for accounts with substantial support activity

Report each metric by channel, customer segment, plan, severity and issue category. Company-wide averages can hide the customers and problems that need attention.

Bottom Line

A useful SaaS support measurement system connects four questions:

1. Did the customer receive a correct resolution?
2. How much effort and time did that resolution require?
3. What did it cost the company?
4. What does the pattern tell product, support and customer success teams to change?

Start with FCR, full resolution time, CSAT, backlog age and support contact rate. Add response, SLA, self-service and cost measures after the underlying data is consistent.