🔔 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 🟢 Enabled or 🔴 Disabled

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 as an admin 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.

Events

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

Event	Description
Admin Command	Usage of admin commands such as !mute, !ban, or !kick
Agent Command	Triggered when the AI agent executes a moderation action
Blacklisted Name	User joined with a name matching the blacklist
Captcha Timeout	Triggered when a user fails the captcha verification
Filter Restriction	User was restricted due to one of the configured filters
Impersonation Detection	Triggered when a user is detected impersonating a group admin
Lockdown Mode	Triggered during the activation of lockdown mode
Reported User	User whose messages were reported by group members
Sentiment Moderation	User affected by sentiment moderation settings
Vote Ban	User banned through community vote actions
Warn Limit Reached	User reached the configured warning limit
Prohibited Trigger	Message contained prohibited filter
Raid Detection	Detection of coordinated joins or spam (raid)
Flood Control	Triggered when flood activity is detected
AI Spam	Message flagged by the AI-based spam detection system
Smart Trigger	Message flagged by the AI-based match against a pre-configured prompt

👤 User Updates

Configure which profile changes are included in notifications:

Event	Description
Username Update	Triggered when a user updates their username (e.g., @username1 → @username2)
Name Update	Triggered when a user updates their first or last name
Profile Photo Update	Triggered when a user updates their profile photo
Premium Upgrade	Triggered when a user upgrades to Telegram Premium

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
• Review notifications regularly to adjust settings
• Test notification delivery

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

Troubleshooting

Not receiving notifications?

• Verify Notifications are toggled 🟢 Enabled
• 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
• 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