TeleGo Docs

Appearance

Quickstart ​

TL;DR:

  • Connect your Telegram bot via token, build a visual flow, and click Publish.
  • Use the Scenario Editor to design automated conversations with nodes and links.
  • Monitor your bot's users and conversation history in real-time through the CRM.

Who this is for ​

  • New Users setting up their first bot.
  • Bot Designers looking to understand the visual flow editor.
  • Workspace Members responsible for managing Telegram user interactions.

What you will learn ​

  • How to connect a Telegram bot to the platform.
  • How to create and design your first automation scenario.
  • How to publish and test your bot in real-time.
  • How to view and manage your bot's users in the CRM.

Overview ​

TeleGo lets you set up a Telegram bot that answers your clients, collects requests, and takes bookings and payments, without code. You describe the bot to the AI Assistant or build the "flow" yourself in the visual Scenario Editor, from nodes (messages, conditions, actions) connected by links.

Once a scenario is published, our runtime engine handles all incoming Telegram messages, executes your logic, and stores user data automatically for you to view in the CRM.

Key concepts ​

  • Bot — A Telegram bot instance connected via an API token from @BotFather.
  • Scenario — A visual map of your bot's logic and conversation flow.
  • Node — A single block in your scenario (e.g., sending a message or checking a condition).
  • Publish — The act of making your scenario live for all Telegram users.
  • CRM — The central dashboard where you see everyone who interacted with your bot.

How it works ​

Getting your bot live follows a simple four-step process:

  1. Connect your Bot: Obtain a token from @BotFather and enter it into the platform's Create Bot dialog.
  2. Build the Scenario: Use the editor to drag and drop nodes. Start with a Start Node and connect it to a Message Node.
  3. Save your Flow: Click Save to store your scenario draft.
  4. Publish: Click the Publish button to make your scenario live, then test it directly in Telegram.

TIP

Always use a Start Node as the entry point for your scenario, otherwise the bot won't know where to begin when a user sends a message.

WARNING

Forgetting to click Publish after making changes is a common pitfall. Saved changes in the editor do not affect the live bot until they are published.

In the UI ​

The platform is organized into a few key areas:

  • Bots List: Your dashboard for all connected bots. Location: Sidebar → Bots.
  • Scenario Editor: The visual workspace where you build flows. Location: Bot Settings → Scenario.
  • CRM: Where you manage user data. Location: Bot Settings → CRM.

Main controls ​

  • Create Bot — Opens the wizard to connect a new Telegram bot.
  • Save — Stores your current scenario draft.
  • Publish — Makes your scenario live for all users. After publishing, test your bot directly in Telegram.

Examples ​

Example 1 — Welcome Message ​

Goal: Send a friendly welcome message when a user first interacts with the bot.
Setup:

  1. Place a Start Node.
  2. Connect it to a Message Node.
  3. In the Message Node, enter: "Hello {%first_name%}! Welcome to our bot."
    Result: When a user sends /start to your bot, they immediately receive the personalized welcome message.

Troubleshooting ​

Symptom: Bot does not respond ​

Cause: The bot might not be published or the Telegram token is invalid.
Fix:

  1. Check the Bot Settings to ensure the token is correct.
  2. Ensure you have clicked Publish at least once.
  3. Verify that the scenario has a Start Node connected to the rest of the flow.
    Prevention: After publishing, test your bot in Telegram to verify connectivity before sharing it with users.

Symptom: Cannot publish scenario ​

Cause: The scenario may contain validation errors, such as disconnected nodes or missing required fields.
Fix:

  1. Look for red warning icons on nodes in the editor.
  2. Ensure every node has a valid path back to the Start Node.
  3. Fill in all required fields (like message content or condition rules).
    Prevention: Regularly save your work to catch errors early.

Symptom: Saved changes not reflected in Telegram ​

Cause: You have saved your changes but haven't published them yet. Only Published scenarios are live.
Fix: Click the Publish button to sync your latest draft with the production engine.
Prevention: Make "Save & Publish" a standard habit after making changes.

FAQ ​

  • Q: How do I get a Telegram token?
    A: Message @BotFather on Telegram and use the /newbot command. He will provide a token that looks like 123456:ABC-DEF1234ghIkl-zyx57W2v1u123ew11.

  • Q: Can I have multiple scenarios for one bot?
    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: How do I safely test changes without affecting live users?
    A: Since there is no built-in version history, the best approach is to duplicate your scenario, give it a test command (e.g. /start_v2), hide it from the menu, and publish it. Test in Telegram, and when ready — unpublish the old one, rename the new one to the original command, and publish. This way you can maintain multiple versions and switch between them with zero downtime. See detailed workflow.

  • Q: Is the CRM data real-time?
    A: Yes, users and messages appear in the CRM as soon as they are processed by our runtime engine.

TeleGo.io Docs

Copyright © 2026