Skip to main content

🔔 Notifications

Notification system settings are created to publish informational updates on bot activity to a community chat or other private channel used by teams or moderators.

Overview​

The Notifications feature allows administrators and moderation teams to stay informed about all bot activities in real-time. Whether you prefer private direct messages or a dedicated moderation channel, the notification system ensures your team never misses important events.

Configuration​

To access Notification settings:

  1. Use the /settings command in your chat
  2. Navigate to 🛡️ Moderation → 🔔 Notifications
  3. Use the Toggle Notifications option to turn the feature 🟢 ON or 🔴 OFF

Configuring Notification Settings​

Notifications Mode​

The bot offers two modes for delivering notifications:

Direct Message​

When selected, the Fren One bot sends private notifications directly to group administrators.

These updates include actions like:

  • User bans
  • User kicks
  • User mutes
  • And other moderation events
Admin DM Requirements

Admins must have started a conversation with the bot for Direct Message mode to work. Ensure all admins have messaged the bot at least once.

Channel​

This setting will allow you to add an external channel for the purpose of forwarding notifications from Fren One for centralized monitoring by multiple team members.

To set this up:

  1. Select Channel in the Notifications Mode menu
  2. The bot will prompt: "📝 Please forward me a message from the desired channel or type the channel ID here."
  3. Forward a message from the desired channel, or manually type the group or channel ID
Make sure Fren One is added to the desired notifications channel
Dedicated Moderation Channel

Create a private channel specifically for bot notifications. This keeps your moderation team informed without cluttering the main chat.

Grabbing channel id

You can grab the id of the channel you want to use for notifications after adding the Fren One bot to it, and typing in !id

Events​

Events lets you choose which activity of the bot will be tracked via notifications. You can enable or disable individual event types:

Admin Command​

Usage of admin commands such as !mute, !ban, or !kick.

Useful for:

  • Tracking moderator actions
  • Auditing command usage
  • Ensuring accountability

Blacklisted Name​

User joined with a name matching the blacklist.

Useful for:

  • Monitoring attempted joins by suspicious usernames
  • Tracking blacklist effectiveness
  • Identifying patterns in malicious accounts

Captcha Failure​

User failed the captcha verification.

Useful for:

  • Identifying bot accounts
  • Monitoring failed verification attempts
  • Adjusting captcha difficulty if needed

Filter Restriction​

User was restricted due to one of the configured filters.

Useful for:

  • Tracking filter effectiveness
  • Identifying false positives
  • Monitoring content violations

Impersonation Detection​

User joined with a name similar to a group admin.

Useful for:

  • Preventing scams targeting your community
  • Quick response to impersonation attempts
  • Protecting admin reputation

Lockdown Mode​

Triggered during the activation of lockdown mode.

Useful for:

  • Confirming lockdown activation
  • Coordinating team response during attacks
  • Tracking security events

Reported User​

User whose messages were reported by group members.

Useful for:

  • Monitoring community-flagged content
  • Responding to member concerns
  • Tracking report patterns

Sentiment Moderation​

User affected by sentiment moderation settings.

Useful for:

  • Monitoring negative interactions
  • Tracking toxic behavior patterns
  • Adjusting sentiment thresholds

Vote Ban​

User banned through community vote actions.

Useful for:

  • Tracking community moderation decisions
  • Monitoring vote ban effectiveness
  • Ensuring fair voting process

Warn Limit Reached​

User reached the configured warning limit.

Useful for:

  • Tracking repeat offenders
  • Timely response to escalated situations
  • Evaluating warning system effectiveness

Prohibited Trigger​

Message contained prohibited filter.

Useful for:

  • Monitoring trigger effectiveness
  • Identifying common violations
  • Adjusting trigger sensitivity

Raid Detection​

Detection of coordinated joins or spam (raid).

Useful for:

  • Immediate response to attacks
  • Coordinating defense measures
  • Tracking raid patterns

Flood Control​

Moderation triggered by excessive messaging in a short time.

Useful for:

  • Preventing spam attacks
  • Monitoring message rate violations
  • Identifying spammers

AI Spam​

Message flagged by the AI-based spam detection system.

Useful for:

  • Monitoring AI detection accuracy
  • Training and improving spam detection
  • Quick response to sophisticated spam

Smart Trigger​

Message flagged by the AI-based match of a message agaisnt pre-configured prompt.

Useful for:

  • Quick response to commonly asked questions
  • Removing recurring misinformation
  • Automated warnings to users sharing prohibited content

Best Practices​

Effective Notification Management
  • Enable all events initially to understand your community's patterns
  • Gradually disable low-priority events to reduce noise
  • Use Channel Mode for team coordination
  • Create separate channels for different event types (e.g., high-priority vs. low-priority)
  • Review notifications regularly to adjust settings
  • Set up notification channels before major community events
  • Test notification delivery before relying on it
  • Document your notification preferences for team reference
Avoiding Notification Fatigue
  • Don't enable every event if your community is very active
  • Prioritize critical events (raids, impersonation, lockdown)
  • Consider muting low-priority events during peak hours
  • Use filters and triggers to reduce false positives
  • Regularly audit which events are actually useful
  • Balance between staying informed and being overwhelmed
  • Consider different notification channels for different severity levels

Common Configuration Examples​

Small Community Setup​

Scenario: Small team with close coordination.

Configuration:

  • Mode: Direct Message
  • Enabled Events: All events
  • Reason: Small volume, full visibility needed

Large Community Setup​

Scenario: Multiple moderators, high activity.

Configuration:

  • Mode: Channel
  • Enabled Events:
    • High priority: Raid Detection, Lockdown Mode, Impersonation Detection
    • Medium priority: Vote Ban, Warn Limit Reached, Reported User
  • Disabled Events: Filter Restriction, Flood Control (too frequent)

Security-Focused Setup​

Scenario: Community targeted by scammers.

Configuration:

  • Mode: Channel
  • Enabled Events:
    • Blacklisted Name
    • Captcha Failure
    • Impersonation Detection
    • Raid Detection
    • AI Spam
    • Smart Triggers
  • Purpose: Focus on security threats only

Audit Trail Setup​

Scenario: Need comprehensive moderation logs.

Configuration:

  • Mode: Channel (dedicated audit log channel)
  • Enabled Events: All events
  • Purpose: Complete record for compliance/review

Notification Formats​

Each notification typically includes:

  • Timestamp: When the event occurred
  • Event Type: What kind of action or detection
  • User Information: Who was affected or took action
  • Details: Specific information about the event
  • Action Taken: What the bot did in response
Notification Content

Notifications are designed to be informative yet concise, providing essential information for quick decision-making.

Troubleshooting​

Not receiving notifications?

  • Verify Notifications are toggled 🟢 ON
  • Check that the specific event type is enabled
  • For DM mode: Ensure admins have messaged the bot
  • For Channel mode: Verify bot is in the channel with admin permissions
  • Test with a known event (e.g., issue a test warn)

Too many notifications?

  • Disable low-priority event types
  • Switch from DM to Channel mode to consolidate
  • Adjust filter and trigger settings to reduce false positives
  • Consider creating event priority tiers
  • Review which events are actually actionable

Notifications going to wrong channel?

  • Reconfigure the Channel setting
  • Verify you forwarded from the correct channel
  • Check the channel ID is accurate
  • Ensure bot has access to the intended channel

Missing notifications for specific events?

  • Verify the event type is enabled in Events settings
  • Check if the event is actually occurring (test it)
  • Ensure the feature triggering the event is enabled
  • Review bot permissions for that specific action

Notification delays?

  • Check Telegram server status
  • Verify bot's connection status
  • For Channel mode: Check channel message rate limits
  • Consider bot load during peak times

Advanced Setup​

Multi-Tier Notification System​

Setup multiple channels for different priorities:

Critical Channel:

  • Raid Detection
  • Lockdown Mode
  • Impersonation Detection
  • Immediate action required

Moderation Channel:

  • Vote Ban
  • Warn Limit Reached
  • Reported User
  • Review and action within hours

Audit Channel:

  • All events
  • Historical record
  • Long-term analysis

Integration with External Tools​

Use notifications to:

  • Feed into logging systems
  • Trigger external alerts
  • Generate moderation reports
  • Train AI/ML models
  • Create analytics dashboards

Team Coordination​

Best practices for teams:

  • Designate who responds to different event types
  • Create response protocols for each notification type
  • Use notification channel for team communication
  • Set up rotating on-call schedules
  • Document common responses to standard notifications
tip

Remember to give the Fren One bot admin privileges and ensure it has access to your notification channel. Test notifications after setup to ensure everything is working correctly.