Suite | Professional, Enterprise, or Enterprise Plus |
Support with | Explore Professional or Enterprise |
The Zendesk Time Tracking app helps support managers gain visibility into the actual time spent across all your customer service interactions within a ticket. The app tracks the time spent on each ticket update and stores this with the ticket.
This time spent can be measured per ticket or per update. Time spent per ticket is called ticket handling time. Time spent per update is called update handling time. With Explore, you can create calculated metrics for these different handling times and create time tracking reports in Explore.
This article describes the difference between ticket handling time and update handling time. It also links to Explore recipes that show you how to create custom time tracking metrics and reports.
Ticket handling time vs. Update handling time
As with any other Support ticket data, there are two approaches for analyzing time tracking app data:
- Ticket handling time
- Update handling time
Ticket handling time
The first approach is to look at the handling time per ticket. You can use this information to report on individual agent performance, or to report on complex workflows where the same ticket is handled by multiple agents.
If you choose to go with this approach, the best place to create your reports is the Support: Tickets dataset. To do so, you can create a standard calculated metric based on the Total time spent (sec) metric (which is available in Explore only after you install the Time Tracking app) and use it to report on the handling time per ticket.
To learn how to create a custom Ticket handling time metric and use it to produce two example time tracking reports, see Explore recipe: Time Tracking app - Measuring ticket handling time.
Update handling time
The second approach is to look at the handling time per update. You can use this information to report on individual agent performance, or to report on complex workflows where the same ticket is handled by multiple agents.
For this approach, the calculated metric and reports should be created in the Support: Updates history dataset based on the data stored in the Changes - Previous value and Changes - New value attributes.
To learn how to create a custom Update handling time metric and use it to produce an example time tracking report, see Explore recipe: Time Tracking app - Measuring update handling time.
123 comments
Alex Zheng
I will open up a ticket with you to investigate further.
Best regards,
1
Elena
It doesn't work in either Support: Updates or Support: Tickets
In tickets you can't add the formula. In Updates it doesn't return any results.
Also, someone should go through the instruction over again. It's unclear and there are errors. It mentions both datasets, tickets and updates by the way.
1
Dane
I have tested it on my end and the information of the Deleted user is still present on tickets that has already been closed. Please refer to the screenshot below. Take note that I set the agent name on this example as "Delete User". It has nothing to do with the behavior of Explore.
However, if you downgrade users, Explore users might experience issues with some reports. Potential issues include:
1
Permanently deleted user
If I sort this metric by Group - will I be losing data once an agent is offboarded and deactivated? Similar to how the number of public comments will change if you deactivate agents that are no longer considered agents (assuming you used the role:agent fiter)?
0
Dane
You can try to use Example 2: and instead of organization you can use the Ticket Groups attribute.
0
Dayana
Hello, so, is not a way to measure the time a ticket was assigned to each group when my ticket could be assignee to several and differents groups?
0
Dave Dyson
0
Qin Brian
Worse than you. Lost the data from long long time ago.
0
Yasmany Campos
Thank you so much
0
Kyna (Ky)
Hi! Anyone else encountered issues with data pulled from the Time Tracking app? We have 0 data about Status time, etc since Apr 26, 2022. Any dates prior to Apr 26 have complete populated data.
0
Sign in to leave a comment.