Getting started with self-service - Part 6: Tracking essential self-service metrics

Available on all Suite plans

Articles in the series

With your help center live (see Getting started with self-service - Part 6: Launching your help center), you should now start tracking the key self-service metrics that will help you determine how your help center is being used, how useful your articles are, and how you’re doing delivering self-service.

This article covers the following topics:

Calculating your self-service score
Connecting Google Analytics to your help center
Using the help center activity dashboards in Explore
Autoreplies activity

Calculating your self-service score

The success of your help center can be measured in a number of ways. You of course want to monitor the uptake in the use of your help center; how many views and users you’re getting per month. You should see an increase based on your efforts to promote your new self-service channel.

You can also compare your number of help center users to the number of tickets that were created in the same period of time. This is referred to as the self-service score (it’s also known as the self-service ratio and the ticket deflection ratio).

Self-service score = Total user sessions of your help center(s) / Total users in tickets

This formula gives you a ratio such as 4:1, meaning that for every four customers who attempt to solve their own issues using self-service, one customer submits a support request. Success here is demonstrated by an increasingly large ratio (for example, for every 40 users only one of them submits a ticket - 40:1 ratio).

To calculate your self-service score

Set up a Google Analytics account and connect it to Guide as described in Enabling Google Analytics for your help center.
When you have several months of user activity available in Google Analytics, take a 30-day snapshot (for example) of the number of visitor sessions in your help center.
Divide that number by the total number of users who have submitted tickets in that same time period. See Explore recipe: Finding how many users submit tickets each month.

Connecting Google Analytics to your help center

Your help center is like any other website in that you want to measure, in as much detail as possible, how it’s being used and where it needs to be improved. After you’ve connected Google Analytics to your help center, you can begin to analyze traffic, user engagement, and other typical website metrics.

Some of the metrics that you should consider tracking in Google Analytics include the following:

Users - Aside from helping you calculate your self-service score, the users metric also shows you the pages your visitors are accessing during their sessions, which gives you a fuller picture of how they’re engaging with your content.
Avg. Session Duration - A low average session duration may indicate that your visitors are not engaging with your content.
% New Sessions - This metric gives you insight into how many of your visitors are returning or new, which can help you determine the type of content you need to focus on (for example, providing more getting started content for new users).
Bounce Rate - A high bounce rate on your landing pages (category and section pages with the listings of your articles) could indicate that you either aren’t providing the content they need or that your article titles need to be improved.

There’s so much data you can track with Google Analytics that we recommend that you read the following series of articles to go in-depth on this subject.

Using the help center activity dashboards in Explore

Help center activity is tracked and is available in the Zendesk Guide dashboard in Explore. Activity is tracked for your knowledge base articles, search, bot and Knowledge Capture activity, and your community (if you’ve enabled a community using Zendesk Gather).

The data you’ll find in these three dashboards help you to analyze and improve how your help center and your content is performing. While all the data is interesting and important, several of them are good indicators that you need to make changes to your knowledge base content.

Knowledge Base activity

Statistics on this dashboard include the number of articles created, article views, and the total number of votes, subscriptions, and comments. Of these, article views, votes, and comments are of particular importance.

Views is the total number of views for articles in the knowledge base. You want to track this over time and see an increase in views. This can indicate how well you’re doing promoting and driving the use of your help center and knowledge base articles.
Net article votes is the difference of all the positive and negative votes on all articles. If you’re getting a high number of negative votes on your articles, that could indicate that they need to be updated and improved. On the other hand, a high number of positive votes indicates that an article is useful and is helping to deflect tickets.

Comments is the total number of comments on articles in the knowledge base. An article with many comments can indicate that the content is confusing or incomplete and requires your customers to ask follow-up questions.

For more information about this dashboard, see Analyzing knowledge base activity with Explore.

Search activity

Statistics on this dashboard include the total number of searches, searches with no results, searches with no clicks, and tickets created. The last three are particularly interesting because they indicate where you may have content gaps and that some articles are not getting the job done.

With no result is the number of searches that returned 0 results. What this tells you is that your customers are searching for something that is not included in your knowledge base. The search strings that are being used could be nonsense, therefore no results, or you need a new knowledge base article to provide the information they are looking for.
With no clicks is the number of searches where no result was selected. This might indicate a content gap (they searched for something, but nothing was available) or that you need to update the titles of your knowledge base articles (the article is there, but the title doesn’t contain the search term they’re using).
Tickets created is the number of searches that led to a ticket being created. Drilling down into the detail for this statistic, you can see each search term used that resulted in a ticket being created. Two things could likely be happening here. First, they searched for a term that had to result, so the customer immediately created a ticket to get the answer they needed. Second, they clicked into an article and for some reason needed more help from an agent, which might mean the article needs to add more information.

For each of these statistics, you can see the search strings that are being used. You might find that customers are using alternate terms (an old product name, the term one of your competitor’s uses for something you have a different name for) and common misspelled words. This is where using labels comes in very handy. You can add these alternate terms and misspellings as labels in your articles to improve the search results for your customers.

For more information about this dashboard, see Analyzing help center search results with Explore

Knowledge Capture activity

If you’re using Knowledge in the Context panel to create articles and enable your agents to link straight to your knowledge base content, reporting about its use is also available in the Guide reporting dashboard in Explore.

For more information about this dashboard, see Analyzing your Knowledge activity.

Community activity

Statistics on this dashboard include the number of posts created, how many users have viewed posts, and the total number of votes, subscriptions, and comments.

Because your community is there to also provide you with feedback, a community post could be telling you that you need to create a knowledge base article to address the subject.

For more information about this dashboard, see Analyzing community activity with Explore.

Autoreplies activity

Finally, if you’ve enabled a bot as part of your self-service channel, you can track your article recommendation activity.

You can discover if your articles are helping to resolve support issues by tracking if customers are clicking into them, how many issues were resolved without agent intervention, and also how many articles were marked as unhelpful. This data is the most direct source of information for determining if your self-service is doing its job and deflecting tickets.

For more information about this dashboard, see Analyzing article recommendations.