Metric Definition
Ratio of views vs tickets submitted
The ratio of knowledge base views to tickets submitted measures how many self-service article views occur for every new support ticket created. It is the core metric for evaluating whether your self-service content is effectively deflecting tickets and reducing the load on human agents.
7 min read
What is the ratio of views vs tickets submitted?
The ratio of views vs tickets submitted compares knowledge base article views to the number of new support tickets created in the same period. A ratio of 50:1 means that for every support ticket submitted, there were 50 knowledge base article views. The higher the ratio, the more self-service activity is occurring relative to human-assisted support.
This metric matters because it quantifies self-service effectiveness at the most fundamental level. A knowledge base exists to answer customer questions without requiring a support agent. If the ratio is low, either customers are not finding the knowledge base, the content is not resolving their questions, or both. If the ratio is high and trending upward, the self-service investment is working.
The ratio also provides financial context. Every ticket that is deflected by self-service avoids the cost of agent handling, which typically ranges from 3 to 15 pounds per ticket depending on complexity and channel. If a knowledge base improvement increases the ratio from 30:1 to 40:1, it means a meaningful reduction in ticket volume and support cost, even if the absolute number of knowledge base views stays the same.
Importantly, this ratio should be interpreted alongside content quality metrics. A high ratio is only valuable if the knowledge base views are actually resolving customer issues. If customers view articles but still submit tickets because the content is unhelpful, the ratio overstates the effectiveness of self-service. Pair this metric with the percentage of positive votes and the ticket deflection rate for a complete picture.
A rising ratio is generally positive, but investigate sudden spikes. A major product outage can drive a surge in knowledge base views without any improvement in content quality. Likewise, a drop in tickets because of a holiday period will inflate the ratio temporarily. Look at the trend over multiple periods rather than single data points.
How to calculate the ratio
The base calculation is a simple division, but the insight comes from how you segment the ratio. Different product areas, customer segments, and issue types will have very different ratios, and these differences reveal where self-service is working and where it is failing.
| Segmentation | What it reveals | Typical action |
|---|---|---|
| Overall ratio | High-level health of the self-service programme | Report to leadership as a headline operational metric |
| Ratio by product area | Which product areas have adequate self-service coverage and which do not | Prioritise content creation for product areas with the lowest ratios |
| Ratio by customer segment | Whether certain customer types rely more heavily on human support | Invest in targeted content and in-app guidance for segments with low ratios |
| Ratio by topic category | Which topic categories are well-served by self-service and which consistently generate tickets | Focus content improvement on categories where the ratio is lowest despite adequate article coverage |
Views-to-tickets ratio in a metric tree
The ratio of views to tickets decomposes into two sides: the numerator (knowledge base views) and the denominator (ticket volume). Improving the ratio requires either increasing effective self-service views, decreasing avoidable tickets, or both.
The tree reveals that improving the ratio is not simply about writing more articles. The content effectiveness branch shows that views only reduce tickets if the content actually resolves the customer's question. The channel routing branch highlights that the path to ticket submission itself can include self-service checkpoints that deflect a portion of would-be tickets.
When the ratio declines, the tree guides diagnosis. If knowledge base views dropped, the problem is discoverability or content supply. If ticket volume increased without a corresponding rise in views, the problem may be a new product issue that has no self-service coverage yet. If both views and tickets rose but tickets rose faster, the content is not keeping pace with demand.
Views-to-tickets ratio benchmarks
| Company type | Typical ratio | What it indicates |
|---|---|---|
| Early-stage SaaS with basic help centre | 5:1 to 15:1 | Limited content library. Self-service not yet established as a primary support channel. |
| Growth-stage SaaS with dedicated content team | 20:1 to 50:1 | Meaningful self-service adoption. Content covers common issues but gaps remain. |
| Mature SaaS with comprehensive self-service | 50:1 to 200:1 | Self-service is the dominant support channel. Most common issues are well-covered by content. |
| Consumer products with large user bases | 100:1 to 500:1 | High self-service adoption driven by scale. Ticket submission reserved for complex or account-specific issues. |
The ideal ratio depends on your product complexity and customer base. A complex enterprise product with high-touch support expectations will naturally have a lower ratio than a consumer tool with millions of users. Track your own ratio over time rather than targeting an absolute benchmark.
How to improve the views-to-tickets ratio
- 1
Intercept ticket creation with self-service suggestions
When a customer starts to create a ticket, analyse their subject line or description and suggest relevant knowledge base articles before they submit. This is the highest-impact intervention because it reaches customers at the exact moment they are about to create a ticket and offers an immediate alternative.
- 2
Close content gaps for high-ticket-volume topics
Map your top ticket categories to existing knowledge base articles. For any category where articles are missing or have low positive vote rates, create or rewrite content. Each gap closed can deflect a measurable percentage of tickets in that category.
- 3
Improve content discoverability through search and in-app links
The best article in the world cannot deflect tickets if customers cannot find it. Optimise article titles and content for the terms customers actually use, improve internal search relevance, and embed contextual help links in the product at the points where users encounter problems.
- 4
Deploy a chatbot as a self-service front door
A well-configured chatbot can understand customer intent and serve relevant knowledge base articles conversationally, often resolving the issue without the customer needing to search the help centre themselves. This increases effective self-service coverage without requiring the customer to change their behaviour.
- 5
Track and act on the ratio at the topic level
The overall ratio hides variation across topics. Some categories may have a 200:1 ratio while others have 5:1. Focus improvement efforts on the categories with the lowest ratios, where self-service is failing and tickets are flowing to agents. Improving the worst-performing categories has a disproportionate impact on the overall ratio.
Related metrics
Customer Satisfaction Score
CSAT
Product MetricsMetric Definition
CSAT = (Satisfied Responses / Total Responses) × 100
Customer satisfaction score measures how satisfied customers are with a specific interaction, product, or experience. Unlike NPS which measures loyalty, CSAT captures satisfaction at a moment in time, making it ideal for evaluating specific touchpoints in the customer journey.
Customer Effort Score
CES
Product MetricsMetric Definition
CES = Sum of All Effort Ratings / Number of Responses
Customer effort score measures how much effort a customer had to exert to accomplish a goal with your product or service. Research shows that reducing effort is more predictive of customer loyalty than increasing satisfaction, making CES a powerful complement to NPS and CSAT.
First Contact Resolution
Support effectiveness
Operations MetricsMetric Definition
FCR Rate = (Issues Resolved on First Contact / Total Issues Handled) × 100
First contact resolution measures the percentage of customer enquiries resolved during the first interaction without requiring follow-up contacts, transfers, or escalations. It is the single most influential metric for customer satisfaction in support operations.
Net Promoter Score
NPS
Product MetricsMetric Definition
NPS = % Promoters - % Detractors
Net Promoter Score measures customer loyalty by asking how likely a customer is to recommend your product or service. It is the most widely used customer experience metric, providing a single number that captures sentiment and predicts growth through word-of-mouth.
Measure the true impact of your self-service investment
Build a metric tree that connects knowledge base views, ticket volume, and content quality so you can quantify how much your self-service content is reducing support costs.
