Blog · Board and management reporting · Customer service
A ticketing dashboard compares queue workload and customer waiting times from support exports. This example reconciles opening and closing backlog, works response and resolution measures from ticket rows, and explains the decisions each measure supports.
A ticketing dashboard compares support demand, backlog, first response time, and resolution time by queue. Build it from a dated ticket export and explain exactly which tickets each timing measure includes. Its purpose is to show where customer waits and unfinished work require action.
Use a historical export with ticket ID, created timestamp, first qualifying agent reply, resolution timestamp, queue, priority, and status at the reporting cutoff. If available, bring status and queue-change history so opening backlog and movements can be reconstructed. A present-day status alone cannot reliably tell you what was unresolved at a past cutoff.
Choose calendar hours or staffed business hours and label the choice. Calendar time includes nights and weekends. Business time requires the actual service calendar and holiday rules. Subtracting timestamps produces elapsed time; it does not automatically apply a service schedule.
Define a qualifying response before measuring it. An automated acknowledgment may reassure a customer, but counting it as an agent reply would change the meaning of first response time. Similarly, choose first resolution or final resolution after reopenings and retain that policy across comparisons.
Use creating a dashboard to choose the business question and audience before arranging charts. A service manager needs queue exceptions and an action owner more than a long list of totals.
Consider a US business reviewing the week of March 2 through March 8, 2026, ending immediately before March 9. Its ticket-event export gives these counts. There are no reopenings, transfers, merges, deletions, or other adjustments in this example.
| Queue | Opening unresolved | New tickets | Resolved in week | Closing unresolved |
|---|---|---|---|---|
| Billing | 2 | 3 | 4 | 1 |
| Technical | 2 | 3 | 2 | 3 |
| Total | 4 | 6 | 6 | 4 |
Closing backlog = Opening backlog + New tickets - Resolved tickets + Net other adjustments
Billing proves as 2 + 3 - 4 = 1. Technical proves as 2 + 3 - 2 = 3. The company check is 4 + 6 - 6 = 4, matching the sum of the closing queue balances.
An unchanged company backlog hides the movement: Billing completed more tickets than arrived, while Technical completed fewer. That directs the manager to inspect Technical's work mix, oldest unresolved tickets, and available expertise. It does not prove that its agents worked less efficiently.
In a real export, show reopened work and transfers as explicit movements. A queue transfer changes the two queue balances but does not create another company ticket. If you cannot explain the bridge, investigate the records before interpreting a backlog trend; the dashboard audit gives the reconciliation method.
For this example, use the six tickets resolved during the week for both timing measures. This is a resolved-ticket cohort, including tickets created before the week. It does not measure first replies sent during the week or the experience of all newly created tickets.
The duration columns below are calendar-hour intervals from the exported timestamps. First response runs from creation to the first qualifying reply; resolution runs from creation to resolution. All six tickets have valid timestamps and no pauses.
| Ticket | Queue | First response (hours) | Resolution (hours) |
|---|---|---|---|
| B-101 | Billing | 1 | 8 |
| B-102 | Billing | 2 | 16 |
| B-103 | Billing | 1 | 24 |
| B-104 | Billing | 4 | 48 |
| T-101 | Technical | 2 | 20 |
| T-102 | Technical | 6 | 60 |
| Sum | 16 | 176 |
Mean first response time = Sum of eligible first response durations / Eligible ticket count
Mean resolution time = Sum of eligible resolution durations / Eligible resolved-ticket count
Billing response time is (1 + 2 + 1 + 4) / 4 = 2.0 hours. Technical response time is (2 + 6) / 2 = 4.0 hours. Billing resolution time is (8 + 16 + 24 + 48) / 4 = 24.0 hours; Technical is (20 + 60) / 2 = 40.0 hours.
Across all tickets, response is 16 / 6 = 2.7 hours and resolution is 176 / 6 = 29.3 hours, rounded to one decimal. Do not average the queue resolution means: (24 + 40) / 2 = 32.0 hours incorrectly gives the smaller Technical cohort the same weight as Billing.
With the detail table in A1:D7, Google Sheets can calculate Billing's mean resolution time as:
=AVERAGEIFS(D2:D7,B2:B7,"Billing")
Google's AVERAGEIFS documentation describes averaging values that meet specified criteria. Show the eligible count alongside the result so a change in the ticket population remains visible.
The median adds another view of the same rows. Sorted resolution durations are 8, 16, 20, 24, 48, and 60 hours, giving (20 + 24) / 2 = 22.0 hours. First response durations sort to 1, 1, 2, 2, 4, and 6, giving a median of 2.0 hours.
=MEDIAN(D2:D7)
Google's MEDIAN documentation explains that an even-sized dataset uses the two central values. The difference between the median and mean here tells the manager to inspect the longer cases; neither figure replaces the individual ticket history.
Covirage is not affiliated with Google.
The support operations owner should maintain the definitions, reporting clock, and backlog reconciliation. Queue leads own investigation and follow-up. Finance or commercial teams can contribute customer context when a queue problem affects a contractual commitment, but the support lead should validate the service event first.
Keep an exception table beside the headline measures: queue, finding, affected ticket IDs, owner, next action, and review date. Compare the same definitions over successive periods using a performance dashboard. Separate a staffing decision from a product-defect escalation, since each requires different evidence.
Upload a ticket export with its timestamps, queue labels, and reporting definitions. Covirage maps the columns, and its tools compute and check the figures; the external AI model explains the results with every figure traced to its rows. Create a free Covirage account and bring a sample of your own data.
See Covirage for customer service teams for the supporting business context.
Include opening backlog, newly created tickets, resolved tickets, and closing backlog by queue. Add first response and resolution times with their eligible ticket counts. Show the reporting cutoff and whether the clock measures calendar hours or staffed business hours.
First response time measures how long a customer waits for the first qualifying agent reply. Resolution time measures the interval from creation to the defined resolution event. Both require an agreed clock and rules for automated messages, reopened tickets, and paused periods.
Do not assign unresolved tickets a completed resolution time or a zero. Report their current age separately. A completed-ticket average describes tickets that finished; the unresolved backlog shows work and customer waits that the completed cohort cannot describe.