The Solved Tickets metric tracks tickets which are solved in Zendesk Support by agents.
An agent will receive a solved point if they are the first to solve a ticket. By default, a ticket may be counted as Solved only once in the life the ticket. The solved point credit is attributed to the agent whom is the first one to solve a ticket.
Why does Tymeshift use this calculation method by default?
The advantage of this calculation method is that it allows you to accurately measure the total number of tickets be solved. Alternate calculation methods can mean that you may actually wind up with a higher a higher number of total solved tickets then tickets created since it's possible to receive credit for solving a single ticket more than one time.
Changing the calculation method:
As noted above, by default, only one agent may receive credit for a solved ticket, and only the first time they solve it. However, you may change the calculation method to allow one solved point per ticket, per agent. This can be changed via Admin > Metric Settings.
Note: if a ticket is solved by automation or trigger, no one will receive a solved point. If the ticket is merged to another case, no solved point will be attributed.
How does Tymeshift calculate solved tickets differently than GoodData?
Tymeshift counts Solved Tickets a bit differently than Zendesk’s GoodData does. Let’s review an example to understand how they are different.
Here’s how Tymeshift handles solved tickets:
- Agent A solves a ticket 5 times
- Tymeshift gives Agent A credit for 1 solved ticket.
- Tymeshift gives Agent A credit for 4 Attended Points.
- Agent B solves the same ticket 5 times
- Tymeshift gives Agent B credit for 1 solved ticket.
- Tymeshift gives Agent B credit for 4 Attended Points.
Tymeshift tracked this ticket as solved only a single time for each agent, however, GoodData counts this as 5 solved tickets for both Agent A and Agent B. It also tracks the 4 times each agent re-opens the ticket.
Common uses of Solved Tickets
Solved Tickets is a great metric to use to get an understanding of the total volume of tickets being solved in your support organization. Depending on your organization's goals, it can also be a great metric to add to your agent's scorecard.
Downfalls of Solved Tickets
Although Solved Tickets is great for getting a handle on how many tickets are being solved within your organization it doesn't account for the number of interactions occurring on tickets. If your organization is highly interaction/conversation drive (lots of back and forth between support + the customer) then using a metric like Public Comments or Public Comments Per Hour could be a better fit. Generally speaking, combing Solved Tickets with another metric will typically give you the best of both worlds.