Telegram Manager
Send the right operational event to the right chat.
Create multiple Telegram Agents with independent functions, destinations and subscriptions—then let each person choose which eligible events should reach them.
Function-scoped routing
One bot is not forced to do everything.
Each Telegram Agent owns its name, function, Bot token, Chat ID, enabled state and event subscriptions. Multiple Agents can deliver different information without sharing routing state.
Task execution
Notify an assigned engineer when work is ready, started or completed, with direct operational context.
Operations
Route Equipment, Connectivity, Power, Inventory and support events to the responsible team.
Change Log
Publish each registered release once per subscribed Agent, even across service restarts.
Event delivery
From a controlled change to a traceable message.
Telegram is a notification channel, not an authority to silently mutate Equipment or bypass permissions.
Event
Task, security, support or product change.
Scope
Client, user, Agent and function rules.
Deduplicate
Stable event identity prevents repeat noise.
Deliver
Protected server-side Telegram API call.
Record
Delivery result and operational history.
Personal notification control
Email and Telegram preferences belong to the person.
Each Client user can select eligible event categories without receiving provider credentials or changing another person’s preferences.
Sign-in activitySuccessful access and security context
Email / TelegramSecurity alertsHigh-priority account and platform events
Email / TelegramAssigned TasksDispatch and execution progress
Email / TelegramDeploymentsEnvironment and release status
Email / TelegramSupportNew request and resolution state
Email / TelegramProduct changesCurated Change Log updates
Email / TelegramSecurity boundary
Tokens stay on the server.
Bot tokens, SMTP credentials and inbound-mail secrets are never returned to the browser. Test delivery validates configuration without revealing the secret.
- Independent Agent credentials and Chat IDs
- Explicit event subscriptions
- Test action before operational use
- Deduplicated release and event delivery
- Audit-aware administrative changes
Operational communication