At-Risk Detection
💎 PremiumMLI automatically flags members whose engagement drops below healthy thresholds. At-risk detection helps you intervene before valuable members leave your server.
How At-Risk Detection Works
On every compute cycle, MLI evaluates each tracked member's health score against configurable thresholds. When a member's score drops into the at-risk range, they're flagged and optionally trigger alerts.
Watch
Health score has dropped into the moderate range and is trending downward. The member isn't at-risk yet but may need attention soon.
At-Risk
Health score has fallen below the at-risk threshold. The member has significantly reduced their engagement and may be disengaging from the community.
Critical
Health score is near zero. The member has been almost entirely inactive for an extended period and is likely to leave the server.
Risk Alerts
When Risk Alerts are enabled in the dashboard, MLI sends notifications to a configured channel when members cross risk thresholds. This lets moderators take proactive action.
Alert Channel
Configure which channel receives at-risk notifications. Typically a staff-only or moderation channel.
Alert Threshold
Set the health score below which alerts are triggered. Default triggers at the at-risk level, but you can make it more or less sensitive.
Alert Cooldown
Prevents duplicate alerts for the same member. Once alerted, a member won't trigger another alert until the cooldown expires.
Privacy
Viewing At-Risk Members
/lifecycle at-risk [limit]View members currently flagged as at-risk, sorted by severity. Optionally limit the number of results shown.
/lifecycle member <user>Check a specific member's risk level, health trend, and what factors are contributing to their decline.
Early Intervention
At-Risk Commands
| Command | Description |
|---|---|
/lifecycle at-risk [limit] | View at-risk members sorted by severity |
/lifecycle member <user> | Check individual risk level and factors |
/mli status | View total active risks on the status card |