Notification Types
Security alerts
Instant alerts when the anti-raid shield trips or a burst of false positives needs your attention.
Appeals & disputes
A member appealed a ban or disputed a decision — you get pinged to review it, right in your DM.
Moderation events
From the bot's first actions on a newcomer to every ban, warn and mute — logged to your admin channel as an audit trail.
Payouts & model updates
Monetization payouts processed or rejected, protection status changes, and your personal ML model becoming ready.
Delivery Options
Why Notifications Matter
- Early warning - Catch spam attacks and security threats before they escalate.
- Stay informed - Know what's happening in your community without constant monitoring.
- Fix mistakes fast - Appeals and false-positive warnings reach you instantly, so wrong calls get reversed in minutes.
How alerts are raised and delivered
Notifications turn events already happening inside Telm into alerts pushed to you, so you learn about something without watching the group. The triggering events fall into a few kinds: security alerts when the anti-raid shield trips or a burst of confirmed false positives needs your attention, appeals and disputes waiting for review, moderation events — from the bot's first actions on a newcomer to every ban, warn and mute in your admin log channel — and account events like a processed payout or a personal ML model becoming ready. Each alert goes out over the channel that suits it — a Telegram DM, your admin log channel, mobile push, webhook or API, or the dashboard — and burst events like raids arrive as one aggregate alert, not a wall of pings.
The practical gain is early warning: catching a raid or a wave of wrong verdicts while it is starting lets you step in before it escalates, and you stay informed without constant manual monitoring. Routing matters — routine moderation events can stay in the admin log channel while a security alert hits your DM immediately — so the important signals are not buried. The honest caveat is that a notification tells you something changed, not always what to do: a raid alert is the prompt to look, and the moderation log and analytics are where you confirm what actually happened.
Frequently asked questions
Will I get flooded with alerts during a spam attack?
No — burst events are aggregated at the source: a raid shows up as one anti-raid alert with the group and time window, and a wave of confirmed false positives arrives as a single burst warning rather than one ping per message. You also choose which event types go to your admin log channel and which reach your DM or phone.
Which events can actually trigger a notification?
Appeals waiting for review, disputed decisions, anti-raid shield activations, false-positive burst warnings, protection status changes (like the gentle-start window ending), the bot's moderation actions, monetization payouts, and your personal ML model becoming ready. Every ban, warn and mute is also logged to your admin log channel for the audit trail.
Can alerts go somewhere other than Telegram?
Yes. Delivery channels include Telegram DM, a dedicated admin log channel, dashboard alerts, mobile push in the Telm app, and webhooks/API. The webhook and API options are what let you route events into your own tooling — a monitoring system or an on-call setup — so notifications are not locked to reading them by hand inside Telegram.
A raid alert fired — does that mean my group is under attack?
It means the anti-raid shield saw a join surge and stepped in — which can be an attack or, occasionally, a genuine influx after a viral post or an ad campaign. Treat the alert as a prompt to look rather than a verdict: the moderation log shows exactly what the shield did while it was active, and analytics shows whether the surge was real engagement.
Related features
Explore more ways Telm can help your community