Two numbers, one gap

Tickets opened tells the client how much they asked for. Tickets closed tells them how much they got. The gap, carried forward, is backlog, and backlog is what the client feels as slow. Present all three. A quarter that opened 134 and closed 128 added six to the queue; say whether that six is normal for the client's size or a trend.

Reading the direction

Volume rising while recurring incidents stay flat usually means the client grew: more people, more devices, more requests. That is a scope conversation, and it is a good one to have before the contract is quietly underwater. Volume rising with recurrence rising means something broke and keeps breaking; that is a project conversation, and the recurring incidents note covers it. Volume falling with satisfaction flat is the best quarter you will have; say so plainly, take the credit in one sentence, and move to the next finding.

The ask

Ticket volume rarely produces a decision on its own. It produces context for one: a scope change, a per-seat adjustment, a self-service change for the request type that doubled. Bring the request-type breakdown in the appendix and ask for the one change that would remove the biggest category.

  • Confirm the seat and device count the contract assumes.
  • Agree one request type to move to self-service or to remove.

Volume is a source row, not a headline

Opened and closed belong in every brief as source rows; they become a finding only when the gap moved. A brief that prints the two periods side by side and ties each finding to its row keeps the volume where it belongs. Sourcerow does that from the ten-field template; the request-type breakdown stays in your PSA.

A worked example

A client opened 112 tickets last quarter and 134 this quarter; closed went from 106 to 128. Both quarters left six in the queue at period end, so the backlog did not move. Recurring incidents rose in the same period, and the recurring-incidents note explains why that combination points at one appliance rather than at the helpdesk.

Without that second number, 134 looks like the client became harder to serve. With it, 134 is 115 ordinary requests plus nineteen repeats of one fault. The page shows opened and closed in the source rows, lists the fault under findings, and asks for the fix. Volume itself gets one clause in the headline and no chart. A client who wants the breakdown by request type gets it in the appendix, which is where curiosity belongs.