Best practices and recipes
- Boosting team productivity overview
- Zendesk Support recipes reference
- Zendesk Support best practices docs
- Gaming companies share tips on using AI in customer support
- Fine Tuning: How to piece together your ideal Zendesk
- Insights recipe: First reply time by event (version 2)
- Insights recipe: Reporting on internal tickets
- Insights recipe: Reporting on multi-select fields using ticket tags
- Insights recipe: Inbound Calls by Wait Time
- Insights recipe: Troubleshooting custom metrics for the Ticket Events data model
- Best practices for deleting groups
- Insights recipe: Reporting on macros using tags in Insights
- Insights recipe: Filtering for follow-up tickets
- Insights recipe: Solved tickets moved between groups
- Insights recipe: Bad ratings with comments
- Insights recipe: Average resolution time without Pending or On-hold time
- Insights recipe: New, Open, and Solved tickets headline reports
- Recreating native ticket metrics with Insights event data
- Insights recipe: Reporting on a numeric field that has a constant value
- Insights recipe: Reporting on nested drop-down fields
- Insights recipe: Measuring the number of incidents by problem
- Insights recipe: Reporting on CSAT and one-touch tickets
- Insights recipe: Agent contributions at the update level
- Insights recipe: Unsolved tickets by group
- Understanding tags and ticket fields
- Insights recipe: Reporting on full resolution time
- Insights recipe: Solved tickets by agent
- Insights recipe: One-touch tickets
- Insights recipe: Tickets by time of day created
- Insights recipe: Work time between first reopen and final solve using Time Tracking
- Boosting team productivity overview
- Zendesk Support recipes reference
- Zendesk Support best practices docs
- Gaming companies share tips on using AI in customer support
- Fine Tuning: How to piece together your ideal Zendesk
- Insights recipe: First reply time by event (version 2)
- Insights recipe: Reporting on internal tickets
- Insights recipe: Reporting on multi-select fields using ticket tags
- Insights recipe: Inbound Calls by Wait Time
- Insights recipe: Troubleshooting custom metrics for the Ticket Events data model
- Best practices for deleting groups
- Insights recipe: Reporting on macros using tags in Insights
- Insights recipe: Filtering for follow-up tickets
- Insights recipe: Solved tickets moved between groups
- Insights recipe: Bad ratings with comments
- Insights recipe: Average resolution time without Pending or On-hold time
- Insights recipe: New, Open, and Solved tickets headline reports
- Recreating native ticket metrics with Insights event data
- Insights recipe: Reporting on a numeric field that has a constant value
- Insights recipe: Reporting on nested drop-down fields
- Insights recipe: Measuring the number of incidents by problem
- Insights recipe: Reporting on CSAT and one-touch tickets
- Insights recipe: Agent contributions at the update level
- Insights recipe: Unsolved tickets by group
- Understanding tags and ticket fields
- Insights recipe: Reporting on full resolution time
- Insights recipe: Solved tickets by agent
- Insights recipe: One-touch tickets
- Insights recipe: Tickets by time of day created
- Insights recipe: Work time between first reopen and final solve using Time Tracking