Ops alerts — Telegram & the admin bell

High-signal operational events fan out to the team two ways, so nothing slips by whether or not anyone's watching a chat.

Telegram team alerts

Real-time alerts to a Telegram chat. It's off until configured — set TELEGRAM_BOT_TOKEN and TELEGRAM_ALERT_CHAT_ID. Then:

• TELEGRAM_ALERT_EVENTS chooses which events fire (a comma-separated list; it fully replaces the default).
• TELEGRAM_TOPIC_<NAME> optionally routes an event's topic (growth / payments / infra / trust / security) to a specific thread in a Telegram supergroup.

Verify it from Admin → Operations → Telegram ops alerts:

• Run health check — shows whether it's configured and which events are live (no secret leaves the server).
• Send test alert — a real round-trip; if it lands in your chat, you're wired.

The admin bell (in-app)

The same high-signal events also drop a system alert into every active admin's notification bell — so ops awareness doesn't depend on Telegram. It's bell-only by default; an admin who finds it noisy can mute the stream from their notification settings.

What fires

Both streams share one event list — currently:

• New signups — a teacher / parent / student joined.
• Top-up flagged / failed — a payment was refused for review, or failed.
• New safety flag — content or a user was reported.
• Grade rollover applied — the annual advance ran (with the counts).

Common issues

• No Telegram alerts. It's unconfigured — run the health check; set the two env vars (and TELEGRAM_ALERT_EVENTS to opt events in).
• 400: group chat was upgraded to a supergroup. Telegram migrated the group — update TELEGRAM_ALERT_CHAT_ID to the new -100… id.
• The bell stream is too noisy. Mute the system alerts kind in your own notification settings — it doesn't affect other admins.