Discord ticket analytics turns your closed and open tickets into numbers: how many were opened, claimed and closed, how fast staff respond on average, and who's doing the most work. Without it, "is our support actually good" is a guess based on whichever tickets you personally remember. Noxyr's ticket analytics dashboard tracks all-time totals, a 24-hour delta, a per-period breakdown with charts, and a top-5 staff leaderboard by closes, reply speed and messages. This guide covers what each number means and how to read it without over-interpreting a small sample.
What the dashboard shows
Four headline cards sit at the top: all-time tickets created, all-time closed, all-time claimed, and the average rating out of 5 (from the ratings feature, if you've turned it on). Each of the first three also shows how many happened in the last 24 hours, so you can tell a slow week from a genuinely slow month at a glance.
Below that, a period selector - 7, 14, 30 days, or all time - drives everything else on the page: opened, claimed, closed, average response time, and messages per day for that window, plus two charts. One plots opened/claimed/closed by day; the other plots average response time against message volume, so you can see whether a busier week also meant a slower one.
How "average response" is measured
Response time on this dashboard is the average time between a member's message in a ticket and the next staff reply, averaged across the tickets in the selected period. A single very slow overnight reply can pull the average up noticeably in a slow week, so treat it as a trend across periods, not a precise SLA number for any one ticket. If you need to know why one specific ticket took long, the transcript is the source of truth - see our transcripts guide for how those are saved and searched.
The staff leaderboard
The Most Active Staff section ranks up to five staff members for the selected period by ticket closes, and shows their average reply time and total messages sent in tickets alongside it. It's designed to exclude self-closed tickets where possible, so a member closing their own resolved ticket doesn't get counted as staff activity.
Use this for recognizing who's actually carrying ticket volume and for spotting a staff member whose reply time is consistently much slower than the rest - that's a coaching conversation, not a numbers problem. Don't use raw close counts alone to judge quality: a staff member handling five complicated escalations looks "less productive" by closes than one handling twenty one-line questions, even if the harder work matters more.
Reading the charts without overreacting
- A spike in opened tickets with a flat closed line for a day or two is normal after any announcement, sale, or outage - watch whether closed catches up within the period, not whether the spike happened at all.
- Claimed staying well below opened over a full week, not just one day, is the real signal that staff are understaffed or claiming isn't part of the workflow yet. See our claiming guide if claim rates look low because staff just aren't using the claim command.
- Response time creeping up over several periods in a row is worth checking against ticket volume on the same chart - if messages per day rose at the same rate, it's a staffing problem, not a motivation problem.
What analytics can't tell you
The dashboard counts tickets and messages; it doesn't read them. It won't tell you which specific answers are wrong, which panel's welcome message is confusing people into opening the wrong kind of ticket, or whether a "closed" ticket was actually resolved versus abandoned. Cross-reference a concerning number against actual transcripts and close reasons before changing a policy based on a chart alone - the numbers tell you where to look, not what you'll find.
Getting more staff to look at it
The page is at Tickets Analytics in the dashboard nav, separate from the main Tickets management page. If you want more of your team checking response times regularly rather than only when something feels off, put the link somewhere staff already look - a pinned message in your internal staff channel works better than assuming people will find it in the dashboard on their own.
A simple weekly habit
You don't need a dashboard ritual to get value from this page - checking it once a week is enough to catch a slow drift before it becomes a pattern nobody remembers the start of. Look at three things in order: did opened tickets change noticeably, did response time move in the same direction as message volume (expected) or the opposite (worth asking why), and does the staff leaderboard still roughly match who you'd expect to be busy. If all three look normal, the check took thirty seconds. If one doesn't, that's the thread to pull before it shows up as a complaint instead of a number.
Common questions
Does analytics cost anything extra? No, it's included with Noxyr's free ticket system, same as the rest of the module.
Can I export the data? The dashboard is the view; there's no built-in CSV export for ticket analytics specifically.
Does the staff leaderboard include admins who never touch tickets? Only staff who've actually closed, claimed or messaged in tickets during the period show up - it's activity-based, not a static staff list.
Why does my average rating say "No ratings yet"? Ratings have to be turned on and at least one member has to submit a score before an average shows - see the ratings guide to enable it.
Is "all time" actually every ticket ever, or capped? The all-time cards reflect your full ticket history in the database; the period charts are limited to the selected window (7/14/30 days or all time).
Check your numbers on the dashboard, or start from scratch with Noxyr's free ticket bot.