Overview
Telestars delivers dashboard alerts through one connected agency bot and a private Telegram recipient. The dashboard creates a short-lived, one-time /start link that proves which Telegram account belongs to the current workspace member.
- Choose an eligible notification bot.
- Complete the private account binding securely.
- Recognize Connected, Connecting, and disconnected states.
- Reconnect after an expired or replaced link.
Before you start
- An active Telestars workspace membership.
- At least one connected bot with a Telegram username when enabling Telegram delivery.
- A valid account email when enabling email delivery.
Step by step
- Open Notifications → Channels and locate the Telegram row.
- Choose a connected workspace bot that has a Telegram username.
- Select Connect or turn on the Telegram switch; Telestars opens a private Telegram URL containing a one-time /start payload.
- In Telegram, start the selected bot from your own private account and wait for its confirmation message.
- Return to Telestars while the page polls for confirmation and verify that the row says Connected privately through the selected bot.
- Send or trigger a permitted test event, then reconnect with a fresh link if the binding expired or was disabled.
How it works
These are the product rules and states that matter for this workflow.
| What to know | Telestars behavior |
|---|---|
| Eligible bot | The selected bot must belong to the active organization and have a Telegram username. |
| One-time link | The /start token is single-use and expires after a short connection window, so generate a fresh link instead of reusing an old one. |
| Private recipient | The completed start command stores the private Telegram user ID for the current Telestars member. |
| Workspace bot consistency | An organization uses one active bot identity for Telegram notification delivery; switch deliberately if another bot is already active. |
| Connection confirmation | The dashboard only treats Telegram as connected when both delivery is enabled and a private Telegram user has been bound. |
Verify the result
- The selected bot name or @username appears in the Telegram channel row.
- The dashboard reports a private connected state rather than only Connecting.
- A test alert reaches the intended private Telegram chat.
Troubleshooting
| If you see this | What to check |
|---|---|
| The bot says the link is expired or invalid | Return to Notifications and generate a new connection link; old or already-consumed tokens cannot be reused. |
| Another notification bot is already active | Disconnect or coordinate the workspace’s existing Telegram notification bot before choosing a different one. |
| Telestars stays on Connecting | Confirm the /start command completed in the exact selected bot, return to the visible browser tab, and use Reconnect if the polling window ended. |
Best practice
Keep in-app alerts enabled as the audit trail, then add Telegram or email only for the events that require attention away from the dashboard.