TeleGo Docs

Appearance

Scenarios Overview ​

TL;DR:

  • A Scenario is a visual map of your bot's logic, built using nodes and links.
  • Nodes represent individual steps (like sending a message), while Links define how users move between them.
  • Only the Published version of a scenario is live for your Telegram users.

Who this is for ​

  • Bot Builders designing conversation flows.
  • Product Managers mapping out user journeys.
  • Support Teams wanting to understand how the bot interacts with users.

What you will learn ​

  • What a scenario is and how it relates to your bot.
  • How nodes and links form a logical flow.
  • The difference between draft and published versions.
  • How the bot executes your scenario in real-time.

Overview ​

A Scenario is the "brain" of your Telegram bot. It is a visual representation of every possible interaction a user can have. Instead of writing code, you use a drag-and-drop editor to place Nodes (steps) and connect them with Links (logic paths).

Each bot can have multiple active scenarios, with each one responding to a different Telegram command (e.g. /start, /payment, /help). A scenario dictates how the bot responds to messages, when it saves data, and how it handles complex branching logic like conditions or timeouts. If you do not want to start from a blank canvas, you can also install a scenario template and then customize the generated draft for your bot.

Key concepts ​

  • Scenario --- The complete visual map of your bot's automated logic.
  • Node --- An individual building block that performs a specific task (e.g., Message, Condition, Action).
  • Link --- A connection between nodes that defines the path a user takes.
  • Start Node --- The mandatory entry point where every new conversation begins.
  • Publishing --- The process of deploying your visual flow to the live production environment.

How it works ​

The execution of a scenario follows a logical path determined by the links you draw between nodes.

The Conceptual Flow ​

When a user interacts with your bot, the flow typically follows this pattern:

Draft vs. Published Versions ​

To ensure your bot stays stable while you make changes, the platform maintains two states for every scenario:

  • Draft: Your current work-in-progress in the editor. Changes saved here are not visible to real users.
  • Published: The version currently running in production. Only when you click Publish does your draft replace the live version.

TIP

You don't have to publish to try a flow. Use Test Without Publishing — the beaker (🧪) button on any node gives you a private Telegram link that runs your current draft from that node, without affecting production data.

WARNING

Leaving a node "hanging" without a link is a common pitfall. If a user reaches a node with no outgoing connection, the conversation will stop.

In the UI ​

You manage your scenarios within the Scenario Editor.

  • Location: Bot Dashboard → Scenario Editor
  • Main controls:
    • Canvas --- The main area where you drag, drop, and connect nodes.
    • Node Palette --- A menu of available node types (Message, Condition, Action, etc.).
    • Save --- Stores your changes as a draft.
    • Publish --- Pushes your draft to the live bot.

Examples ​

Example 1 — Simple Feedback Loop ​

Goal: Collect a user's rating and tag them if they are unhappy.

Setup:

  1. Message Node: Asks "How was your experience?" with buttons 1-5.
  2. Condition Node: Checks if the selected rating is less than 3.
  3. Action Node (on the True path): Adds a tag needs_support.
  4. Message Node (on both paths): Sends a "Thank you" note.

Result: Users are automatically segmented based on their feedback, allowing your team to follow up with dissatisfied customers.

Troubleshooting ​

Symptom: Scenario does not run ​

Cause: The scenario may be missing a Start Node or the bot hasn't been published.
Fix: Ensure a Start Node is placed and connected to your first message, then click Publish.
Prevention: Always verify the entry path in the editor before publishing.

Symptom: Cannot publish ​

Cause: Validation errors are present, such as required fields being empty or invalid link configurations.
Fix: Check for red error indicators on nodes. Common issues include empty message text or unconfigured condition rules.
Prevention: Use the Save button frequently; it will often highlight basic errors before you attempt to publish.

Symptom: Flow stops unexpectedly ​

Cause: The user reached a node that has no outgoing link connected to its Next or True/False outputs.
Fix: Inspect the node where the user got stuck and ensure it is connected to a subsequent step.
Prevention: Use the "Auto-layout" or zoom out to visually scan for disconnected nodes.

FAQ ​

  • Q: Can one bot have multiple scenarios?
    A: Yes. The number of scenarios you can create per bot depends on your plan. Each scenario can respond to its own Telegram command (e.g. /start, /payment, /help), and multiple scenarios can be published and active at the same time. You can also maintain unpublished drafts and switch them to active by publishing.

  • Q: What happens if I edit a published scenario?
    A: Your edits are saved as a Draft. The live bot will continue using the old version until you click Publish again.

  • Q: Can I test before publishing?
    A: Yes. Use Test Without Publishing — click the beaker (🧪) button on any node to get a private Telegram link that runs your current draft from that node. It never touches your live users, analytics, or quota. Publishing is only needed when you're ready to go live for real users.

TeleGo.io Docs

Copyright © 2026