Analytics
Use Analytics to understand ticket volume, response speed, SLA health, team workload, and customer satisfaction.
Analytics access
| Capability | Free | Community | Pro | Org plans |
|---|---|---|---|---|
Overview tab | ||||
Team tab | ||||
Operations tab | ||||
Feedback analytics tab |
Analytics data retention is plan-driven. Organization plans provide the Pro server tier to member servers, so they match the Pro column:
| Limit | Free | Community | Pro |
|---|---|---|---|
| Analytics retention | 30 days | 12 months | Unlimited |
Collecting ratings is a separate feature with its own plan rules. See Feedback & Ratings.
Date ranges
Choose a range at the top of the page. All tiers include recent ranges such as Today, Yesterday, and the last 7, 14, or 30 days. Custom ranges are available within your plan's retention window, shown in the table above. Plans with unlimited retention also include the All time range.
Overview tab
Available to all usersThe Overview tab is the baseline health check for a server.
| Area | What it shows |
|---|---|
| Summary | Total tickets, resolution rate, SLA compliance or average first response, and average resolution time |
| Ticket volume | Tickets created and closed over time |
| Category distribution | Each category's share of tickets |
| SLA by category | Compliance, average response time, and default vs. custom targets, when SLA is configured |
SLA tracking is Pro
Set SLA targets in Settings for the server default, or in Categories for category-specific overrides. Free and Community servers show average first response time instead of SLA compliance.
Team tab
Pro per-server plan and all organization plans
The Team tab compares staff workload and response performance.
| Metric | Meaning |
|---|---|
| Team Members | Active staff included in the selected range |
| Closed | Tickets closed, with the number claimed |
| Resolved | Tickets credited to a resolver, and how many members earned the credit |
| Team Avg Response | Average first staff response time, with average CSAT when ratings exist |
The staff table is sorted by resolved by default. A podium above it highlights the top three on whichever column you sort by, and the rank column follows the same sort. Sorting a column the other way round hides the podium, since the top three would then be whoever is doing the least.
| Column | Description |
|---|---|
| # | Position in the current sort |
| Staff Member | Nickname and avatar, matching the name shown in Discord |
| Claimed | Tickets the staff member claimed |
| Closed | Tickets the staff member pressed close on |
| Resolved | Tickets credited to them as the resolver |
| Msgs | Messages the staff member sent in tickets |
| Tickets | Distinct tickets they posted in |
| Avg Response | Average time to first response, over tickets they answered first |
| Avg Resolution | Average time from open to close, over tickets they closed |
| Avg Handle | Average time from claim to close, over the ones they claimed |
| CSAT | Customer satisfaction score, when ratings exist |
| Days #1 | Days in the range they finished as the server's top staff member |
Resolved is not the same as closed
Whoever presses close gets the Closed count. Resolved goes to the last staff member to reply before it closed, or failing that its claimer or closer, so the person who did the work is credited even when someone else sweeps the queue shut. One resolver per ticket, and resolution also counts self-closed and auto-closed tickets that Closed does not, so the two columns will not add up to each other.
Use this tab to recognize strong performers, find coverage gaps, balance workload, and identify where training or staffing changes would help.
Operations tab
Pro per-server plan and all organization plans
The Operations tab focuses on capacity planning.
| Area | What it shows |
|---|---|
| Summary | Average SLA compliance, average throughput, peak hour, and active data hours |
| SLA over time | Daily SLA compliance |
| Throughput trend | Tickets processed per hour, by day |
| Peak hours | Ticket volume by hour of day, for scheduling coverage |
Feedback analytics tab
Pro per-server plan and all organization plans
The Feedback analytics tab is the advanced CSAT view of the ratings described in Feedback & Ratings.
| Area | What it shows |
|---|---|
| Summary | CSAT score, satisfaction rate, response rate, and total ratings, with period comparisons |
| Ratings over time | Daily rating volume and average rating |
| CSAT by response time | CSAT grouped by first staff response speed |
| Staff leaderboard | CSAT by attributed staff member |
| Low-rating watchlist | Recent low ratings with comments, staff, and category |
Working with the data
Configure SLA targets
Set the server default
In Settings → Automation, set Target Response Time on the Default Ticket SLA card.
Override by category
Open Categories → [Category] → General for categories that need different targets.
Track compliance
Review Analytics → Overview and Analytics → Operations.
Review cadence
| Cadence | Review |
|---|---|
| Daily | Summary cards for unusual changes |
| Weekly | Team workload, SLA trends, and coverage gaps |
| Monthly | Volume, category mix, peak hours, and goal progress |
Troubleshooting
No data available
- No tickets were created in the selected range
- The range exceeds your plan's retention window
- Snapshots have not generated yet, usually during the first 24 hours after install
Fix: expand the date range, wait for snapshots, or create test tickets.
Advanced analytics not available
Team, Operations, and Feedback analytics require a Pro per-server plan or an organization plan.
Data seems outdated
Snapshots are generated daily at 1 AM. Today's data updates hourly, and full historical data updates overnight.