Skip to main content

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:

LimitFreeCommunityPro
Analytics retention30 days12 monthsUnlimited

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 users

The Overview tab is the baseline health check for a server.

AreaWhat it shows
SummaryTotal tickets, resolution rate, SLA compliance or average first response, and average resolution time
Ticket volumeTickets created and closed over time
Category distributionEach category's share of tickets
SLA by categoryCompliance, 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.

MetricMeaning
Team MembersActive staff included in the selected range
ClosedTickets closed, with the number claimed
ResolvedTickets credited to a resolver, and how many members earned the credit
Team Avg ResponseAverage 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.

ColumnDescription
#Position in the current sort
Staff MemberNickname and avatar, matching the name shown in Discord
ClaimedTickets the staff member claimed
ClosedTickets the staff member pressed close on
ResolvedTickets credited to them as the resolver
MsgsMessages the staff member sent in tickets
TicketsDistinct tickets they posted in
Avg ResponseAverage time to first response, over tickets they answered first
Avg ResolutionAverage time from open to close, over tickets they closed
Avg HandleAverage time from claim to close, over the ones they claimed
CSATCustomer satisfaction score, when ratings exist
Days #1Days 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.

AreaWhat it shows
SummaryAverage SLA compliance, average throughput, peak hour, and active data hours
SLA over timeDaily SLA compliance
Throughput trendTickets processed per hour, by day
Peak hoursTicket 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.

AreaWhat it shows
SummaryCSAT score, satisfaction rate, response rate, and total ratings, with period comparisons
Ratings over timeDaily rating volume and average rating
CSAT by response timeCSAT grouped by first staff response speed
Staff leaderboardCSAT by attributed staff member
Low-rating watchlistRecent 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

CadenceReview
DailySummary cards for unusual changes
WeeklyTeam workload, SLA trends, and coverage gaps
MonthlyVolume, 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.