klipfolio image

1176

arrow-right icon

40.62

vs previous period

Tickets

Date created: Jan 15, 2019  •   Last updated: Mar 14, 2022

What is Tickets?

Customer Issues, tickets, or incidents, refers to the capture of user or system initiated requests. These might include help requests, bug or error reports, events or alarms, feature requests, complaints or any type of other feedback. Generally we think of user generated issues first, but increasingly with the use of software and connected devices, these incident reports are being generated automatically.

Alternate names: Customer Issues, Incidents

Tickets Formula

ƒ Count(Open Issues) + Count(Closed Issues)

Start tracking your Tickets data

Use Klipfolio PowerMetrics, our free analytics tool, to monitor your data. Choose one of the following available services to start tracking your Tickets instantly.

Klipfolio dashboard image

How to visualize Tickets?

Use a summary chart to visualize your Tickets data and compare it to a previous time period.

Tickets visualization example

klipfolio image

Tickets

1176

arrow-right icon

40.62

vs previous period

Summary Chart

Here's an example of how to visualize your current Tickets data in comparison to a previous time period or date range.
arrow-right icon
arrow-right icon

Tickets

1175.83

arrow-right icon

40.61

vs previous period

Summary Chart

Here's an example of how to visualize your current Tickets data in comparison to a previous time period or date range.

More about Tickets

A Customer Issue, in addition to documenting the request, will generally capture a lot of additional detail, such as steps to reproduce, system or device information, urgency, customer type, location etc...

As Customer Issues come in, they are in an open state, and depending on the organization, they flow through a number of state changes, such as active, pending, and stale, before they are finally closed.

Issue Tracking Systems (ITS) are most commonly used in a support, help desk, or customer success function, but are also used extensively with software development and manufacturing organizations. An ITS can help automate much of the documentation and status history.

Having an idea of how many tickets are in your support queue, new ones being opened, and existing ones closed, can help you determine reasons for a high and low volume. If you have a low number of open tickets, this could indicate your support team has very efficient response times or that you don't have many issues/inquiries at that moment.

A high number of open incidents could indicate your team is struggling to keep up with the volume of inquiries. This could be a lack of efficiency or perhaps necessitate hiring more support staff to keep up.

Using this metric, especially with ratios such as Tickets Per Agent, or Tickets Per Customer will help assess the health of your team.