Overview
A Welcome DM delay can represent elapsed time or a response gate. A response gate makes the sequence interactive by keeping later steps pending until the fan sends a new eligible message.
- Choose between a timed pause and a response gate.
- Place the gate after a message that clearly invites a reply.
- Verify that later steps remain pending until the condition is met.
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 the Welcome DM builder and add a Delay after the message that should precede the pause.
- Set the intended delay duration within the supported range.
- Enable Wait for fan response when the next step should require a new inbound message.
- Add the continuation steps after the delay and save the sequence.
- Test once without replying, then send a fan response and confirm the sequence advances only once.
How it works
These are the product rules and states that matter for this workflow.
| What to know | Telestars behavior |
|---|---|
| Timed delay | A normal delay advances after its configured duration when the workflow remains eligible. |
| Response gate | Wait for fan response keeps the next step pending until a new eligible fan message arrives. |
| Supported duration | Welcome DM validates delay values from zero seconds through seven days. |
| Durable order | The continuation uses the saved step order rather than choosing a different message dynamically. |
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 next step sent without a reply | Confirm Wait for fan response is enabled on the correct Delay step and the saved version is active. |
| The reply did not advance the flow | Check the active instance, bot scope, Telegram message eligibility, and whether the sequence already completed. |
| The delay feels too long | Edit the saved duration and retest with a new sequence instance. |
Best practice
Test one trigger, one destination, and one complete sequence at a time before adding paid media or longer delays.