Stats & Reports
Read the Stats page: what each number measures, how it is calculated, and where to find team, rating, response-target, mood, and AI numbers
Stats (called Analytics in earlier versions of the dashboard) shows how your support is performing across every bot you own or manage: how many tickets are open and waiting, how many came in and were closed, how quickly staff answer, when members open tickets, who on your team handles the most, and which members come back. It is for owners and team leads who want to spot bottlenecks and fair staff numbers without counting tickets by hand.
Opened from a bot's page, it counts that bot's servers; opened from inside a server (with Stats in the sidebar), every number, chart, and block counts that server. Show all servers under the title switches back to the account-wide view.
Stats are included from the Basic plan up; on Free the page says "Stats come with a paid plan". The response-target warnings and Reply and close targets need Enterprise (SLA Management), and the mood and AI blocks only fill in when those features have produced data on your servers.
Time range
One time range at the top of the page drives every block on it: 7 days, 30 days, or 90 days (30 days when you open the page), or Pick dates for one of these:
- Calendar months: the current month and the 11 before it. The current month counts up to now.
- Custom range: a From and a To date, both days included. A range can cover up to 366 days, must end today at the latest, and cannot start before 2015. Apply shows it; when the dates do not fit, a line under them says why.
With a month or custom range picked, the button shows it and the line under the page title names the month or the dates ("How all your servers did from March 3, 2026 to April 2, 2026."). Days start and end at midnight in your browser's time zone.
The choice stays in the page address, so going back, reloading, or sharing the link keeps it; a link whose range cannot be shown (for example, one that ends in the future) opens the default 30 days instead. The team page and each staff member's page have the same time range, and links between Stats, the team page, and a staff member's page keep it.
Numbers marked "the period before" compare with the period of the same length just before the selected one:
- the 30 days before the last 30 days;
- the previous month for a month;
- the same number of days before a custom range (a range of March 11 to 20 is compared with March 1 to 10).
While the selected month, or a range that ends today, is still running, the comparison covers only the same stretch of the period before, so a half-finished month is not measured against a whole one.
Numbers are cached for a few minutes, so a ticket closed a moment ago may take a short while to show. An update received while numbers are being calculated prevents that older result from being reused on the next refresh. Days in the charts, Busiest hours, and Staff coverage are in your browser's timezone.
The main page
From top to bottom:
- A response-target warning when there is one.
- Four numbers.
- Right now (see Right now).
- The Opened and closed chart: tickets opened per day, and tickets closed per day by the day they closed, whenever they were opened; days are in your timezone. For a range longer than 120 days the chart shows one point per week, starting on Monday, labelled "Week of" its first day.
- Closed without a reply (see Closed without a reply).
- Busiest hours and Top ticket types.
- Your team.
- More stats, which is folded until you open it (the page remembers whether you left it open).
When SLA tracking is on and open tickets have used 80% or more of a response target, a line at the top says how many, broken down by Critical, High, Medium, and Low, with See open tickets. Like the rest of the page, the warning counts all your bots, one bot, or one server, and See open tickets opens the open tickets of the same bot or server.
The four numbers
| Number | What it measures |
|---|---|
| Open now | Tickets open right now. The line under it says how many are still waiting for a first staff reply, or "Every open ticket has a reply". See open tickets opens the list |
| New tickets | Tickets opened in the selected range. The line under it gives the all-time total |
| Closed | Tickets closed in the range, counted by when they closed, whenever they were opened: the same count as the closed line of the Opened and closed chart. Deleted ticket channels count as closed. The line under it is described below the table |
| Typical first reply | The median time from ticket creation to the first staff message, over tickets opened in the range that received one: half of those tickets were answered faster. Staff writing in a ticket they opened themselves is not a first reply. The lines under it are described below the table |
Closed: the line under it is the reopen rate ("4% were reopened later", see Reopen rate) once at least 10 closes in the range can be checked for reopens. Until then it compares the closes with the new tickets ("12 fewer than were opened", "5 more than were opened", or "As many as were opened").
Typical first reply:
- The line under it says how long 9 in 10 of them waited at most (the 90th percentile).
- Responses slower than 7 days are excluded as outliers.
- No replies yet when staff have not replied, Under a minute when the median is shorter than that.
- When Business Hours is on, a second line gives the same median counting only the time inside business hours ("12m counting business hours only"), over the tickets that record it: tickets opened while business hours were on, from the update that added this line. A reply sent while you were closed waited 0 business minutes.
A median is used instead of an average so that one ticket left for days does not make every reply look slow, and a few instant replies do not hide a slow queue.
Medians and 90th percentiles on the Stats and team pages are within 2.5% of the exact value, less than the rounding the page shows.
Reopen rate
The share of closes in the range that were later reopened, the same definition as Reopened on the team pages.
Every close counts, by when it happened, so a ticket closed, reopened, and closed again inside the range is two closes, one of them reopened. A close counts as reopened when the ticket was reopened after it, whether the ticket is closed again now or still open.
Reopens are only recorded for tickets opened from the update that added this number on, so older tickets are left out of both sides of the share; until 10 closes in the range can be checked, the caption compares closes with new tickets instead.
Right now
The open tickets at this moment. The time range does not change this section; it follows the page's scope (all servers, one bot, or one server).
| Block | What it shows |
|---|---|
| Open tickets by age | Open tickets grouped by how long they have been open: under 1 hour, 1 to 24 hours, 1 to 7 days, and over 7 days |
| Who has open tickets | For each staff member, how many open tickets they have claimed (busiest first, up to 8 people), plus how many open tickets nobody has claimed. Click a person for their staff page |
| Waiting for staff | No staff reply yet and Member wrote again after the last staff reply, then Oldest without a reply (see below the table) |
Waiting for staff shows:
- No staff reply yet: open tickets no staff member has answered (the same count as the line under Open now). A ticket opened by a staff member stays here until someone else replies.
- Member wrote again after the last staff reply: answered tickets where the member who opened the ticket sent a message after the latest staff reply, including ModMail DMs. Messages from bots, Atlas, or other people in the channel do not count. On tickets opened before the update that records the member's latest message, only their 100 most recent messages are checked.
- Below, Oldest without a reply lists the five oldest unanswered tickets, each linking to the ticket.
Closed without a reply
Tickets closed in the selected range (by when they closed) that never got a staff reply and that Atlas, the AI assistant, did not solve. This includes tickets the member closed themselves, tickets closed automatically for inactivity, and deleted ticket channels. The card gives the count and links to the five most recently closed.
Your team
The five staff members who handled the most tickets in the range, each with their ticket count and median first reply. In a server's stats it counts that server only. See team opens the team page for the same server and range.
Staff coverage
Inside More stats: when tickets come in compared with when your staff reply, for every weekday and hour of the selected range in your browser's timezone. The aim is to spot hours where members open tickets but few staff are around.
-
The grid: one square per weekday and hour (seven rows of 24 hours on a wide screen, 24 rows of seven days on a phone). Darker squares mean more. Tickets opened shades by tickets opened in that hour, Staff replies by messages your staff sent in tickets in that hour. Point at or tap a square to read its numbers, or use Show as a table for every number.
-
Understaffed hours are striped and outlined. An hour is understaffed when:
- it brings at least 3 tickets and at least an average hour's share of the week's tickets, and
- its share of the week's staff replies (counting that hour and the next, since answers follow arrivals) is less than half its share of tickets.
The sentence at the top names the run of understaffed hours that misses the most replies ("Most understaffed: Saturday 6:00 PM to 10:00 PM"), or says "Staff replies keep up with new tickets at every hour."
-
Staff replies are recorded from the update that added this block. Before any are recorded, the block shows only when tickets come in and names the busiest hours. When recording started inside the selected range, the comparison starts on that day ("Compared from Oct 8") so the days before do not look unstaffed.
-
It appears once at least 20 tickets were opened in the range, like Busiest hours.
-
Staff replies are counted per hour of the day in UTC and placed into your week by the hour's middle, with your timezone's offset on that day (daylight saving time included). In a timezone with a half-hour offset, such as India, each square therefore covers a UTC hour, for example 5:30 to 6:30 PM, shown as 6 PM. Tickets are placed the same way, so the two always line up.
Tickets by reason
Inside More stats: the tickets opened in the range, grouped by the button or menu option the member picked to open them (for applications, the application's title).
Labels that differ only in upper and lower case (for the letters A to Z) or in spaces at the start or end are one row, shown with the newest ticket's spelling. The 8 most common reasons get a row each; the rest share Other reasons. Some tickets get a row of their own:
- Tickets escalated from an Auto Support thread (whose subject is the member's own question) are From Auto Support threads.
- ModMail tickets are ModMail (direct messages).
- Tickets with no recorded button or option (for example, from older panels) are Reason not recorded.
| Column | What it measures |
|---|---|
| Tickets | Tickets with that reason, and their share of all tickets opened in the range |
| Typical first reply | The median time to the first staff reply over those tickets that got one (replies of 7 days or more excluded). None yet without replies |
| Typical time to close | The median time from opening to the latest close over those tickets that are closed (over 365 days excluded). None yet while none is closed |
| Rating | The average star rating of those tickets and how many ratings it comes from. Hidden ratings are left out |
| Reopened | Of those tickets that have been closed at least once, the share that were reopened. Only tickets opened from the update that records reopens count; Not enough data until at least 5 such tickets have been closed |
Every column counts the tickets opened in the range, so a reason's numbers stay together even when a ticket closes or is rated later. Per-reason medians are within 2.5% of the exact value, like every median on the page.
Ratings and low ratings
Inside More stats, when Closing tickets → Ratings is on and members have rated tickets:
-
Ratings:
- the average star rating and how many ratings it comes from (for example "4.6 out of 5 on average · From 3 ratings"), and the same for the period before;
- how many members rated after the bot asked them ("Rated after being asked: 12 of 20");
- how many ratings gave each number of stars.
Ratings count in the period they were given. A request counts as asked once the bot has sent it; members who rated with
/feedbackbefore the request went out are not counted as asked. -
Low ratings: the 10 latest 1 and 2 star ratings in the range, each with what the member wrote, who handled the ticket (the staff member credited on the rating, Atlas when the AI handled it alone, or no staff), the date, and a link to the ticket.
Reply and close targets
Inside More stats, on Enterprise with SLA Management turned on: how often tickets got their first reply on time and were closed on time:
- As a share with counts (for example "90% (9 of 10)"), and the same for the period before.
- The split by priority.
- The trend over the range: both targets together, in about six steps. That is per day for ranges up to 7 days, otherwise steps of a sixth of the range rounded up to whole days, such as 5 days for 30 days, 15 days for 90 days, and 61 days for a year.
Tickets count in the period they were opened. A target still running has no result yet and is left out until it is met or missed. Without Enterprise this block does not appear.
Late first replies
Inside More stats: staff who answered a claimed ticket after its first-response target, with a count and the affected tickets. Only late replies recorded since staff tracking was turned on are included.
Customer mood and AI answers
Inside More stats.
When Tone alerts is on, Customer mood shows how members felt (positive, neutral, negative), the most common feelings, and whether mood improved during tickets. Its Time to close by mood comparison shows the average time from opening to the latest close for closed tickets that ended positive, ended negative, or improved (over 365 days excluded, as in Time to close), and its day-by-day list uses your time zone's days.
When the AI has worked on tickets, AI answers (Atlas) shows how many Atlas closed on its own, how many it helped staff with, and why it handed tickets to staff.
A ticket counts as closed by Atlas on its own (and shows Solved by AI in the ticket list) when Atlas answered it, the member was not handed to staff and did not give an answer a thumbs down, and the conversation shows Atlas's answers settled everything the member asked.
Staff who only greet, thank, or close the ticket do not change that; staff who give or correct part of the answer, or a follow-up question Atlas never answered, do. Tickets Atlas answered without solving count as helped.
Busiest hours and ticket types
| Block | What it shows |
|---|---|
| Busiest hours | The five hours of the day with the most new tickets in the range, in your timezone. It appears once at least 20 tickets were opened in the range |
| Top ticket types | The five ticket types with the most tickets (tickets with no type are left out) |
| Time to close (in More stats) | For tickets opened in the range that are closed: the median time from opening to the latest close, and more (see below the table) |
| Members with several tickets (in More stats) | Members who opened more than one ticket in the range, with their counts |
Time to close, for tickets opened in the range that are closed, shows:
- the median time from opening to the latest close ("Half of them closed within 2h 48m");
- how long 9 in 10 took at most (the 90th percentile);
- how many closed tickets it is based on;
- the same median and 90th percentile for the 6 ticket types with the most closed tickets (over 365 days excluded).
Blocks with nothing to show yet are grouped under Not enough data yet instead of showing empty charts.
Ticket types
Top ticket types, the types under Time to close, a staff member's Top ticket types and the Category breakdown of Scheduled Reports group tickets the same way:
- A channel ticket's type is its Discord category.
- Thread tickets share their parent channel with many others, so a thread ticket's type is the button or menu option it was opened with (spaces at the start or end ignored). A thread ticket with no recorded button or option, or escalated from an Auto Support thread (whose subject is the member's own question), counts under its parent channel.
The team page
Click See team under Your team to open Your team., with a Bot selector (or All bots), a Server selector once a bot with more than one server is picked (or All servers), and the same time range as the Stats page (7 days, 30 days, 90 days, or Pick dates for a calendar month or a custom range, see Time range).
Opened from a server's stats, the team page counts that server only, and links between Stats, the team page, and a staff member's page keep the same bot, server, and period.
With one server selected, the bot owner also sees a Compensation button here. It opens that server's Compensation Reports (Enterprise): what each staff member earned from the tickets they handled.
The top shows Tickets, Handled by staff, Median first reply (with the business-hours median under it when your tickets record one), and Rating (with how many ratings it comes from), each compared with the previous period, then the table Every staff member. Click a staff member's name for their own page (see One staff member).
| Column | Meaning |
|---|---|
| Staff member | Discord display name. Few tickets marks members with fewer than 10 tickets in the period, whose numbers a single ticket can swing |
| Tickets | Tickets attributed to them in the period, with the change against the period before |
| Share of tickets | Their share of all tickets opened in the period |
| Closed | Tickets they closed |
| First reply (median) | The median time to the first staff reply on tickets where they replied first: half of those tickets were answered faster. Replies slower than 7 days are left out. When those tickets record business hours, the median counting only business hours is shown under it |
| Time to close (median) | The median time from opening to close on tickets they closed (over 365 days left out), with the business-hours median under it when recorded |
| Rating | Average customer rating and how many ratings it comes from. Shown in grey with fewer than 5 ratings |
| Reopened | Of their closes in the period, the share that were reopened later, with how many closes it is based on. See Reopens, handoffs, and idle claims |
| Handoffs | Claims they gave up in the period before the ticket closed. Point at the number for the split |
| Idle claims | Open tickets they claimed over an hour ago with no staff reply since, right now |
| Late replies | Missed first-response targets on their tickets, counted when the target was missed |
| Active days | Days in the period, in your time zone, on which they sent at least one reply in a ticket. See Reply activity |
| Hours with replies | Clock hours in the period in which they sent at least one reply in a ticket |
| Messages | Messages they sent in tickets opened in the period |
Click a column title to sort by it; durations and Reopened sort lowest first.
How tickets are counted, as shown on the page: a ticket counts for every staff member who claimed, answered, or closed it, in the period it was opened. Replies after the first response count once the ticket closes. Ratings come from customer feedback on those tickets, and SLA misses count when the breach happened.
The table lists the staff with the most tickets (up to 500). Staff who gave up a claim, have an idle claim, closed a ticket opened before the period, or missed a response target are listed too, even without a ticket in the period.
In Discord, /staff-stats shows these numbers for one server and the last 7, 30, or 90 days, counted the same way.
A median is used for reply and close times so that one ticket left for days does not make a staff member look slow. Like the medians on the main page, they are within 2.5% of the exact value, less than the rounding the page shows.
Reopens, handoffs, and idle claims
-
Reopened: every close counts, by when it happened: the ticket's current close, and each earlier close that a reopen undid. A close counts as reopened when the ticket was reopened after it, at any time since. A member who closes a ticket, sees it reopened, and closes it again has two closes, one of them reopened.
Closes by the member who opened the ticket are not counted. The reopen rate on the main page counts closes the same way, for the whole team. None when they have no counted close in the period.
-
Handoffs: each time their claim on a ticket ended while the ticket was still open (an unclaim), counted by when it ended. The split says whether they released it themselves, it was removed by someone else, it was released automatically (by Auto-unclaim, because the member waited too long for a staff reply), or not recorded (handoffs from before the dashboard recorded who removed a claim). Closing a ticket is not a handoff, and neither is an automatic release after the member stopped answering.
-
Idle claims: the state right now, whatever the period: open tickets they claimed more than an hour ago, where no staff member has replied since the claim. A reply from any staff member clears it. Their staff page lists the 10 oldest, each linking to the ticket.
Reply activity
Active days, Hours with replies, and the When they reply heatmap show when a staff member sent replies in tickets. They are a rough sign of when someone is on duty, not a timesheet: an hour counts as soon as one reply was sent in it, and time spent reading tickets, in voice, or anywhere else leaves no trace.
Replies are counted per clock hour; a period that starts or ends partway through an hour includes that whole hour, and an hour with replies in two servers counts once.
Days and the heatmap use your browser's time zone, daylight saving time included. In a time zone with a half-hour offset, such as India, each hour of the heatmap covers a UTC hour (for example 5:30 to 6:30 PM, shown as 5 PM), and a reply near midnight can count toward the neighbouring day.
One staff member
Click a staff member on the team page to open their own page: their picture and name as the title, the same Bot and Server selectors and time range, and four numbers, each with its change against the period before and the Team median under it:
- Tickets (with the count for the period before)
- Closed (with the share of their tickets)
- Median first reply
- Rating (with how many ratings it comes from)
The team median is the middle value among the staff members of the same bot, server, and period who have that number (staff with tickets for ticket numbers, staff with ratings for the rating), so it shows what a typical member of your team does. With fewer than 10 tickets or fewer than 5 ratings in the period, a note says the numbers rest on too few tickets to judge by.
Below the numbers:
- Claimed, no reply yet: their idle claims, oldest first, when they have any.
- Daily activity: tickets they worked on and closed per day.
- How they work: how many of their tickets they claimed, sent the first reply to, replied to, and closed, plus messages per ticket.
- Top ticket types.
- Compared with the period before: tickets, closed, median first reply, median time to close, the business-hours medians when recorded, rating with its number of ratings, late replies, and messages side by side.
- Reopens and handoffs: their reopened share with how many closes it is based on, and their handoffs split by who removed the claim, each with the team median.
- When they reply: active days, hours with replies, and replies sent, each with the team median, and a weekday by hour heatmap in your time zone where darker squares mean more replies.
- Recent tickets: what they did on each.
- Recent ratings.
Blocks with nothing to show yet are grouped under Not enough data yet. Missed response targets still appear in the comparison even if the staff member has no attributed tickets or ratings in either period; only a member with no tickets, ratings, missed targets, closes, handoffs, idle claims, or replies gets the empty-state message.
What is recorded from this release
Reopens, who removed a claim, reply activity, and business-hours times are recorded from the update that added the staff numbers above. Older tickets still count everywhere else, but:
- Reopened only counts closes of tickets opened since then; with none it reads None.
- Handoffs from before then are listed as not recorded in the split.
- Active days and Hours with replies read Not recorded until replies are recorded. When recording started partway through the period, the page says from which day, and those numbers cover only the days since.
- Business-hours medians appear only once tickets in the period record business hours (Business Hours on).
Export CSV on the team page downloads the table. Its columns:
- staff member, Discord ID;
- tickets, tickets in the previous period, share, closed;
- median first reply and its business-hours median, median time to close and its business-hours median (all in minutes);
- average rating, rating count;
- closes counted for reopens, closes reopened later, reopened (%);
- handoffs with the released, removed, and not-recorded split, idle claims right now, late replies;
- active days, hours with replies, replies sent, and messages.
Empty cells mean no data. This is the only stats export; the main page has none.
Related pages
-
AI usage (under More tools in the sidebar of the dashboard home, or in the account menu): AI token usage per month, separate from stats. Its Insights tab follows the plans of the bots you own or manage, so staff do not need a separate personal AI plan to view eligible managed bots.
-
Scheduled reports: email these metrics daily, weekly, or monthly on Enterprise, under General → Scheduled reports. See Scheduled Reports.
-
Compensation reports: on Enterprise, work out what each staff member earned per ticket, review it and export it, under Compensation. See Compensation Reports.
-
/statsin Discord shows a compact version for one server. See Staff Tools. -
The home page of each server shows:
- Total tickets (all time)
- New today (since midnight in your time zone)
- Active tickets (open now)
- Typical first reply (the median time to the first staff reply for tickets opened in the last 30 days; No replies yet when staff have not replied, Under a minute when it is shorter than that)
- a daily Ticket activity chart
Each bot's page shows the same four numbers and chart, counted across all of its servers.
There is no custom report builder or widget layout. Ticket exports are on the Tickets page; see Dashboard Ticket Management.
Limits and gotchas
- Every block, including the response-target warning, Customer mood, and AI answers, counts the same bots or server as the page. In a bot's or a server's stats, links to tickets and the team page keep that bot and server selected.
- Staff coverage, the reopen rate, Tickets by reason (the reason itself, and its Reopened column) and the business-hours first reply use information recorded from the update that added them. Older tickets still count everywhere else; until enough new data exists these show their "not enough data" states instead of zeros.
- Typical first reply only counts tickets that received a staff reply. Tickets still waiting show under Open now and Right now instead, so a slow team can show a good typical reply while the queue grows.
- Member wrote again after the last staff reply needs the time of the latest staff reply, which older tickets may not have; those are not counted until staff reply again.
- Staff numbers depend on staff roles being configured under each server's Staff → Staff roles. Replies from people without a staff role count as member messages.
- Top ticket types leaves out tickets with no type: channel tickets without a category, and thread tickets with neither a recorded button or option nor a parent channel name.
- Busiest hours needs 20 tickets opened in the selected range before it appears.
- Tickets whose channel was deleted still count as closed until they are purged.
Troubleshooting
| Symptom | Cause | Fix |
|---|---|---|
| The page says "No servers yet" | You own no bot and manage no server | Add a bot with Add a bot under Your bots, or ask an owner to give you dashboard access |
| The page says "Stats come with a paid plan" | No server you can see is on Basic or higher | Upgrade the bot owner's plan; see Plans |
| Everything is zero | No tickets in the selected range, or the bot was added recently | Pick 90 days, or wait for tickets; the all-time total under New tickets fills first |
| A staff member is missing from Your team | They have no staff role, or they handled no tickets in the range | Add their role under Staff → Staff roles; check the team page, which lists everyone with attributed tickets |
| Busiest hours is missing | Fewer than 20 tickets were opened in the selected range | Pick a longer range, or wait; it appears at 20 |
| The warning says tracking new tickets needs the Enterprise plan | SLA tracking was used on Enterprise and the plan changed | Existing tracked tickets stay visible; upgrade to track new ones |
| Response times look too good | Only answered tickets count toward Typical first reply | Check Right now for the unanswered backlog and Closed without a reply for tickets nobody answered |
| Staff coverage shows only tickets, with "Staff replies are recorded from this update on" | No staff replies are recorded yet in the selected range | Wait for staff to answer tickets after the update; the comparison appears once 20 tickets came in since replies started being recorded |
| Most tickets are under Reason not recorded | They were opened from a panel without a button or option label, or before reasons were stored | New tickets from labelled buttons and menu options get their own rows |
Numbers differ from /stats | /stats covers one server and its own period | Open Stats from inside that server and pick the same range |
Common questions
Where did Analytics go? It is now Stats in the sidebar, at the same address.
How is the typical first reply calculated? From ticket creation to the first message from a staff member other than the person who opened the ticket, over tickets opened in the selected range that received one. The big number is the median (half of those tickets were answered faster) and the line under it is the 90th percentile (9 in 10 were answered within it).
Responses slower than 7 days are treated as outliers and excluded. The team page uses the same median for each staff member, over the tickets where they replied first.
Can I see stats for one server only? Yes. Open the server (click its tile on the dashboard home), then click Stats in the sidebar. Show all servers under the title switches back to all of them.
Why is a staff member's ticket count higher than the tickets they closed? A ticket counts for everyone who claimed, answered, or closed it. Closed counts only the person who closed it.
How do I compare staff fairly? Open a staff member from the team page. Each number shows the Team median for the same bot, server, and period, and members with fewer than 10 tickets or 5 ratings are marked, because a few tickets can swing their numbers. Active days and Hours with replies say when someone replied, not how long they worked.
Can I export stats? Only the team table, with Export CSV on the team page. For ticket data, export from the Tickets page.
Why does busiest hours not show up? With fewer than 20 tickets the hourly pattern is noise, so the block waits until 20 tickets exist.
When is my team understaffed? Open More stats and read Staff coverage. Its first sentence names the hours where many tickets come in but few staff replies are sent ("Most understaffed: Saturday 6:00 PM to 10:00 PM"), and striped squares mark every such hour. Use Staff replies to see when your team is active.
What is the reopen rate on the Closed number? The share of closes in the selected range that were later reopened, counting every close (a ticket closed twice is two closes), like the team pages. It only counts tickets opened after reopen tracking was added and appears once 10 such closes exist; before that the line compares closes with new tickets.
Why did the Closed number change? Closed now counts the tickets closed in the range, whenever they were opened, the same as the chart. It used to count only tickets opened in the range that are closed now.
Do closed tickets from deleted channels still count? Yes, until they are purged from the Tickets page.
Where do I see AI token usage? On AI usage (under More tools in the sidebar of the dashboard home, or in the account menu), not on Stats.
Set up analytics dashboards, the short version
Join our Discord server for support
AI Ticket Reviews
On Pro and Enterprise, enable AI assistant → Atlas → Ticket reviews to review staff work after tickets close. This is independent of customer ratings and mood history.
The team page lists each staff member with their number of reviews, average score from 1 to 5 (with the change against the previous period under it), and how many reviews need attention; click a name for their staff page. A staff member's page shows their average and their own reviews. Each review is a row with the staff member (or the ticket number on a staff member's page), the closing date, its score, and a Needs attention tag when flagged. Open it to read the summary, a score and reason for each dimension with how many messages each is based on, tone changes, timing context, and any rude or dismissive replies, then click Open ticket to check the conversation. A rude reply or a dimension scored 1 or 2 flags the ticket even when its average is high. Unknown dimensions do not affect the average.
Owners see the team; dashboard staff see only their own reviews. The review period uses the ticket's closing time. Sampling means these numbers cover reviewed tickets, not all staff activity. Up to 5,000 staff reviews contribute to the period comparison and up to 100 details are shown, with flagged tickets first. A notice appears when the selection is limited; narrow the period or server before drawing conclusions. See Ticket Reviews for settings, evidence requirements and limits.
Estimated Handling Time
Stats → Your team and each staff member’s page show estimated handling time for tickets opened in the selected period. The estimate is recorded when a ticket closes and sums intervals of up to five minutes between that staff member’s consecutive replies on the same ticket. Longer gaps and single replies add no time. Reading and typing are not measured, and overlapping tickets can overlap in the estimate. This is separate from first reply time, time to close and hours with replies.
Not recorded means no ticket in the selection has a handling measurement for that staff member. Older unmeasured tickets do not contribute a zero. A measured ticket with only one reply contributes zero minutes. Open a ticket’s Member profile for its member’s history and per-ticket staff estimates.
Profiles also offer Filter members: exact matching on owner-defined fields, with retained ticket counts and average visible ratings for the matching members in that server. These figures use current profile values across all retained history, independently of the Stats period picker.
Was this page helpful?
Last updated on