To track Discord staff activity fairly, measure the work your staff do for members, not how much they talk: tickets claimed and closed, how long tickets wait before someone picks them up, and applications reviewed. Agree on an inactivity threshold everyone knows about, give staff a way to take leave, and start new staff on a trial with clear goals. This guide explains what to measure and why, then shows how to set it up with Staff Hub in Better Tickets.
Why staff tracking goes wrong
Most servers start tracking staff after something goes wrong: a ticket sits unanswered for a day, or a moderator quietly stopped showing up weeks ago. The usual fixes cause new problems:
- Counting messages. It rewards whoever chats most, not whoever helps. Staff learn to post more, not to answer tickets.
- Spreadsheets. Someone has to fill them in, and they're out of date by the end of the week.
- Surprise removals. Removing someone for being "inactive" without a rule they knew about feels unfair, even when the decision is right.
- No record of leave. A moderator who said they'd be away for exams gets flagged as inactive, and the team loses trust in the system.
What to measure
For a support team, the useful numbers come from the work itself:
| Measure | What it tells you |
|---|---|
| Tickets claimed | Who is picking up new tickets |
| Tickets closed | Who is seeing tickets through to the end |
| Median time to claim | How long members wait before someone takes their ticket |
| Applications reviewed | Who is keeping up with hiring decisions |
| Days since last activity | Who has gone quiet |
Median time to claim is more honest than the average, because one ticket left overnight doesn't drown out a week of quick responses. Look at trends over a week or a month rather than single days, and compare each person with the team, not with an ideal.
Handle inactivity with a rule everyone knows
Pick a threshold, such as five days with no claims, closes or reviews, and post it in your staff channel. When someone crosses it, check in with them first. Most of the time there's a reason: exams, work, a holiday they forgot to mention. Removing staff should come after a conversation, not straight from an alert.
Give staff a simple way to take leave, with a start and end date, so they don't get flagged while they're away. When they come back early, ending the leave should be just as easy.
Start new staff on a trial
A trial gives new staff a clear target and gives you a fair basis for promoting them. Keep the goals small and measurable:
- Claim a set number of tickets, for example 25 in two weeks.
- Keep their median time to claim under a target, for example 15 minutes.
- No strikes during the trial.
At the end, promote them, extend the trial if they were close, or end it with a short explanation.
Use strikes sparingly, and let them expire
Strikes work when they're rare, written down and temporary. Record the reason each time, let strikes expire after a set period such as 30 days, and decide in advance what happens at the limit. Keep private notes separate from strikes: a note like "great with new members, slower on report tickets" is useful context that shouldn't count against anyone.
Set up staff tracking in Better Tickets
Staff Hub builds all of the above from the tickets and applications Better Tickets already handles, so there's nothing for your staff to log. It's included with Plus and Max.
Give your staff their roles
Anyone with a staff role on a ticket panel, a reviewer role on an application form, or a rank role counts as staff. If your team already handles tickets, they're already listed.
Open Staff in the dashboard
In the dashboard, open Staff → Team overview to see each member's claims, closes, time to claim, reviews and status for the last 7, 30 or 60 days.
Set your alerts
In Staff → Setup → Alerts, pick a staff channel, how many days count as quiet, and how long a ticket can wait unclaimed before the bot pings that panel's staff.
Add ranks and trials
In Ranks, list your ranks from lowest to highest, each with up to five roles, for example a shared Staff role plus Helper, Mod or Admin. Give your first rank trial days and goals. Promoting someone swaps their rank roles for you.
Turn on the weekly report
In Weekly report, choose a channel, day and time. Each week the bot posts the team's totals and every active member's numbers.
Tell your staff about leave
Staff run /staff leave to ask for time off and /staff back to return
early. Approve requests on the Team overview.
Every setting is explained in the Staff Hub docs.
Keep it fair
Share the rules with your staff before you start: what's measured, the quiet threshold, how leave works and what strikes are for. Staff who know how they're judged tend to welcome the numbers, because the numbers show the work they've been doing all along.
Frequently asked questions
How do I track staff activity on Discord?
Measure the work staff actually do for your server, not how much they chat. For a support team that means tickets claimed and closed, how long tickets wait before someone claims them, and applications reviewed. A ticket bot already records all of this; Better Tickets' Staff Hub turns it into a per-member overview with a weekly report.
Is counting staff messages a good way to measure activity?
Not on its own. Message counts reward chatting, not helping, and they're easy to inflate. Use them as context at most, and judge staff on the tickets and applications they handle.
How long should staff be inactive before you act?
Pick a clear threshold, such as five or seven days with no tickets or reviews, tell your team what it is, and skip anyone on approved leave. An automatic alert is a prompt to check in, not a reason to remove someone.
Should new staff start on a trial?
Yes. A trial of one or two weeks with simple goals, such as a number of tickets claimed and a target time to claim, gives new staff something concrete to aim for and gives you a fair basis for promoting them.
How do I handle staff leave on Discord?
Let staff tell you before they go, with a start and end date, so inactivity rules don't flag them. In Better Tickets they run /staff leave, an admin approves it on the dashboard, and /staff back ends it early.
Do I need a separate staff management bot?
Not if your staff's work already runs through your ticket bot. Better Tickets' Staff Hub builds the staff overview from the tickets and applications it already handles, so there's nothing extra to log and no second bot to set up.