A Discord ticket rating is a 1-5 score the member gives after their ticket closes, so staff (and you) have an actual number for support quality instead of a gut feeling. Noxyr can DM the ticket opener a rating request the moment their ticket closes, log every score to a channel with the reviewer's name and the ticket it was about, and roll every rating into an average shown on the ticket analytics dashboard. This is Discord's version of a post-support CSAT survey, and it's off by default - here's what turning it on actually does.
How the rating prompt works
When a ticket closes with ratings enabled, the bot DMs the person who opened it: an embed asking "How was the support in [server name]?" with five buttons, 1/5 through 5/5. Clicking one records the score against that ticket, and the member gets a short "Thanks, rating saved" confirmation. A ticket can only be rated once - clicking again or trying to rate a ticket that's already been scored does nothing.
Because it's a DM, a member who has DMs closed from the server simply doesn't get the prompt - there's no in-channel fallback, since the ticket channel itself is already gone by the time the rating goes out.
Turning it on
- 1. On the dashboard's Tickets page, turn on Rating after close.
- 2. Pick a rating channel - every score logs there as an embed with the score, a simple bar (like
[###--]for 3/5), the ticket name, the panel it came from, and who rated it. - 3. Via Discord instead:
/ticketsetup rating_enabled:true rating_channel:#ratings.
Skip the rating channel and ratings still get recorded and counted in the average - you just won't see each one logged individually as it comes in.
Reading the average
The ticket analytics page on the dashboard shows an all-time average rating out of 5 as one of its headline cards, next to tickets created, closed and claimed. It reads "No ratings yet" until the first one comes in, so a brand-new server or one that just turned ratings on won't show a misleadingly low number from an empty sample. See our ticket analytics guide for what else that page tracks, including staff-level response times.
There's no per-panel or per-staff-member rating breakdown in the current version - the average is server-wide. If you need to know whether one staff member's tickets get rated worse than another's, the rating channel log is the place to cross-reference manually, since each entry names the reviewer.
Why some servers leave it off
Rating requests are one more DM a member has to act on after they've already gotten what they wanted, and low response rates are normal for any post-support survey, Discord or otherwise - most members who are satisfied just leave. That's fine; a rating system doesn't need every ticket rated to be useful, it needs enough of a sample to notice a trend. Turn it on if you have staff you want accountability data for, or a store where buyer trust matters. Skip it for a small personal server where "did that go okay" is obvious without a number.
If low-effort feedback isn't what you want and you'd rather collect a written review with a comment, that's a separate feature - see the reviews setup, which posts public reviews with a comment field rather than a private 1-5 tap.
What a low average actually tells you
A dropping average is a symptom, not a diagnosis. Before assuming staff quality is the problem, check whether ratings dropped right after a policy change (a longer wait time, a stricter refund rule), whether one specific panel or product line is dragging the number down, and whether the sample is still small enough that two or three bad scores are swinging it. The rating log with reviewer names next to scores is the fastest way to spot a pattern instead of reacting to a single number.
Getting more members to actually rate
Most rating prompts of any kind get ignored - that's normal, not a sign the feature is broken. A couple of things nudge the response rate up without being annoying: keep the confirmation message ("Thanks, rating saved") as the only follow-up, since chasing someone for a rating after they've already gotten support tends to feel like a survey popup rather than genuine curiosity, and make sure the close reason on the ticket makes clear the conversation is actually finished - a member who's confused about whether their issue is resolved is less likely to bother clicking a button.
Common questions
Can staff rate their own tickets? The prompt only goes to the ticket opener, so staff can't submit a rating for a ticket they worked unless they were also the one who opened it.
Does the member need to be in the server to rate? They need to still share a server with the bot and have DMs open to it - if they've already left, the DM will fail to send.
Can I change a rating after it's submitted? No, there's no edit or re-rate flow once a score is recorded.
Is the rating system free? Yes, it's included in Noxyr's ticket module at no cost.
Does turning ratings on notify staff, not just the analytics page? Only if you set a rating channel - without one, scores are still counted but not posted anywhere visible.
Add Noxyr and turn on ratings from the Tickets page, or read the full setup in the Tickets docs.