Explore is designed to slice and dice data by categories and fields, but sometimes you need a random selection of tickets to undertake an audit. This recipe uses the Support: Tickets dataset to pull a random selection of tickets, which you can then use to audit individual agents or ticket groups.
This article contains the following topics:
- What you'll need
- Returning a random selection of tickets
- Auditing individual agents
- Auditing ticket groups
- Next steps
What you’ll need
Skill level: Intermediate
Time required: 15 minutes
- Zendesk Explore Professional or Enterprise
- Editor or Admin permissions (see Giving agents access to Explore)
- Ticket data in Zendesk Support
Returning a random selection of tickets
- In Explore, click the reports (
) icon.
- In the Reports library, click New report.
- On the Select a dataset page, click Support > Support - Tickets, then click Start report. The report builder opens.
- Click the Calculations (
) menu > Standard calculated metric.
- Name this metric Random.
- In the Formula field, enter the following:
RANDOM()
Tip: If you're working in a language other than English, read this article to help you enter Explore formulas in your language. - Click Save.
- Apply any necessary filters, like date range, group, channel, or satisfaction rating.
- In the Metrics panel, click Add and add your calculated metric.
From here, you can audit individual agents or entire ticket groups, depending on your needs.
Auditing individual agents
- In the Rows panel, click Add and add Assignee name.
- Next to Filters, click Add and add Assignee role.
- Click the Assignee role filter (the gray box) and select Agent and/or Admin as appropriate based on your auditing needs.
- From the Result manipulation (
) menu, select Top/bottom.
- In the Top field, specify how many results you want per assignee.
- In the Strategy field, select Per block on rows.
- In the Rows panel, click Add and add Ticket ID. This gives you a "top X" tickets per person based on your random metric.
Note: Adding any other metric or attribute will change the ticket IDs displayed.
From here, you can click the ticket ID and select Open link to look at the ticket. Alternatively, you can click the drop-down arrow next to Save and choose Export to create a CSV or Excel file with your results.
Auditing ticket groups
- In the Rows panel, click Add and add Ticket group.
- From the Result manipulation (
) menu, select Top/bottom.
- In the Top field, specify how many results you want per group.
- In the Strategy field, select Per block on rows.
- In the Rows panel, click Add and add Ticket ID. This gives you a "top X" tickets per group based on your random metric.
Note: Adding any other metric or attribute will change the ticket IDs displayed.
From here, you can click the ticket ID and select Open link to look at the ticket. Alternatively, you can click the drop-down arrow next to Save and choose Export to create a CSV or Excel file with your results.
Next steps
For more information about the metrics and attributes you can use with the Tickets dataset, see Metrics and attributes for Zendesk Support.
13 comments
Bobby Koch
This is great - how would we "delay" the random list of tickets? Every time i refresh the page, the tickets re-randomize. Could I bake in a time delay to only refresh once every hour?
0
Maude
Hi Bobby,
It's not possible to "freeze" the results for a certain amount of time while refreshing.
Performing a refresh means that the function runs again, giving a new set of random data.
One thing that I can advise here, is to export your query the first time you run it. By doing this you'll be able to have that results saved and go back to it whenever you want to.
Hope that helps! :)
0
Bobby Koch
Hiya Maude! thanks for the reply - appreciate you.
I think where this turns into an issue is with email deliverability. We have a group of team leads that are supposed to audit these tickets, but we need them to all receive the same tickets, without creating a group. right now, if I set a schedule to send to you and me (not tied to a group) it will generate two completely separate lists of tickets. Just some feedback as it would be nice to be able to randomize on a schedule to avoid inconsistencies. i am sure there is a counter argument as well!
Cheers, Bobby
0
Gerald J
Is there a way that I can extract or limit the number of random tickets? for example I want to only get 10% of the total solved for the week
0
Sarah V
Hi,
This is great, thanks for the recipe!
Would it be also possible to add a column with the initial ticket text (first message from the requester)?
Thanks,
Sarah
0
Elaine
I don't see an option at this since Explore doesn't capture the content of ticket comments you may include the ticket subject attribute. You may also check the lists of attributes that you can use in this article. Hope that helps!
0
Sarah V
Hi Elaine,
Thank you for your reply. I'm trying my luck with the json data export from the Admin Center now to get the ticket description text :-)
0
Lindsey Rhyne
I gave this a go and the report is working, except that the results don't refresh? I expected to see a new random sample each time I refreshed the report or the page. Anyone know how to fix this?
0
Tony
I think it might be related to the fact that reports do not refresh constantly. As this article mentions:
Data refresh intervals for Explore reporting
I hope this helps. If you want to check that further, you can reach out to our support.
Best,
0
John Ara
Hello.
How do we filter the random selection tickets by month or custom dates?
For example, I want to monitor tickets from the month of February 2024 (February 1-29, 2024) or the week of March 4-9, 2024.
I would like to check if it is possible to filter only closed or solved tickets.
I also want to see a few individuals only instead of getting all the assignees.
Thank you.
0
Noly Maron Unson
Hi John,
You can add filter to the report like Ticket status (to filter the Solved/Closed tickets), Tickets created - date and Assignee name. This will make it that the random tickets that will appear will still adhere to the filter you have set.
Hope this helps.
0
Denise Sehlmeyer
Question, what's the difference between 0 & 1 in the ‘Random’ Column?
0
Alex Zheng
I believe this is just the random selection so each ticket is randomly assigned a value of 0 or 1.
0