Best practice guide
Cleaning up inactive Discord members should not feel like a surprise punishment. A healthy process explains what counts as activity, when warnings happen, what an inactive role means, and when staff may review removal.
If you are unsure how members will react, start in Ghost Mode.
A large member count can hide a small active community. But removing people without warning can create distrust.
Use signals that match your community: messages, reactions, voice or stage activity, threads, slash commands, buttons, scheduled events or RSVPs, polls and quizzes, and optional lightweight signals such as typing or CTA buttons.
Use reports, staff-only review, or Ghost Mode before removing anyone. Observation helps staff separate quiet supporters from abandoned accounts and spot permission or coverage gaps.
A good warning says which threshold was reached, what the member can do next, whether activity can lower or reset the score, and who to contact if something looks wrong.
For many servers, the safest cleanup path is warning, inactive role, staff review, then optional removal. An inactive role is reversible and gives staff more context.
Check moderators, long-time contributors, paid supporters, volunteers between events, students with absence windows, exempt roles, recent returns, and permission gaps.
Include activity signals, warning threshold, inactive role threshold, review threshold, auto-kick status, how members can check their score, and a privacy note.
/start.Starting with bulk removals: start with reports, warnings, and inactive roles.
Treating lurkers as bad members: define what showing up means for your server.
Using XP as cleanup proof: XP shows volume; Decay Score shows whether activity is fading.
Enabling auto-kick too early: use staff review first. Auto-kick is optional and should be guarded.
Not explaining the policy: publish a short, member-friendly explanation before visible action.
Sometimes, but not first. Warnings, inactive roles, and staff review are usually safer.
For most role-heavy communities, yes. It is reversible and gives staff more context before removal.
Yes. CleanerBot can work from configured activity signals without reading or storing message content.
Point them to your policy, show the thresholds, and explain that activity can lower or reset the score. If a threshold feels too strict, adjust it.
Start with visibility, warnings, inactive roles, and staff review.