Overview
Telegram does not always publish the Secretary business connection immediately after setup. Telestars distinguishes an undiscovered connection from a known connection that is disabled or lacks reply permissions.
- Recognize Pending as a discovery state rather than an automatic failure.
- Know when a standard bot may be armed before discovery.
- Understand stricter managed-profile behavior.
- Trigger and verify the first inbound business event.
Before you start
- Access to the official @BotFather bot and the Telegram account that owns the bot.
- A Telegram Business profile where the bot should handle private conversations.
- Permission to add and manage bots in the Telestars workspace.
Step by step
- Finish BotFather Secretary Mode, Telegram Business linking, and the required permissions for the exact bot.
- Open My Bots and inspect the business state shown on the bot card.
- If a standard bot has no other activation blocker, enable AI even when the card says Pending discovery.
- Send a new private message from another Telegram account to the linked Business profile.
- Wait for Telegram to send the business connection event or inbound business message, then refresh the bot card.
- If a known connection changes to permission missing or reconnect required, repair Telegram settings and use Check permission.
How it works
These are the product rules and states that matter for this workflow.
| What to know | Telestars behavior |
|---|---|
| Pending discovery | It means Telestars has not yet received the business_connection_id; it does not by itself prove that the Telegram setup is wrong. |
| Standard bot arming | A standard bot can be enabled before discovery when all product and wallet requirements are satisfied; replies begin once Telegram provides the identifier. |
| Known connection checks | When an identifier already exists, Telestars checks whether the connection is enabled and can reply before activation. |
| Managed profile exception | A managed profile requires an explicit linked Secretary connection before its AI switch can be enabled. |
| Main bot role | A main bot routes traffic for managed profiles and is not itself an AI conversation target. |
Verify the result
- The state changes from Pending after a new inbound business message, or AI remains safely armed awaiting that event.
- A discovered connection reports no disabled or missing-reply-permission state.
- The first conversation is attached to the intended bot or managed profile.
Troubleshooting
| If you see this | What to check |
|---|---|
| Pending remains after the first test | Confirm the message came from another Telegram account, then recheck the chatbot link, private-chat scope, and reply permission. |
| The AI switch cannot be enabled on a managed profile | Link that profile to its discovered Secretary connection first; managed profiles do not use the standard pending-arming exception. |
| Reconnect required appears | Remove or repair the disabled Telegram Business chatbot connection, reconnect it, and run verification again. |
Best practice
When setup is complete and the state is Pending, the most useful diagnostic action is a fresh inbound message from a separate Telegram account.