Overview
Bot Flow controls the exact sequence inside a standalone bot conversation after `/start`. You can build and save a draft, preview it, and publish only when every step and delivery dependency is valid.
- Build a structured `/start` journey.
- Preview and save a draft without activating it prematurely.
- Publish the validated sequence for live bot starts.
Before you start
- Choose the Telegram trigger and destination before building message steps.
- Prepare every Gallery asset for the bot that will deliver it.
- Use a test account to validate the complete Telegram path before enabling live traffic.
Step by step
- Open Bot Flow and select the Telegram bot fans will start.
- Add an opening text step that explains the next action clearly.
- Add and reorder any media, voice, delay, or additional text steps.
- Preview the complete sequence and resolve all validation errors.
- Save the draft, then publish it when the dashboard confirms the selected bot can activate the flow.
How it works
These are the product rules and states that matter for this workflow.
| What to know | Telestars behavior |
|---|---|
| Trigger | The published flow runs from the bot `/start` journey. |
| Step limit | A Bot Flow supports up to 100 ordered steps. |
| Draft state | Saving a draft does not make that version the active `/start` experience. |
| Validation | Empty text, missing media, invalid delay, unsupported bundle, or invalid price prevents publication. |
Verify the result
- Trigger the workflow from Telegram and confirm each configured step arrives once and in order.
- Confirm media, buttons, delays, and paid state match the builder preview.
- Verify that saving, starting, pausing, or disabling the workflow leaves a clear dashboard status.
Troubleshooting
| If you see this | What to check |
|---|---|
| The draft saves but cannot publish | Use the access and validation state shown for the selected bot, then resolve the first listed blocker. |
| The old flow still runs | Confirm the edited version was published rather than only saved as a draft. |
| A test does not restart | Use a fresh test context or the repeatable behavior exposed by the current flow rather than assuming every completed start resets. |
Best practice
Make the first live version short. Validate one complete `/start` journey before expanding it toward paid steps or long waits.