View Ticket Center analytics
Read ticket volume, average time to resolve, first response against response targets and category usage for a date range.
Analytics shows how your Ticket Center is doing: how many tickets come in, how fast they are solved and whether first replies meet their response targets. Open it under Management → Ticket Center → Analytics.
Why it matters
Figures show where help is needed. A spike before exams, a category that keeps growing or response targets that are often missed tell you where to add people, write a handbook page or change priorities.
Before you start
| Requirement | Detail |
|---|---|
| Permission | View analytics |
| Data | Tickets created in the chosen period |
| First response figures | Priorities with a response target. See Set up the Ticket Center. |
How to read your figures
Open Management → Ticket Center and click Analytics. The page title is Support analytics.
Set the Date range. The default is the last 90 days. You can pick up to 366 days, but no future dates and no dates before your institution was created.
Read the key figures at the top, then the charts below.
Key figures
| Figure | Meaning |
|---|---|
| Tickets created | Tickets created in the period |
| Average time to resolve | Average time from creation to resolution |
| First response (SLA) | Share of tickets whose first staff reply met their priority's target, shown as "x of y eligible tickets". Tickets without a target, and tickets still inside their window without a reply, are left out. |
| Most used category | The category used most often |
| Busiest day | The day with the most new tickets |
Charts
| Chart | Shows |
|---|---|
| Ticket volume over time | Created tickets per day in your time zone. Empty days show as zero, so peaks stand out. |
| Category usage | How often each category was used. Tickets without one count as Uncategorized. |
| First response vs resolved | First replies that met the target, compared with tickets actually resolved |
Common pitfalls
| Pitfall | What happens | What to do |
|---|---|---|
| "No tickets in this period" | The range is too short | Choose a wider Date range. |
| First response (SLA) shows "Not enough data" | No tickets with a priority target in the period | Set up priorities with response targets. |
| Comparing with last year | The range is capped at 366 days | Compare two ranges one after the other. |
FAQ
Do internal notes count as a first response?
No. Only a public reply from staff counts.
Which time zone do the charts use?
Your own time zone.