Analyzing the metrics that matter to improve customer support

<div class="article-banners">
<div id="docs-wmp-link"><a href="https://support.zendesk.com/hc/en-us/articles/5411234991258-plan" rel="noopener" target="_blank">What's my plan?</a></div>
<div class="article-banner" id="suite_all">
<table>
<tbody>
<tr>
<td>
<strong>All Suites</strong>
</td>
<td>Team, Growth, Professional, Enterprise, or Enterprise Plus</td>
</tr>
</tbody>
</table>
</div>
<div class="article-banner" id="support_with_explore_all">
<table>
<tbody>
<tr>
<td>
<strong>Support with</strong>
</td>
<td>Explore Light, Professional, or Enterprise</td>
</tr>
</tbody>
</table>
</div>
</div>
<div class="body">
<div class="bodydiv">
<p class="p">Using Explore, you can analyze your customer service experience to identify areas
where you're exceeding expectations and areas that might need improvement. You can
then use this information to improve the effectiveness of your team and your
customer support. </p>
<p class="p">Learn which metrics are important to monitor, how to report on them in Explore, what
trends to look for, and how to take action on this information.</p>
<p class="p">This article contains the following topics:</p>
<ul class="ul" id="topic_v1b_4zp_k5b__ul_ygm_4cq_k5b">
<li class="li"><a class="xref" href="#topic_twv_f1q_k5b">How many tickets are we solving?</a></li>
<li class="li"><a class="xref" href="#topic_bnf_31q_k5b">What are the most common ticket areas?</a></li>
<li class="li"><a class="xref" href="#topic_gvj_j1q_k5b">How much work do we have?</a></li>
<li class="li"><a class="xref" href="#topic_byc_k1q_k5b">How long do customers wait for a first reply?</a></li>
<li class="li"><a class="xref" href="#topic_a11_l1q_k5b">How long do tickets take to resolve?</a></li>
<li class="li"><a class="xref" href="#topic_fqt_l1q_k5b">How often are solved tickets reopened?</a></li>
<li class="li"><a class="xref" href="#topic_mzr_m1q_k5b">How satisfied are customers?</a></li>
<li class="li"><a class="xref" href="#topic_kdx_n1q_k5b">More resources</a></li>
<li class="li"><a class="xref" href="#topic_c5m_41q_k5b">Join the conversation!</a></li>
</ul>
</div>
</div>
<div aria-labelledby="ariaid-title2" class="topic nested1" id="topic_twv_f1q_k5b">
<h2 class="title topictitle2" id="ariaid-title2">How many tickets are we solving?</h2>
<div class="body">
<p class="p">The number of tickets solved gives you a quick indication of how your team is doing.
It's most useful for examining overall trends, as some tickets are quickly solved
while others take longer. Monitoring this metric over time helps you evaluate your
team's performance and decide your resourcing needs.</p>
</div>
<div aria-labelledby="ariaid-title3" class="topic nested2" id="topic_i42_t1q_k5b">
<h3 class="title topictitle3" id="ariaid-title3">Viewing prebuilt reports (Lite and Professional)</h3>
<div class="body">
<p class="p">The <a class="xref" href="https://support.zendesk.com/hc/en-us/articles/4408835846810#topic_hlj_xbj_z3b" target="_blank">Tickets tab of the Zendesk Support
dashboard</a> gives you an at-a-glance view of your solved, unsolved,
created, and reopened tickets.</p>
<p class="p"><img class="image img-screenshot" id="topic_i42_t1q_k5b__image_m12_qzp_k5b" src="https://zen-marketing-documentation.s3.amazonaws.com/docs/en/explore_metrics_matter_tickets_tab.png"></p>
<p class="p">Additionally, the <strong class="ph b">Assignee activity</strong> report on the <a class="xref" href="https://support.zendesk.com/hc/en-us/articles/4408835846810#topic_dpf_ybj_z3b" target="_blank">Assignee activity tab of the Zendesk Support
dashboard</a> shows your top ticket solvers, along with a wealth of other
information. </p>
<p class="p"><img class="image img-screenshot" id="topic_i42_t1q_k5b__image_ktg_vt5_q5b" src="https://zen-marketing-documentation.s3.amazonaws.com/docs/en/explore_assignee_activity_report.png"></p>
</div>
</div>
<div aria-labelledby="ariaid-title4" class="topic nested2" id="topic_n2d_51q_k5b">
<h3 class="title topictitle3" id="ariaid-title4">Creating your own reports (Professional)</h3>
<div class="body">
<p class="p">The <a class="xref" href="https://support.zendesk.com/hc/en-us/articles/4408827693594-Metrics-and-attributes-for-Zendesk-Support#topic_zlf_slp_4y" target="_blank">Tickets dataset</a> contains the metrics
and attributes you need to create your own reports about solved tickets.</p>
<p class="p">The following Explore recipes give you some great starting points for creating
your reports:</p>
<ul class="ul" id="topic_n2d_51q_k5b__ul_o12_qzp_k5b">
<li class="li"><a class="xref" href="https://support.zendesk.com/hc/en-us/articles/4408825110682" target="_blank">Reporting on created and solved
tickets</a></li>
<li class="li"><a class="xref" href="https://support.zendesk.com/hc/en-us/articles/4408838648602" target="_blank">Daily ticket activity in the last 30
days</a></li>
<li class="li"><a class="xref" href="https://support.zendesk.com/hc/en-us/articles/4408819446298" target="_blank">Solved tickets this year compared to last
year</a></li>
</ul>
<p class="p">For a full list of recipes, see <a class="xref" href="https://support.zendesk.com/hc/en-us/articles/4409149172890" target="_blank">Explore recipes reference</a>.</p>
</div>
</div>
<div aria-labelledby="ariaid-title5" class="topic nested2" id="topic_iz1_v1q_k5b">
<h3 class="title topictitle3" id="ariaid-title5">What to look for</h3>
<div class="body">
<p class="p">As you look at your reports, focus on the following information:</p>
<ul class="ul" id="topic_iz1_v1q_k5b__ul_q12_qzp_k5b">
<li class="li">The <strong class="ph b">Solved tickets</strong> metric for both the whole team and individual
agents.</li>
<li class="li">The average values over a period of time (for example, a month). Some days,
agents will be over or under the target.</li>
<li class="li">The number of solved tickets compared with the number of open tickets. This
shows how well the team is keeping up with the ticket queue.</li>
</ul>
</div>
</div>
<div aria-labelledby="ariaid-title6" class="topic nested2" id="topic_lz5_v1q_k5b">
<h3 class="title topictitle3" id="ariaid-title6">How to use the results</h3>
<div class="body">
<p class="p">The following table gives some examples of how you can use solved ticket reports
to help improve your team's efficiency:</p>
<div class="tablenoborder">
<table border="1" cellpadding="4" cellspacing="0" class="table" frame="border" id="topic_lz5_v1q_k5b__topic_fg5_fww_sjb__simpletable_kfp_3dt_tjb" rules="all" summary="">
<colgroup>
<col>
<col>
</colgroup>
<thead class="thead" style="text-align:left;">
<tr class="row">
<th class="entry nocellnorowborder" id="topic_lz5_v1q_k5b__d52e219">If you see this</th>
<th class="entry cell-norowborder" id="topic_lz5_v1q_k5b__d52e222">Do this</th>
</tr>
</thead>
<tbody class="tbody">
<tr class="row">
<td class="entry nocellnorowborder" headers="topic_lz5_v1q_k5b__d52e219">Ticket volumes are consistently high.</td>
<td class="entry cell-norowborder" headers="topic_lz5_v1q_k5b__d52e222">
<ul class="ul" id="topic_lz5_v1q_k5b__ul_s12_qzp_k5b">
<li class="li">Consider hiring more agents. Look for patterns of
particularly busy or quiet times and staff
accordingly.</li>
<li class="li">Consider more training for your agents.</li>
<li class="li">Look for common problem areas in tickets. Meet with
product managers to see if the product could be
improved. Consider setting up an About field (see <a class="xref" href="#topic_bnf_31q_k5b">What are the
most common ticket areas?</a>).</li>
<li class="li">Consider <a class="xref" href="https://support.zendesk.com/hc/en-us/articles/4408846795674" target="_blank">setting up a
knowledge base</a> to enable customers to serve
themselves. A great knowledge base means that many of
your customers will find the answer to their problem
without ever opening a ticket.</li>
</ul>
</td>
</tr>
<tr class="row">
<td class="entry nocellnorowborder" headers="topic_lz5_v1q_k5b__d52e219">Ticket volumes are consistently low.</td>
<td class="entry cell-norowborder" headers="topic_lz5_v1q_k5b__d52e222">
<ul class="ul" id="topic_lz5_v1q_k5b__ul_t12_qzp_k5b">
<li class="li">You might be able to reduce your number of agents.</li>
</ul>
</td>
</tr>
<tr class="row">
<td class="entry row-nocellborder" headers="topic_lz5_v1q_k5b__d52e219">Some agents have low solve rates.</td>
<td class="entry cellrowborder" headers="topic_lz5_v1q_k5b__d52e222">
<ul class="ul" id="topic_lz5_v1q_k5b__ul_u12_qzp_k5b">
<li class="li">Check which tickets the agent has been working on. They
could be particularly time-consuming problems.</li>
<li class="li">If an agent has a consistently low solve rate, they
might require more product training.</li>
</ul>
</td>
</tr>
</tbody>
</table>
</div>
</div>
</div>
</div>
<div aria-labelledby="ariaid-title7" class="topic nested1" id="topic_bnf_31q_k5b">
<h2 class="title topictitle2" id="ariaid-title7">What are the most common ticket areas?</h2>
<div class="body">
<p class="p">Feedback from customers can help you improve your products and your customers'
experiences. Take advantage of this feedback by categorizing your support requests
into product areas. Then, you can easily see which product areas generate the most
support issues.</p>
<p class="p">To categorize your support requests, <a class="xref" href="https://support.zendesk.com/hc/en-us/articles/4408883152794" target="_blank">add a custom field to your tickets and support request
form</a>. This field can contain as many values as you want, and you can call
the field whatever you want. In this example, the field is called Product and
contains three values.</p>
<p class="p"><img class="image img-screenshot" id="topic_bnf_31q_k5b__image_w12_qzp_k5b" src="https://zen-marketing-documentation.s3.amazonaws.com/docs/en/improving_support_1.png"></p>
<p class="p">To see how Zendesk categorizes tickets, see <a class="xref" href="https://support.zendesk.com/hc/en-us/articles/4409155792026" target="_blank">The 'About' Field</a>.</p>
</div>
<div aria-labelledby="ariaid-title8" class="topic nested2" id="topic_bw5_w1q_k5b">
<h3 class="title topictitle3" id="ariaid-title8">Viewing prebuilt reports (Lite and Professional)</h3>
<div class="body">
<p class="p">Explore doesn't include custom fields on prebuilt dashboards. However, you can
report on custom ticket fields by creating your own reports.</p>
</div>
</div>
<div aria-labelledby="ariaid-title9" class="topic nested2" id="topic_cw5_w1q_k5b">
<h3 class="title topictitle3" id="ariaid-title9">Creating your own reports (Professional)</h3>
<div class="body">
<p class="p">The <a class="xref" href="https://support.zendesk.com/hc/en-us/articles/4408827693594-Metrics-and-attributes-for-Zendesk-Support#topic_zlf_slp_4y" target="_blank">Tickets dataset</a> includes each of your
custom fields as an attribute. For more information, see <a class="xref" href="https://support.zendesk.com/hc/en-us/articles/4408824384538" target="_blank">Reporting with custom fields</a>.</p>
<p class="p"><strong class="ph b">To create a report showing areas with the most tickets</strong></p>
<ol class="ol" id="topic_cw5_w1q_k5b__ol_z12_qzp_k5b">
<li class="li">In Explore, <a class="xref" href="https://support.zendesk.com/hc/en-us/articles/4408821589530" target="_blank">create a new report</a> using the
<strong class="ph b">Support - Tickets</strong> dataset.</li>
<li class="li">In the <strong class="ph b">Metrics</strong> panel, select <strong class="ph b">Tickets</strong> &gt; <strong class="ph b">Tickets</strong>.</li>
<li class="li">In the <strong class="ph b">Rows</strong> panel, select <strong class="ph b">Ticket custom fields</strong> &gt;
<strong class="ph b"><em class="ph i">customfieldname</em></strong>.<p class="p"><strong class="ph b"><em class="ph i">customfieldname</em></strong> is
the name of the custom field you created to categorize your
tickets.</p>
</li>
</ol>
<p class="p">The following Explore recipes give you some great starting points for creating
your reports:</p>
<ul class="ul" id="topic_cw5_w1q_k5b__ul_ab2_qzp_k5b">
<li class="li"><a class="xref" href="https://support.zendesk.com/hc/en-us/articles/4660627546010" target="_blank">Reporting on custom ticket
fields</a></li>
<li class="li"><a class="xref" href="https://support.zendesk.com/hc/en-us/articles/4408846701082" target="_blank">Reporting on nested drop-down
fields</a></li>
</ul>
</div>
</div>
<div aria-labelledby="ariaid-title10" class="topic nested2" id="topic_dw5_w1q_k5b">
<h3 class="title topictitle3" id="ariaid-title10">What to look for</h3>
<div class="body">
<p class="p">As you look at your reports, focus on the following information:</p>
<ul class="ul" id="topic_dw5_w1q_k5b__ul_cb2_qzp_k5b">
<li class="li">The number of tickets in each area compared to the overall ticket
volume.</li>
<li class="li">The average time it takes to solve a ticket in each area.</li>
<li class="li">The average CSAT rating for tickets in each area.</li>
</ul>
</div>
</div>
<div aria-labelledby="ariaid-title11" class="topic nested2" id="topic_ew5_w1q_k5b">
<h3 class="title topictitle3" id="ariaid-title11">How to use the results</h3>
<div class="body">
<p class="p">The following table gives some examples of how the category can help improve your
customer support:</p>
<div class="tablenoborder">
<table border="1" cellpadding="4" cellspacing="0" class="table" frame="border" id="topic_ew5_w1q_k5b__topic_xcx_t2t_tjb__simpletable_ycx_t2t_tjb" rules="all" summary="">
<colgroup>
<col>
<col>
</colgroup>
<thead class="thead" style="text-align:left;">
<tr class="row">
<th class="entry nocellnorowborder" id="topic_ew5_w1q_k5b__d52e467">If you see this</th>
<th class="entry cell-norowborder" id="topic_ew5_w1q_k5b__d52e470">Do this</th>
</tr>
</thead>
<tbody class="tbody">
<tr class="row">
<td class="entry nocellnorowborder" headers="topic_ew5_w1q_k5b__d52e467">One category generates significantly more tickets than
others.</td>
<td class="entry cell-norowborder" headers="topic_ew5_w1q_k5b__d52e470">
<ul class="ul" id="topic_ew5_w1q_k5b__ul_eb2_qzp_k5b">
<li class="li">Work with product teams to identify whether the product
area could be improved.</li>
<li class="li">
<a class="xref" href="https://support.zendesk.com/hc/en-us/articles/4408846795674" target="_blank">Create a knowledge
base</a> with information to help customers use
that area of the product.</li>
</ul>
</td>
</tr>
<tr class="row">
<td class="entry row-nocellborder" headers="topic_ew5_w1q_k5b__d52e467">Many tickets are not assigned to a category.</td>
<td class="entry cellrowborder" headers="topic_ew5_w1q_k5b__d52e470">
<ul class="ul" id="topic_ew5_w1q_k5b__ul_fb2_qzp_k5b">
<li class="li">Train your agents to categorize tickets by selecting
from the list of predefined categories.</li>
<li class="li">Make the category field mandatory, meaning a category
must be chosen before you can proceed.</li>
<li class="li">
<a class="xref" href="https://support.zendesk.com/hc/en-us/articles/4408883152794#topic_ubz_ynk_xj" target="_blank">Add the field to your
support request form</a> so your customers can
choose the relevant category when they submit a support
request.</li>
</ul>
</td>
</tr>
</tbody>
</table>
</div>
</div>
</div>
</div>
<div aria-labelledby="ariaid-title12" class="topic nested1" id="topic_gvj_j1q_k5b">
<h2 class="title topictitle2" id="ariaid-title12">How much work do we have?</h2>
<div class="body">
<p class="p">Your ticket backlog provides a general pulse on the health of your support team.
Ticket backlog is defined as all tickets currently in a new, open, pending, or
on-hold state. In other words, it's your unsolved tickets that need work done on
them.</p>
<p class="p">This is an important metric to watch because it provides insight into your incoming
ticket volume and how well you keep up, given your resources.</p>
</div>
<div aria-labelledby="ariaid-title13" class="topic nested2" id="topic_swc_x1q_k5b">
<h3 class="title topictitle3" id="ariaid-title13">Viewing prebuilt reports (Lite and Professional)</h3>
<div class="body">
<p class="p">The <a class="xref" href="https://support.zendesk.com/hc/en-us/articles/4408835846810#topic_wyg_ybj_z3b" target="_blank">Backlog tab of the Zendesk Support
dashboard</a> includes prebuilt reports that measure your daily and
weekly ticket backlog.</p>
<p class="p"><img class="image img-screenshot" id="topic_swc_x1q_k5b__image_ib2_qzp_k5b" src="https://zen-marketing-documentation.s3.us-west-1.amazonaws.com/docs/en/explore_metrics_matter_ticket_backlog.png"></p>
</div>
</div>
<div aria-labelledby="ariaid-title14" class="topic nested2" id="topic_twc_x1q_k5b">
<h3 class="title topictitle3" id="ariaid-title14">Creating your own reports (Professional)</h3>
<div class="body">
<p class="p">The <a class="xref" href="https://support.zendesk.com/hc/en-us/articles/4408827693594-Metrics-and-attributes-for-Zendesk-Support#topic_dfb_ydg_ndb" target="_blank">Backlog history dataset</a> contains the
metrics and attributes you need to create your own reports about your ticket
backlog.</p>
<p class="p">The following Explore recipes give you some great starting points for creating
your reports:</p>
<ul class="ul" id="topic_twc_x1q_k5b__ul_kb2_qzp_k5b">
<li class="li"><a class="xref" href="https://support.zendesk.com/hc/en-us/articles/4408827158426" target="_blank">Backlog tickets by month</a></li>
<li class="li"><a class="xref" href="https://support.zendesk.com/hc/en-us/articles/4408833663514-Explore-Recipe-Top-problem-tickets-by-unsolved-incidents" target="_blank">Top problem tickets by unsolved
incidents</a></li>
</ul>
</div>
</div>
<div aria-labelledby="ariaid-title15" class="topic nested2" id="topic_uwc_x1q_k5b">
<h3 class="title topictitle3" id="ariaid-title15">What to look for</h3>
<div class="body">
<p class="p">As you look at your reports, focus on the following information:</p>
<div class="p">
<ul class="ul">
<li class="li">Ticket backlog volume cross-referenced with ticket age and first reply
time. A large backlog isn't necessarily a bad thing if your team is
capable of a high throughput.</li>
<li class="li">Ticket priority cross-referenced with ticket status. A large backlog may
or may not be bad, but one with many high-priority tickets probably
is.</li>
<li class="li">Historical backlog trends. For example, what are your busiest months?
Which of your agents are performing the best?</li>
<li class="li">Whether there are multiple support requests from the same customer, or
in the same categories.</li>
</ul>
</div>
<p class="p">Remember that speed is important, but not at the expense of quality. Sometimes,
support issues take longer to solve than the customer expects or longer than the
performance targets you’ve set for your team. However, the longer it takes to
solve a customer’s issue, the more likely customer satisfaction will suffer.</p>
</div>
</div>
<div aria-labelledby="ariaid-title16" class="topic nested2" id="topic_vwc_x1q_k5b">
<h3 class="title topictitle3" id="ariaid-title16">How to use the results</h3>
<div class="body">
<p class="p">The following table gives some examples of how examining your ticket backlog can
help improve your customer support:</p>
<div class="tablenoborder">
<table border="1" cellpadding="4" cellspacing="0" class="table" frame="border" id="topic_vwc_x1q_k5b__topic_obj_zft_tjb__simpletable_pbj_zft_tjb" rules="all" summary="">
<colgroup>
<col>
<col>
</colgroup>
<thead class="thead" style="text-align:left;">
<tr class="row">
<th class="entry nocellnorowborder" id="topic_vwc_x1q_k5b__d52e646">If you see this</th>
<th class="entry cell-norowborder" id="topic_vwc_x1q_k5b__d52e649">Do this</th>
</tr>
</thead>
<tbody class="tbody">
<tr class="row">
<td class="entry nocellnorowborder" headers="topic_vwc_x1q_k5b__d52e646">Your backlog is too big.</td>
<td class="entry cell-norowborder" headers="topic_vwc_x1q_k5b__d52e649">
<ul class="ul" id="topic_vwc_x1q_k5b__ul_nb2_qzp_k5b">
<li class="li">This means that customers are waiting longer for help.
Your team can help by keeping the customer informed
about the status and progress of their request.</li>
<li class="li">Are a lot of tickets in a pending state waiting for a
customer response? Consider creating an automation to
remind the customer of the pending status of their
issue. If they don’t respond after a set number of days,
you can automatically resolve the ticket to remove it
from the backlog. For an example, see <a class="xref" href="https://support.zendesk.com/hc/en-us/articles/4408832749210" target="_blank">Zendesk on Zendesk:
Bump Bump Solve</a>.</li>
<li class="li">A backlog consists of both unassigned tickets and
assigned tickets that have not yet been solved. The two
combined equals your total ticket backlog. Try to ensure
that tickets are assigned to someone as quickly as
possible.</li>
</ul>
</td>
</tr>
<tr class="row">
<td class="entry nocellnorowborder" headers="topic_vwc_x1q_k5b__d52e646">You have a lot of high-priority tickets in your
backlog.</td>
<td class="entry cell-norowborder" headers="topic_vwc_x1q_k5b__d52e649">
<ul class="ul" id="topic_vwc_x1q_k5b__ul_ob2_qzp_k5b">
<li class="li">Consider creating a trigger that escalates high-priority
tickets to make them visible more quickly. See <a class="xref" href="https://support.zendesk.com/hc/en-us/articles/4408886797466" target="_blank">Creating triggers for
automatic ticket updates and
notifications</a>.</li>
<li class="li">Triage incoming tickets from customers to ensure they've
set the priority field appropriately.</li>
<li class="li">Make sure your agents aren't setting the priority field
incorrectly. If so, they might need further training in
how to categorize requests.</li>
</ul>
</td>
</tr>
<tr class="row">
<td class="entry nocellnorowborder" headers="topic_vwc_x1q_k5b__d52e646">You see multiple support requests from the same customer in
the same category.</td>
<td class="entry cell-norowborder" headers="topic_vwc_x1q_k5b__d52e649">
<ul class="ul" id="topic_vwc_x1q_k5b__ul_pb2_qzp_k5b">
<li class="li">Engage directly with the customer to find out what's
wrong.</li>
</ul>
</td>
</tr>
<tr class="row">
<td class="entry row-nocellborder" headers="topic_vwc_x1q_k5b__d52e646">You get multiple support requests from different customers
for the same problem.</td>
<td class="entry cellrowborder" headers="topic_vwc_x1q_k5b__d52e649">
<ul class="ul" id="topic_vwc_x1q_k5b__ul_qb2_qzp_k5b">
<li class="li">Consider <a class="xref" href="https://support.zendesk.com/hc/en-us/articles/4408839258778" target="_blank">writing a knowledge
base article</a> about the problem.</li>
<li class="li">
<a class="xref" href="https://www.zendesk.com/blog/cultivate-community-customer-experience" target="_blank">Engage with the
community</a> in your knowledge base.</li>
<li class="li">Talk to your product development team. Could a product
redesign help to stop problems?</li>
</ul>
</td>
</tr>
</tbody>
</table>
</div>
</div>
</div>
</div>
<div aria-labelledby="ariaid-title17" class="topic nested1" id="topic_byc_k1q_k5b">
<h2 class="title topictitle2" id="ariaid-title17">How long do customers wait for a first reply?</h2>
<div class="body">
<p class="p">First reply time (FRT) is the amount of time from when a ticket is created to when an
agent makes the first reply to the customer. In other words, it measures how long it
takes a real human, not an automated reply, to contact the customer. First reply
time is a good indicator of the efficiency of your team and how well they hold up in
handling fluctuating incoming ticket volumes.</p>
<p class="p">Your performance target for this metric should align with your industry and customer
expectations for first reply times. For example, you might use:</p>
<ul class="ul" id="topic_byc_k1q_k5b__ul_i4h_zbq_k5b">
<li class="li">24 hours for support requests submitted using email and online forms</li>
<li class="li">60 minutes for requests submitted using social media</li>
</ul>
<p class="p">Of course, exceeding these expectations is even better from the customer’s
perspective.</p>
</div>
<div aria-labelledby="ariaid-title18" class="topic nested2" id="topic_i2g_x1q_k5b">
<h3 class="title topictitle3" id="ariaid-title18">Viewing prebuilt reports (Lite and Professional)</h3>
<div class="body">
<div class="section" id="topic_i2g_x1q_k5b__section_tb2_qzp_k5b">
<p class="p">The <a class="xref" href="https://support.zendesk.com/hc/en-us/articles/4408835846810#topic_zd3_ybj_z3b" target="_blank">Efficiency tab of the Zendesk Support
dashboard</a> includes prebuilt reports that measure your first reply
time.</p>
<p class="p"><img class="image img-screenshot" id="topic_i2g_x1q_k5b__image_ub2_qzp_k5b" src="https://zen-marketing-documentation.s3.amazonaws.com/docs/en/explore_metrics_matter_ticket_backlog.png"></p>
</div>
</div>
</div>
<div aria-labelledby="ariaid-title19" class="topic nested2" id="topic_j2g_x1q_k5b">
<h3 class="title topictitle3" id="ariaid-title19">Creating your own reports (Professional)</h3>
<div class="body">
<p class="p">The <a class="xref" href="https://support.zendesk.com/hc/en-us/articles/4408827693594-Metrics-and-attributes-for-Zendesk-Support#topic_zlf_slp_4y" target="_blank">Tickets dataset</a> contains the metrics
and attributes you need to create your own reports about first reply time and
efficiency.</p>
<p class="p">The following Explore recipes give you some great starting points for creating
your reports:</p>
<ul class="ul" id="topic_j2g_x1q_k5b__ul_wb2_qzp_k5b">
<li class="li"><a class="xref" href="https://support.zendesk.com/hc/en-us/articles/4408820652058" target="_blank">Reporting on first reply time</a></li>
<li class="li"><a class="xref" href="https://support.zendesk.com/hc/en-us/articles/4408823587738-Explore-recipe-First-reply-time-heatmap" target="_blank">First reply time heatmap</a></li>
<li class="li"><a class="xref" href="https://support.zendesk.com/hc/en-us/articles/4408819310746" target="_blank">Displaying tickets with a higher than
average first reply time</a></li>
<li class="li"><a class="xref" href="https://support.zendesk.com/hc/en-us/articles/4408846756506" target="_blank">Creating a ticket first reply date
attribute</a></li>
<li class="li"><a class="xref" href="https://support.zendesk.com/hc/en-us/articles/4408827196954" target="_blank">Getting resolution times (first reply,
first resolution, and full resolution) based on tags</a></li>
</ul>
</div>
</div>
<div aria-labelledby="ariaid-title20" class="topic nested2" id="topic_k2g_x1q_k5b">
<h3 class="title topictitle3" id="ariaid-title20">What to look for</h3>
<div class="body">
<p class="p">As you look at your reports, focus on the following information:</p>
<ul class="ul" id="topic_k2g_x1q_k5b__ul_yb2_qzp_k5b">
<li class="li">Look at your ticket volume whenever your first reply time changes. A change
might correspond with a temporary change in ticket volume. Start by looking
at the <a class="xref" href="https://support.zendesk.com/hc/en-us/articles/4408835846810#topic_hlj_xbj_z3b" target="_blank">Tickets</a> and <a class="xref" href="https://support.zendesk.com/hc/en-us/articles/4408835846810#topic_zd3_ybj_z3b" target="_blank">Efficiency</a> tabs in the Zendesk
Support dashboard. If you had a temporary surge from a new product launch or
a major service incident, then this might not be a worrying trend. If you
can predict these surges, that's a great time to bring a bit of extra help
onboard.</li>
<li class="li">If your first reply time is 24 hours on email-submitted requests and your
median number of agent interactions is eight per ticket, then your average
reply time median should be 4 hours or less. Looking at tickets with an
average reply time greater than 4 hours should highlight opportunities for
improving agent performance (such as training or adding self-service
documentation to your knowledge base).</li>
<li class="li">What are your customers telling you about your reply time? Look at your CSAT
ratings and comments.</li>
<li class="li">Monitor first reply time for each of your support channels to ensure that
expectations are being met.</li>
<li class="li">Monitor first reply time by product area if you're using a custom field as
described earlier in this article (see <a class="xref" href="#topic_bnf_31q_k5b">What are the most common ticket areas?</a>).</li>
<li class="li">Monitor average reply time. This is the average amount of time for all
replies to the customer when solving a support request.</li>
</ul>
</div>
</div>
<div aria-labelledby="ariaid-title21" class="topic nested2" id="topic_l2g_x1q_k5b">
<h3 class="title topictitle3" id="ariaid-title21">How to use the results</h3>
<div class="body">
<p class="p">The following table gives some examples of how examining your first response
times can help improve your customer support:</p>
<div class="tablenoborder">
<table border="1" cellpadding="4" cellspacing="0" class="table" frame="border" id="topic_l2g_x1q_k5b__topic_qxc_pgt_tjb__simpletable_rxc_pgt_tjb" rules="all" summary="">
<colgroup>
<col>
<col>
</colgroup>
<thead class="thead" style="text-align:left;">
<tr class="row">
<th class="entry nocellnorowborder" id="topic_l2g_x1q_k5b__d52e899">If you see this</th>
<th class="entry cell-norowborder" id="topic_l2g_x1q_k5b__d52e902">Do this</th>
</tr>
</thead>
<tbody class="tbody">
<tr class="row">
<td class="entry row-nocellborder" headers="topic_l2g_x1q_k5b__d52e899">First reply times are high.</td>
<td class="entry cellrowborder" headers="topic_l2g_x1q_k5b__d52e902">
<ul class="ul" id="topic_l2g_x1q_k5b__ul_ac2_qzp_k5b">
<li class="li">Look at when you get most of your tickets. An Explore
report using the <strong class="ph b">Tickets</strong> metric and the <strong class="ph b">Ticket
created - Hour</strong> attribute is a quick way to help
make sure you have support online when your customers
are.</li>
<li class="li">However quickly your team solves emailed tickets,
sometimes live channels can be a faster way for
customers to get help and for you to solve tickets.</li>
<li class="li">When something goes wrong, it's critical to find and
address the issue as quickly as possible. Letting
customers know you're aware and working on a problem is
key to turning a bad situation into a good interaction
with your company.</li>
<li class="li">If your customers serve themselves, then you don't need
to worry about first reply times! <a class="xref" href="https://support.zendesk.com/hc/en-us/articles/4408846795674" target="_blank">Set up a knowledge
base</a> and write articles that address your top
customer pain points. Stay present in your knowledge
base and always answer questions from customers.</li>
</ul>
</td>
</tr>
</tbody>
</table>
</div>
</div>
</div>
</div>
<div aria-labelledby="ariaid-title22" class="topic nested1" id="topic_a11_l1q_k5b">
<h2 class="title topictitle2" id="ariaid-title22">How long do tickets take to resolve?</h2>
<div class="body">
<p class="p">Resolution time is important not just to you and your team. Customers also want their
problems solved quickly. There are several key metrics that indicate how long it
takes for agents to resolve issues:</p>
<ul class="ul" id="topic_a11_l1q_k5b__ul_cc2_qzp_k5b">
<li class="li">
<strong class="ph b">Resolution time:</strong> The time it takes for a support issue to be solved. A
ticket might get solved more than once because it can be reopened before it’s
closed. The time it took to solve the issue the first time is called first
resolution time.</li>
<li class="li">
<strong class="ph b">Full resolution time:</strong> The time it took to finally solve the ticket.</li>
<li class="li">
<strong class="ph b">Agent replies:</strong> The number of replies it takes for your agents to solve
the ticket. The faster you can solve a ticket, the happier the customer will
be.</li>
<li class="li">
<strong class="ph b">One-touch resolution:</strong> Support issues that were resolved in a single
interaction such as a call, ticket reply, or live chat. This has a positive
impact on customer satisfaction and helps reduce support costs.</li>
</ul>
</div>
<div aria-labelledby="ariaid-title23" class="topic nested2" id="topic_ey3_x1q_k5b">
<h3 class="title topictitle3" id="ariaid-title23">Viewing prebuilt reports (Lite and Professional)</h3>
<div class="body">
<p class="p">The <a class="xref" href="https://support.zendesk.com/hc/en-us/articles/4408835846810#topic_zd3_ybj_z3b" target="_blank">Efficiency tab of the Zendesk Support
dashboard</a> includes prebuilt reports that measure how long your
tickets take to solve.</p>
<p class="p"><img class="image img-screenshot" id="topic_ey3_x1q_k5b__image_ec2_qzp_k5b" src="https://zen-marketing-documentation.s3.amazonaws.com/docs/en/Explore_improve_metrics_4.png"></p>
</div>
</div>
<div aria-labelledby="ariaid-title24" class="topic nested2" id="topic_fy3_x1q_k5b">
<h3 class="title topictitle3" id="ariaid-title24">Creating your own reports (Professional)</h3>
<div class="body">
<p class="p">The <a class="xref" href="https://support.zendesk.com/hc/en-us/articles/4408827693594-Metrics-and-attributes-for-Zendesk-Support#topic_zlf_slp_4y" target="_blank">Tickets dataset</a> contains the metrics
and attributes you need to create your own reports about first reply time and
efficiency.</p>
<p class="p">The following Explore recipes give you some great starting points for creating
your reports:</p>
<ul class="ul" id="topic_fy3_x1q_k5b__ul_gc2_qzp_k5b">
<li class="li"><a class="xref" href="https://support.zendesk.com/hc/en-us/articles/4408845671706" target="_blank">First assignment to first resolution
time</a></li>
<li class="li"><a class="xref" href="https://support.zendesk.com/hc/en-us/articles/4408846254234" target="_blank">Reporting on full resolution
time</a></li>
<li class="li"><a class="xref" href="https://support.zendesk.com/hc/en-us/articles/4408830883610" target="_blank">Average ticket resolution time without
pending or on-hold time</a></li>
<li class="li"><a class="xref" href="https://support.zendesk.com/hc/en-us/articles/4408827196954-Explore-recipe-Getting-resolution-times-first-reply-first-resolution-and-full-resolution-based-on-tags" target="_blank">Getting resolution times (first reply,
first resolution, and full resolution) based on tags</a></li>
<li class="li"><a class="xref" href="https://support.zendesk.com/hc/en-us/articles/4408825230490" target="_blank">Time Tracking app: metrics you need to be
measuring</a></li>
</ul>
</div>
</div>
<div aria-labelledby="ariaid-title25" class="topic nested2" id="topic_gy3_x1q_k5b">
<h3 class="title topictitle3" id="ariaid-title25">What to look for</h3>
<div class="body">
<p class="p">Metrics that can help you understand the time and effort that went into solving a
ticket include:</p>
<ul class="ul" id="topic_gy3_x1q_k5b__ul_ic2_qzp_k5b">
<li class="li">
<strong class="ph b">Handle time:</strong> The time that an agent spends working on a single
support interaction. In Support, handle time is captured using the <a class="xref" href="https://support.zendesk.com/hc/en-us/articles/4408828227098" target="_blank">Time Tracking app</a>. Explore can
report on this data using the custom fields Total time spent, Avg time spent
per ticket, and Avg time spent per update. For details, see <a class="xref" href="https://support.zendesk.com/hc/en-us/articles/4408825230490" target="_blank">Time Tracking app: metrics you need to be
measuring</a>.</li>
<li class="li">
<strong class="ph b">Agent touches:</strong> An update that an agent makes to a ticket. This
includes changes of ticket status, adding comments, and others. With
Explore, you can report on agent touches using the <strong class="ph b">Agent replies</strong>
metric and <strong class="ph b">Agent replies brackets</strong> attribute.</li>
<li class="li">
<strong class="ph b">Requester wait time:</strong> The time a customer waits for their issue to be
resolved. This is the time that a ticket spends in the New, Open, and
On-hold statuses. During these periods, it’s the support team’s
responsibility to resolve the issue. It's a good indicator of the customer’s
experience of the support interaction.</li>
</ul>
</div>
</div>
<div aria-labelledby="ariaid-title26" class="topic nested2" id="topic_hy3_x1q_k5b">
<h3 class="title topictitle3" id="ariaid-title26">How to use the results</h3>
<div class="body">
<p class="p">The following table gives some examples of how examining your full resolution
times can help improve your customer support:</p>
<div class="tablenoborder">
<table border="1" cellpadding="4" cellspacing="0" class="table" frame="border" id="topic_hy3_x1q_k5b__topic_u3f_qgt_tjb__simpletable_v3f_qgt_tjb" rules="all" summary="">
<colgroup>
<col>
<col>
</colgroup>
<thead class="thead" style="text-align:left;">
<tr class="row">
<th class="entry nocellnorowborder" id="topic_hy3_x1q_k5b__d52e1105">If you see this</th>
<th class="entry cell-norowborder" id="topic_hy3_x1q_k5b__d52e1108">Do this</th>
</tr>
</thead>
<tbody class="tbody">
<tr class="row">
<td class="entry nocellnorowborder" headers="topic_hy3_x1q_k5b__d52e1105">Tickets are taking too long to resolve.</td>
<td class="entry cell-norowborder" headers="topic_hy3_x1q_k5b__d52e1108">
<ul class="ul" id="topic_hy3_x1q_k5b__ul_kc2_qzp_k5b">
<li class="li">This has a direct effect on customer satisfaction:
People don’t want to wait a long time to have their
problems resolved. However, focusing solely on
resolution time isn’t necessarily a good idea. Speed
doesn’t always equal quality. (For more, see <a class="xref" href="#topic_fqt_l1q_k5b">How often
are solved tickets reopened?</a>)</li>
<li class="li">In addition to resolution time, finding the actual time
that the agent spent resolving the issue is important.
Total resolution time doesn’t do that because it
includes stages in the ticket lifecycle when the agent
isn’t working on it. For example, when it’s sent back to
the customer for information and put in a Pending
status.</li>
</ul>
</td>
</tr>
<tr class="row">
<td class="entry nocellnorowborder" headers="topic_hy3_x1q_k5b__d52e1105">You have a high proportion of one-touch resolution
tickets.</td>
<td class="entry cell-norowborder" headers="topic_hy3_x1q_k5b__d52e1108">
<ul class="ul" id="topic_hy3_x1q_k5b__ul_lc2_qzp_k5b">
<li class="li">This might indicate that you have lots of low-complexity
support issues that could be better handled with
self-service. Agents should work on more complex issues,
not those that a customer can easily solve on their own
by reading FAQs.</li>
</ul>
</td>
</tr>
<tr class="row">
<td class="entry row-nocellborder" headers="topic_hy3_x1q_k5b__d52e1105">Tickets have a high proportion of agent touches.</td>
<td class="entry cellrowborder" headers="topic_hy3_x1q_k5b__d52e1108">
<ul class="ul" id="topic_hy3_x1q_k5b__ul_mc2_qzp_k5b">
<li class="li">This might indicate that the agent needs more training
because it takes them more touches than the team average
to solve tickets.</li>
</ul>
</td>
</tr>
</tbody>
</table>
</div>
</div>
</div>
</div>
<div aria-labelledby="ariaid-title27" class="topic nested1" id="topic_fqt_l1q_k5b">
<h2 class="title topictitle2" id="ariaid-title27">How often are solved tickets reopened?</h2>
<div class="body">
<p class="p">A reopen occurs when a ticket's status is changed from Solved back to Open.</p>
<p class="p">When tickets are reopened, this might indicate that agents aren’t fully solving the
customer’s support issues. This might be because agents are concentrating on
first-touch resolutions and speed over quality. It’s good practice to routinely
monitor your team’s ticket reopens.</p>
</div>
<div aria-labelledby="ariaid-title28" class="topic nested2" id="topic_ygn_x1q_k5b">
<h3 class="title topictitle3" id="ariaid-title28">Viewing prebuilt reports (Lite and Professional)</h3>
<div class="body">
<p class="p">The <a class="xref" href="https://support.zendesk.com/hc/en-us/articles/4408835846810#topic_hlj_xbj_z3b" target="_blank">Tickets tab of the Zendesk Support
dashboard</a> contains information about reopened tickets.</p>
<p class="p"><img class="image img-screenshot" id="topic_ygn_x1q_k5b__image_pc2_qzp_k5b" src="https://zen-marketing-documentation.s3.amazonaws.com/docs/en/Explore_improve_metrics_5.png"></p>
</div>
</div>
<div aria-labelledby="ariaid-title29" class="topic nested2" id="topic_zgn_x1q_k5b">
<h3 class="title topictitle3" id="ariaid-title29">Creating your own reports (Professional)</h3>
<div class="body">
<p class="p">The <a class="xref" href="https://support.zendesk.com/hc/en-us/articles/4408827693594-Metrics-and-attributes-for-Zendesk-Support#topic_zlf_slp_4y" target="_blank">Tickets dataset</a> contains the metrics
and attributes you need to create your own reports about reopened tickets.</p>
</div>
</div>
<div aria-labelledby="ariaid-title30" class="topic nested2" id="topic_ahn_x1q_k5b">
<h3 class="title topictitle3" id="ariaid-title30">What to look for</h3>
<div class="body">
<div class="p">
<ul class="ul">
<li class="li">The total number of reopens</li>
<li class="li">The percentage of tickets with reopens</li>
</ul>
</div>
</div>
</div>
<div aria-labelledby="ariaid-title31" class="topic nested2" id="topic_bhn_x1q_k5b">
<h3 class="title topictitle3" id="ariaid-title31">How to use the results</h3>
<div class="body">
<p class="p">The following table gives some examples of how examining your ticket reopens can
help improve your customer support:</p>
<div class="tablenoborder">
<table border="1" cellpadding="4" cellspacing="0" class="table" frame="border" id="topic_bhn_x1q_k5b__table_y1l_jcq_k5b" rules="all" summary="">
<colgroup>
<col>
<col>
</colgroup>
<thead class="thead" style="text-align:left;">
<tr class="row">
<th class="entry nocellnorowborder" id="d48e1309">If you see this</th>
<th class="entry cell-norowborder" id="d48e1312">Do this</th>
</tr>
</thead>
<tbody class="tbody">
<tr class="row">
<td class="entry row-nocellborder" headers="d48e1309">The percentage of tickets being reopened is high.</td>
<td class="entry cellrowborder" headers="d48e1312">
<ul class="ul" id="topic_bhn_x1q_k5b__ul_z1l_jcq_k5b">
<li class="li">Is this an escalated issue? Ticket reopens are more
likely when agents deal with more complex support
issues, so reopens might be higher for escalated
tickets.</li>
<li class="li">Are your agents sufficiently trained? They might not
have sufficient knowledge to solve more complex
problems.</li>
<li class="li">Was there missing information in the ticket that caused
the agent to misdiagnose the issue? Consider collecting
more information in the customer ticket form if this is
the case.</li>
</ul>
</td>
</tr>
</tbody>
</table>
</div>
</div>
</div>
</div>
<div aria-labelledby="ariaid-title32" class="topic nested1" id="topic_mzr_m1q_k5b">
<h2 class="title topictitle2" id="ariaid-title32">How satisfied are customers?</h2>
<div class="body">
<p class="p">Every time you interact with a customer, consider <a class="xref" href="https://support.zendesk.com/hc/en-us/articles/4408822875034" target="_blank">measuring their satisfaction with a Customer Satisfaction
Survey (CSAT)</a>, a short survey sent to the customer after their problem is
solved.</p>
<p class="p">Tracking CSAT helps you spot trends that might be affecting customer satisfaction.
Satisfaction ratings are also key performance indicators for your agents because
each rating received is associated with the agent who solved the customer’s problem.
These can be averaged to give each agent an overall CSAT score.</p>
<p class="p">At Zendesk, we simply ask if the interaction was good or bad. If customers want to
give more feedback, they can add a comment.</p>
<p class="p">Examples of metrics you can track include:</p>
<ul class="ul" id="topic_mzr_m1q_k5b__ul_vc2_qzp_k5b">
<li class="li">A customer’s CSAT rating over time</li>
<li class="li">CSAT ratings by channel, product, or service</li>
<li class="li">Average CSAT ratings for agents and teams</li>
</ul>
</div>
<div aria-labelledby="ariaid-title33" class="topic nested2" id="topic_gmr_x1q_k5b">
<h3 class="title topictitle3" id="ariaid-title33">Viewing prebuilt reports (Lite and Professional)</h3>
<div class="body">
<p class="p">The <a class="xref" href="https://support.zendesk.com/hc/en-us/articles/4408835846810#topic_ijh_ybj_z3b" target="_blank">Satisfaction tab of the Zendesk Support
dashboard</a> includes reports that help you analyze your customer
satisfaction scores.</p>
<p class="p"><img class="image img-screenshot" id="topic_gmr_x1q_k5b__image_xc2_qzp_k5b" src="https://zen-marketing-documentation.s3.amazonaws.com/docs/en/Explore_improve_metrics_6.png"></p>
</div>
</div>
<div aria-labelledby="ariaid-title34" class="topic nested2" id="topic_hmr_x1q_k5b">
<h3 class="title topictitle3" id="ariaid-title34">Creating your own reports (Professional)</h3>
<div class="body">
<p class="p">The <a class="xref" href="https://support.zendesk.com/hc/en-us/articles/4408827693594-Metrics-and-attributes-for-Zendesk-Support#topic_zlf_slp_4y" target="_blank">Tickets dataset</a> contains the metrics
and attributes you need to create your own reports about customer
satisfaction.</p>
<p class="p">The following Explore recipes give you some great starting points for creating
your reports:</p>
<ul class="ul" id="topic_hmr_x1q_k5b__ul_zc2_qzp_k5b">
<li class="li"><a class="xref" href="https://support.zendesk.com/hc/en-us/articles/4408845694234" target="_blank">Reporting on customer satisfaction by
agent</a></li>
<li class="li"><a class="xref" href="https://support.zendesk.com/hc/en-us/articles/4408822875930" target="_blank">Determining satsifaction scores for your
agents</a></li>
<li class="li"><a class="xref" href="https://support.zendesk.com/hc/en-us/articles/4408843401370" target="_blank">Determine ticket assignee when
satisfaction rating is given</a></li>
<li class="li"><a class="xref" href="https://support.zendesk.com/hc/en-us/articles/4408825376282" target="_blank">Display all customer satisfaction
comments</a></li>
<li class="li"><a class="xref" href="https://support.zendesk.com/hc/en-us/articles/4408838658074-Explore-Recipe-Bad-ratings-with-comments" target="_blank">Bad ratings with comments</a></li>
<li class="li"><a class="xref" href="https://support.zendesk.com/hc/en-us/articles/4408845685146" target="_blank">Reporting on CSAT and one-touch
tickets</a></li>
<li class="li"><a class="xref" href="https://support.zendesk.com/hc/en-us/articles/4408820380314-Explore-Recipe-Percentage-satisfaction-score-based-on-agent-replies" target="_blank">Percentage satisfaction score based on
agent replies</a></li>
<li class="li"><a class="xref" href="https://support.zendesk.com/hc/en-us/articles/4408837820442-Explore-recipe-Satisfaction-trending-year-over-year" target="_blank">Satisfaction trending
year-over-year</a></li>
</ul>
</div>
</div>
<div aria-labelledby="ariaid-title35" class="topic nested2" id="topic_imr_x1q_k5b">
<h3 class="title topictitle3" id="ariaid-title35">What to look for</h3>
<div class="body">
<div class="p">
<ul class="ul">
<li class="li">Compare ticket stats on tickets rated bad to those rated good.</li>
<li class="li">Look for satisfaction ratings with comments.</li>
</ul>
</div>
</div>
</div>
<div aria-labelledby="ariaid-title36" class="topic nested2" id="topic_jmr_x1q_k5b">
<h3 class="title topictitle3" id="ariaid-title36">How to use the results</h3>
<div class="body">
<p class="p">The following table gives some examples of how examining your customer
satisfaction can help improve your customer support:</p>
<div class="tablenoborder">
<table border="1" cellpadding="4" cellspacing="0" class="table" frame="border" id="topic_jmr_x1q_k5b__topic_zx2_ygt_tjb__simpletable_ay2_ygt_tjb" rules="all" summary="">
<colgroup>
<col>
<col>
</colgroup>
<thead class="thead" style="text-align:left;">
<tr class="row">
<th class="entry nocellnorowborder" id="topic_jmr_x1q_k5b__d52e1441">If you see this</th>
<th class="entry cell-norowborder" id="topic_jmr_x1q_k5b__d52e1444">Do this</th>
</tr>
</thead>
<tbody class="tbody">
<tr class="row">
<td class="entry row-nocellborder" headers="topic_jmr_x1q_k5b__d52e1441">You get one or more bad ratings.</td>
<td class="entry cellrowborder" headers="topic_jmr_x1q_k5b__d52e1444">
<ul class="ul" id="topic_jmr_x1q_k5b__ul_cd2_qzp_k5b">
<li class="li">Notify managers when you get feedback. You can automate
this using a trigger to notify a manager or group of
managers when a ticket receives a bad rating. Use the
following two <a class="xref" href="https://support.zendesk.com/hc/en-us/articles/4408886797466" target="_blank">trigger
conditions</a>:<ul class="ul" id="topic_jmr_x1q_k5b__ul_dd2_qzp_k5b">
<li class="li">
<strong class="ph b">Ticket: Satisfaction</strong> &gt; <strong class="ph b">Changed to</strong>
&gt; <strong class="ph b">Bad</strong>
</li>
<li class="li">
<strong class="ph b">Ticket: Satisfaction</strong> &gt; <strong class="ph b">Changed to</strong>
&gt; <strong class="ph b">Bad with comment</strong>
</li>
</ul>
</li>
<li class="li">Give your agents more information about your customers.
Tickets with more touches often have a lower CSAT
rating. Making more customer information available to
your support teams with CRM integrations or custom user
and organization fields can help your team know more
about customers up front. If you can eliminate initial
questions on tickets, that leads to faster resolution
times and more one-touch ticket solves.</li>
<li class="li">Did your agent provide inaccurate information? Was there
an issue with resolution time? Consider categorizing
badly rated tickets based on the reasons why the ticket
was rated the way it was. If it's purely about ticket
handling, resolution time, or workflow issues, then
those are some great projects to work on going
forward.</li>
</ul>
</td>
</tr>
</tbody>
</table>
</div>
</div>
</div>
</div>
<div aria-labelledby="ariaid-title37" class="topic nested1" id="topic_kdx_n1q_k5b">
<h2 class="title topictitle2" id="ariaid-title37">More resources</h2>
<div class="body">
<p class="p">By focusing on the metrics that matter, both your organization and your customers
will benefit. All of the reports you've learned about in this article can be used to
help you avoid ongoing issues.</p>
<p class="p">If you're new to Explore and want to learn the basics, read <a class="xref" href="https://support.zendesk.com/hc/en-us/articles/4408831710618" target="_blank">Getting started with Zendesk Explore</a>.</p>
<p class="p">For some great ideas to help you get started with reporting, check out <a class="xref" href="https://support.zendesk.com/hc/en-us/articles/4409149172890" target="_blank">Explore recipes reference</a>.</p>
<p class="p">Finally, to see all of the Explore documentation, start with <a class="xref" href="https://support.zendesk.com/hc/en-us/articles/4408846357018" target="_blank">Zendesk Explore resources</a>.</p>
</div>
</div>
<div aria-labelledby="ariaid-title38" class="topic nested1" id="topic_c5m_41q_k5b">
<h2 class="title topictitle2" id="ariaid-title38">Join the conversation!</h2>
<div class="body">
<p class="p">What tools do you use to help measure the success of your support organization? How
have you managed to improve these metrics? Let us know in the comments below.</p>
</div>
</div>
<script id="docs-schema-markup" type="application/ld+json">{
"@context": "https://schema.org",
"@type": "TechArticle",
"@id": "https://support.zendesk.com/hc/en-us/articles/4408832234394",
"url": "https://support.zendesk.com/hc/en-us/articles/4408832234394-Analyzing-the-metrics-that-matter-to-improve-customer-support",
"headline": "Analyzing the metrics that matter to improve customer support",
"description": "You can analyze key customer support metrics to identify performance trends and areas for improvement, then use this data to enhance your team's effectiveness and customer satisfaction.",
"articleSection": "Measuring success",
"datePublished": "2021-10-16T03:46:34+00:00",
"dateModified": "2025-09-05T23:49:49+00:00",
"inLanguage": "en-US",
"mainEntityOfPage": {
"@type": "WebPage",
"@id": "https://support.zendesk.com/hc/en-us/articles/4408832234394"
},
"author": {
"@type": "Organization",
"name": "Zendesk",
"@id": "https://www.zendesk.com"
},
"publisher": {
"@type": "Organization",
"name": "Zendesk",
"@id": "https://www.zendesk.com"
},
"isPartOf": {
"@type": "WebSite",
"name": "Zendesk Help",
"@id": "https://support.zendesk.com/hc/"
},
"about": {
"@type": "SoftwareApplication",
"name": "Zendesk",
"@id": "https://www.zendesk.com",
"softwareAddOn": {
"@type": "SoftwareApplication",
"name": "Copilot",
"@id": "https://support.zendesk.com/hc/en-us/sections/4405303717658"
}
}
}</script>