Product community cleanup that avoids support friction.
Keep customer and user communities active with transparent inactivity tracking. No message access. No privileged intents.
"Please do not do anything we cannot explain."
What you’re optimizing for
- A professional, low-noise environment for your customers.
- Accurate retention metrics by filtering out ghosts.
Common pain points
- Public "shaming" of inactive users looks unprofessional.
- Need to avoid accidentally kicking enterprise clients.
Standard Setup Preset
Select SaaS / Product Community during /start.
Core Behavior
- Operating Mode
- Ghost (Staff-only outputs)
- Timeline
-
Warning 30 days (~1mo)Mark Inactive 60 days (~2mo)Kick Eligible 120 days (~4mo)
- Auto-kick
- Off
Signals & Actions
- Activity Signals (ON)
- Messages, reactions, interactions, typing, threads, rsvps.
- Engagement
- Polls OFF, CTA OFF.
-
@active user (14d)
@power user (45d)
(Rewards are announced in staff channels only)
Suggested Channels & Roles
Why CleanerBot fits this use case
"Ghost Mode" means the bot is invisible to normal users. It silently tracks activity and reports to staff channels, allowing you to manage your community without creating public noise or anxiety.
Keep customer spaces tidy without friction
Product communities need clean member lists and calm policies. People come back when they need help, so the defaults are conservative and review-led. This CleanerBot preset is tuned for SaaS and product communities that want community cleanup which avoids support friction.
The SaaS preset reflects a support reality: long-tail users may be quiet for weeks, then return with a serious issue. A slower timeline prevents unnecessary churn while still helping moderators see who is truly inactive.
This matches the target group analysis for business and tech communities: the need is real, but the tolerance for drama is low. Clear thresholds plus manual review keeps decisions predictable and defensible.
Support-friendly pattern
- Exempt customers on paid plans.
- Review flagged accounts during support triage.
- Only tighten timelines after observing demand.
What to communicate
- State that inactivity labels are reversible.
- Provide one clear recovery action.
- Document your review cadence internally.
Related reading: auto-kick guardrails, inactivity policy template.
Common Questions
Will my customers see the bot?
No. In Ghost Mode, CleanerBot never posts in public channels and never sends DMs to users. It only posts in the admin channels you designate.
Can I exempt paying clients?
Yes. Whitelist your "Customer" or "Enterprise" roles, and they will be completely ignored by the inactivity system.
Is voice chat tracked?
By default, no (to save resources), but you can enable it if your community uses voice for support calls or meetings.
Will this affect support tickets or help channels?
Not if you keep the process review-led. Use the queue to confirm context before removals, and document the policy in a short staff note so decisions stay consistent.
How should we treat trial users versus paying customers?
Exempt paying customer roles and keep stricter timelines on trial or marketing roles. This keeps SaaS and product communities tidy without creating accidental churn for real customers.
Can we run this quietly for a while before announcing it?
Yes. Start in Ghost Mode to validate the review list with your support team, then announce once you are confident the policy matches how your product community actually behaves.
Invite CleanerBot, run /start, and publish a short, transparent inactivity policy in your rules channel with the Inactivity Policy Template.
Moving away from Discord Prune? Read the Discord Prune vs CleanerBot Comparison.