๐ 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โ
Notifications tell your admins about the agent's moderation activity, by direct message or in a moderation channel.
Configurationโ
In the webappโ
Open your workspace, select the Telegram group under Channels in the sidebar, then select Moderation, then the Notifications tab. Changes save with the Save bar at the bottom of the page.
In Telegram (bot menu)โ
To access Notification settings:
- Use the
/settingscommand in your chat - Navigate to ๐ก๏ธ Moderation โ ๐ Notifications
- 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
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:
- Select Channel in the Notifications Mode menu
- The bot will prompt: "๐ Please forward me a message from the desired channel or type the channel ID here."
- Forward a message from the desired channel, or manually type the group or channel ID
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 |
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