Build a Zendesk Scorecard for Speed, Volume and Satisfaction
A weekly support scorecard should show whether the queue is getting busier, whether first replies are slowing and how customers rated the experience. Report each measure with its own cohort and denominator.
Worked example
Illustrative channel scorecard
Email = 140 created, 131 with first replies; median 45 business minutes Chat = 32 created, 30 with first replies; median 4 business minutes Email CSAT = 18 positive of 20 rated, 100 invited; 90% positive, 20% coverage Chat CSAT = 9 positive of 10 rated, 15 invited; 90% positive, 66.7% coverage
Steps
- List created-ticket volume and first reply time in the Support Tickets dataset for the same channel and reporting window. Specify calendar or business hours and show how many tickets had an eligible reply.
- Use the Surveys dashboard or reporting view available in your configuration to record positive responses and total valid ratings for each channel.
- Show these counts beside the headline rates. Report survey coverage separately when you have the invitation count for the corresponding cohort.
- Check which channels generate surveys and which tickets contribute to first reply time. Mark small groups and incomplete recent periods for review.
What to check
- Use your actual survey scale and its positive-response definition. Combined results can be misleading when teams use different surveys.
- Check whether a metric uses created date, reply date or survey response date. Label each separately even when they share a weekly display.