Volunteer coordination that stays structured and kind.
Keep NGOs, volunteer groups, and event teams active with transparent inactivity tracking. No message access. No privileged intents.
"Please never touch Staff. Never ever."
What you’re optimizing for
- Keep the community active with clear expectations.
- Ensure volunteers are actually available to help.
Common pain points
- Inactive members accumulate and weaken participation metrics.
- Sensitive "Staff" or "Board" roles getting accidentally purged.
Standard Setup Preset
Select NGO / Volunteer / Events during /start.
Core Behavior
- Operating Mode
- Ghost (Staff-only outputs by default)
- Timeline
-
Warning 30 days (~4w)Mark Inactive 90 days (~3mo)Kick Eligible 180 days (~6mo)
- Auto-kick
- Off
Signals & Actions
- Activity Signals (ON)
- Messages, reactions, voice, interactions, typing, threads, RSVPs.
- Engagement
- Streaks ON, Rewards ON.
-
@active volunteer (14d streak)
@core volunteer (60d streak)
Suggested Channels & Roles
Why CleanerBot fits this use case
Our focus is fairness: predictable thresholds, long grace windows, and manual review queues before any removal happens. Perfect for sensitive environments where you can't afford to accidentally kick a board member.
Coordinate volunteers with empathy and clarity
Volunteer communities need structure, but they also need grace. The best policies make expectations explicit while leaving room for real life. CleanerBot is tuned here for NGOs and volunteer teams that want volunteer coordination to stay structured and kind.
The NGO preset defaults aim for steady coordination rather than aggressive cleanup. It gives enough time for volunteer cycles, event gaps, and seasonal pauses while still creating a clear queue for follow-up.
The target group analysis emphasizes privacy and fairness for civic groups. A review-first workflow plus clear, public timelines helps teams enforce standards without feeling punitive.
Volunteer-safe pattern
- Review flags after major events.
- Use labels to route outreach, not blame.
- Exempt coordinators and core organizers.
Clarity beats strictness
- Pin the policy in staff and public channels.
- Keep recovery actions obvious.
- Track changes in a short staff note.
Related reading: inactivity policy template, auto-kick guardrails.
Common Questions
Does CleanerBot read messages?
No. We don’t store or process message content. We use activity signals only and do not require privileged intents.
Do we have to use presets?
No. Presets are optional. Use /start to pick Standard or Ghost, or configure everything manually.
Is this a “purge bot”?
No. We manage inactivity over time with transparent scoring, warnings, and guardrails — not bulk deletions.
How do we handle seasonal pauses or event breaks?
Pause enforcement during known quiet periods, then resume once normal coordination returns. This keeps volunteer coordination structured and kind when real-life cycles change availability.
Should coordinators and team leads be exempt?
Usually yes. Exempt coordinator roles so operational ownership is never flagged by automation, then use the review queue to focus on volunteers whose availability is unclear.
Invite CleanerBot, run /start, and publish a short, transparent inactivity policy in your rules channel.