Use support measures to choose an improvement
Read the Desk overview in context and turn a service question into a useful next action.
Use support measures to choose an improvement
Start a support review with a question: are customers waiting too long, is unassigned work growing, or is one type of request repeatedly returning? A number is useful only when it answers a clearly defined question.
Read the Desk overview
1. Select the intended desk and open Overview. Review the date scope and the Department, Assignee, SLA focus and Status controls before interpreting the cards.
2. Read each measure with its label and context. Open tickets, Avg. resolution and Channel snapshot describe different things; do not divide unrelated cards to invent a completion rate.
3. Compare relevant tickets through Tickets, using their actual identities, states and history. Check whether the records belong to the same period and service scope as your question. A filtered list is not necessarily every ticket in the desk.
Make the comparison meaningful
For an on-time response measure, define the included requests, response event, target and service calendar first. A first response, a later reply and resolution are separate events. Do not average calendar hours and business hours as though they were the same measure.
Show the count behind a percentage. “8 of 10 requests received a first response within target” is more informative than “80%” alone. Keep requests with missing information visible rather than silently treating them as successful or assigning them a zero duration.
When comparing periods, use the same definitions and explain changes in workload or scope. An unexplained value or percentage needs its underlying definition and records; do not silently correct it to a more plausible number.
Choose one practical change
If older unassigned requests dominate the backlog, agree who will review that queue and when. If repeated questions consume capacity, improve the relevant instructions and check the next set of requests. Name an owner, a review date and the measure you expect to change.
Your result is one justified improvement, not a dashboard screenshot presented as a complete service assessment. Revisit the same question after the change and distinguish the observed result from an assumed cause.
Continue learning
In this series: Handle support requests — guide 13 of 14.
Turn what you learned into the way the team works.
Mark this lesson complete once the workflow exists in your workspace—not simply when you reach the bottom.