Overview
My Bots combines plan, AI, Secretary, runtime, and readiness signals. The visible badge and expanded blocker list tell you whether to complete setup, trigger discovery, restore Telegram permissions, or repair a failed script asset.
- Interpret AI off, AI on, Pending, Needs permission, Reconnect, and AI paused states.
- Use the blocker’s direct dashboard action.
- Repair a disabled or permission-limited Secretary connection.
- Avoid enabling AI on a routing-only main bot.
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
- Open My Bots and locate the exact @username or managed profile that is not behaving as expected.
- Read the status badge and summary, then expand the card to expose Finish setup or Needs attention details.
- Use the provided action to open Creator info, Scripts, Billing, AI setup, or Check permission rather than changing unrelated settings.
- For Needs permission, restore Telegram Business reply permissions; for Reconnect, repair or recreate the chatbot link on the same profile.
- For AI paused after script media delivery, open the highlighted script or asset and restore Telegram readiness.
- Refresh the card, verify the connection when available, deliberately re-enable AI, and repeat the separate-account live test.
How it works
These are the product rules and states that matter for this workflow.
| What to know | Telestars behavior |
|---|---|
| AI paused | A runtime safety reason such as script media delivery failure can disable AI and retain metadata that points to the affected script, step, or asset. |
| Needs permission | The connection exists, but Telegram reports that it cannot reply with the current permissions. |
| Reconnect | The previously discovered business connection is disabled or invalid and must be restored in Telegram Business. |
| Role-aware toggle | Main bots are routing-only; managed profiles need a linked connection; standard bots may be armed while discovery is pending. |
| Targeted actions | Each activation blocker maps to the dashboard surface where the underlying state can be fixed. |
Verify the result
- The status badge reflects the intended state and the expanded blocker list is empty or understood.
- Check permission succeeds for a discovered Secretary connection.
- A new test message receives one reply and appears in Fan Inbox.
Troubleshooting
| If you see this | What to check |
|---|---|
| Check permission cannot verify right now | Confirm Telegram is reachable and the connected token is current, then retry without changing unrelated creator or script data. |
| AI remains paused after repairing an asset | Verify the replacement is ready for the target bot and the active script is valid, then deliberately turn AI back on. |
| Messages route to the wrong managed profile | Review the discovered business connection assignment and link it to the intended managed profile before testing again. |
Best practice
Use one clearly named BotFather bot per intended profile, keep tokens private, and verify every connection with a real message from a second account.