Skip to main content

System Alerts

Stay informed of critical platform issues and moderation needs through automated alerts.

Alert Types​

Moderation Alerts​

High Report Volume

  • Triggers when content receives multiple reports
  • Indicates potential guideline violations
  • Requires urgent review

Report Queue Backup

  • Alerts when pending reports exceed threshold
  • Default: 50+ pending reports
  • Action: Prioritize report review

Repeat Offender

  • Flags users with multiple content violations
  • Tracks hidden content by user
  • May require account action

Content Alerts​

Spam Detection

  • Multiple similar submissions from same user
  • Rapid content posting
  • Promotional/duplicate content patterns

Viral Content Issues

  • Popular content receiving high report rate
  • Trending content with guideline concerns
  • Wide visibility requiring quick action

User Alerts​

Account Abuse

  • Multiple accounts from same device/IP
  • Ban evasion attempts
  • Coordinated harassment patterns

User Complaints

  • Direct user complaints via support
  • Pattern of user-to-user conflicts
  • Serious violation reports

System Alerts​

Performance Issues

  • API response time degradation
  • High error rates
  • Database performance concerns

Security Concerns

  • Unusual authentication patterns
  • Potential security vulnerabilities
  • Suspicious admin access attempts

Alert Priority Levels​

Critical (Immediate Action)​

  • Security breaches or attempts
  • Severe guideline violations (hate speech, threats)
  • System outages affecting users
  • Legal/safety concerns

Response Time: < 1 hour

High (Same Day)​

  • Multiple reports on same content
  • Repeat offender patterns
  • Report queue backup
  • User safety concerns

Response Time: < 4 hours

Medium (24-48 Hours)​

  • Standard content reports
  • Performance degradation
  • Quality issues
  • Community concerns

Response Time: < 24 hours

Low (Monitor)​

  • Trends to watch
  • Minor guideline issues
  • Feature requests
  • Informational notices

Response Time: As needed

Alert Configuration​

Setting Thresholds​

Configure alert triggers based on platform size:

MetricSmall PlatformMedium PlatformLarge Platform
Pending Reports> 20> 50> 100
Reports on Single Item> 3> 5> 10
User Violations> 2> 3> 5
Error Rate> 1%> 0.5%> 0.1%

Adjust based on:

  • Platform growth
  • Admin team capacity
  • Historical patterns
  • Community standards

Notification Channels​

Alerts can be delivered via:

  • Admin dashboard (primary)
  • Email notifications
  • Slack/Discord integration
  • SMS for critical alerts
  • Push notifications

Responding to Alerts​

Moderation Alerts​

Immediate Steps:

  1. Review the reported content
  2. Check reporter history and credibility
  3. Evaluate against community guidelines
  4. Take appropriate action (hide, warn, dismiss)
  5. Document decision and reasoning

For Repeat Offenders:

  1. Review user's complete history
  2. Check previous warnings
  3. Assess pattern severity
  4. Consider account suspension
  5. Document all actions

Content Alerts​

Viral Content Review:

  1. Prioritize high-visibility content
  2. Review in full context
  3. Consider community impact
  4. Act quickly to prevent spread
  5. Communicate with stakeholders

Spam Detection:

  1. Verify spam classification
  2. Check user intent
  3. Hide spam content
  4. Warn or suspend user
  5. Update spam detection rules

User Alerts​

Account Abuse:

  1. Investigate account connections
  2. Review activity patterns
  3. Check for ban evasion
  4. Take preventive action
  5. Monitor for recurrence

User Complaints:

  1. Review complaint details
  2. Investigate all parties
  3. Check content/interaction history
  4. Mediate if appropriate
  5. Take enforcement action

System Alerts​

Performance Issues:

  1. Check system monitoring tools
  2. Identify bottlenecks
  3. Implement quick fixes
  4. Escalate to engineering
  5. Monitor resolution

Security Concerns:

  1. Assess threat severity
  2. Implement immediate protections
  3. Investigate thoroughly
  4. Document incident
  5. Update security measures

Alert Management Best Practices​

Daily Workflow​

  1. Review overnight alerts first thing
  2. Prioritize by severity level
  3. Action critical alerts immediately
  4. Delegate medium/low priority items
  5. Document all actions taken

Team Coordination​

  • Assign primary responders by shift
  • Establish escalation procedures
  • Share critical alert information
  • Hold regular alert review meetings
  • Train team on response protocols

Documentation​

  • Record all alert responses
  • Note actions taken and outcomes
  • Track resolution times
  • Identify recurring issues
  • Review patterns monthly

Continuous Improvement​

  • Analyze false positive rates
  • Refine alert thresholds
  • Update response procedures
  • Train on new alert types
  • Solicit team feedback

Alert Implementation​

Current Status​

The BookWish platform currently implements basic alerting through:

  • Database record status (Report.status)
  • Moderation status flags (Line.moderationStatus, Review.moderationStatus)
  • Manual admin dashboard monitoring

Future Enhancements​

Planned alert system improvements:

  • Automated email/Slack notifications
  • Configurable alert rules
  • Alert dashboard with filtering
  • Historical alert analytics
  • Machine learning for pattern detection

Manual Monitoring​

Until automated alerts are implemented, monitor:

-- Pending reports count
SELECT COUNT(*) FROM reports WHERE status = 'pending';

-- Reports on single content
SELECT reported_line_id, COUNT(*) as report_count
FROM reports
WHERE reported_line_id IS NOT NULL
GROUP BY reported_line_id
HAVING COUNT(*) >= 3;

-- User with multiple violations
SELECT u.id, u.username,
  COUNT(DISTINCT r.id) as reports
FROM users u
JOIN reports r ON r.reported_user_id = u.id
WHERE r.status = 'action_taken'
GROUP BY u.id, u.username
HAVING COUNT(DISTINCT r.id) >= 2;

Alert Response Templates​

Content Hidden Response​

Report ID: {report_id}
Action: Content hidden
Reason: {violation_type}
Content: {content_preview}
User: {username}
Notes: {additional_context}
Reviewer: {admin_username}
Date: {timestamp}

False Positive​

Report ID: {report_id}
Action: Dismissed
Reason: Does not violate guidelines
Content: {content_preview}
Notes: {explanation}
Reviewer: {admin_username}
Date: {timestamp}

Warning Issued​

Report ID: {report_id}
Action: Warning issued to user
Violation: {violation_type}
User: {username}
Previous Warnings: {count}
Notes: {warning_text}
Reviewer: {admin_username}
Date: {timestamp}

Next Steps​