TeleGo Docs

Appearance

Changelog

Track product releases, platform fixes, and the bigger workflow changes that shape how TeleGo is used.

v1.14.0
October 10, 2026

From a description to your first request

Describe your service, paste your prices, and the bot answers clients from them, collects a request and sends it to your Telegram. Test it and get a [TEST] request yourself before you publish.

Now you can:
  • Requests in your Telegram: the AI Assistant ends a request with a ready message (name, phone, goal) sent to you, and sets up the notifications from the editor.
  • Your prices and terms right while describing the bot: the bot uses them in its messages and AI answers, and they are saved to a knowledge base.
  • Fill in all placeholders in one place, and test as a client: the request comes to you marked [TEST].
  • Human Handoff step: Custom setup — choose who gets this step's notification and write its text with the client's answers and other variables. People chosen in the step get it even when the bot's notifications are off.
  • Set up notifications from the editor and the AI Assistant: link your Telegram, press Start in your bot and turn notifications on for yourself, without leaving the scenario.
  • AI Assistant: asks for your services, prices and terms when the bot talks about them, uses them in the plan and saves them to a knowledge base connected to the AI steps.
  • AI Assistant launch card: replace each placeholder once for all steps, connect a knowledge base or paste your text, and turn on requests in your Telegram.
  • Two ready starting points: "Collect consultation requests" and "Answer questions and offer a consultation".
AI AssistantActions nodeTesting
v1.13.0
October 3, 2026

AI Assistant and AI on every plan

Describe your bot in plain words and the AI Assistant builds the flow. And AI is no longer Pro-only: Starter includes 500,000 AI tokens a month.

Now you can:
  • AI Assistant in the editor: describe the bot, review the plan, click Create scenario. Select a node to ask about it or change it.
  • Starter now includes AI: 500K AI tokens per month, up to 2 AI Agent nodes per scenario and a small knowledge base.
  • Higher daily AI limits on every plan.
  • AI Assistant builds a whole scenario from a short description: it asks a few questions, shows the plan (steps, buttons, fields and tags) and creates connected nodes when you confirm.
  • AI Assistant can explain or change the selected node, and it knows about the AI Agent node and its On error output.
  • Message node: media "From variable" sends a file whose URL was saved to a variable earlier in the flow.
  • AI Agent node, On error output: route the flow when the AI provider fails or the AI token limit is reached.
AI AssistantAI AgentPlans and limits
v1.12.0
October 3, 2026

Group moderation

Your bot can now keep Telegram groups and channel comments clean: it deletes spam, links and swearing, penalizes repeat offenders and logs every action — set up with switches in the bot settings, no scenario needed.

Now you can:
  • New Bots -> Moderation section: connect up to 5 groups, switch rules on and choose a warning -> mute -> ban ladder.
  • Rules for links and invites, profanity, forbidden words, forwards, flood, new members, posting as a channel, and an AI filter.
  • Built-in profanity dictionaries for Russian, English, Ukrainian, Spanish, Portuguese, German and Turkish, plus AI-drafted dictionaries for any language.
  • Journal with search, filters and one-click Lift; statistics in Analytics -> Group Moderation.
  • Group moderation in the bot settings: rules, penalty ladder, warning message with auto-delete, and per-group status with the rights the bot is missing.
  • Moderation Journal: every violation with member, group, rule, penalty and message fragment; search, filters, sorting and Lift for mutes and bans. Events are kept for 90 days.
  • Analytics -> Group Moderation: violations, deleted messages, mutes and bans with period comparison, daily chart, top reasons, offenders and groups.
  • A bot can run moderation only: turning moderation on activates the bot without a published scenario.
  • Test mode (only log): the bot journals what it would do without deleting anything, so you can tune the rules on a live group.
  • The links rule also removes @mentions of other channels and groups; edited messages and albums are checked too.
Group ModerationAnalyticsGroups & channels
v1.11.0
August 2, 2026

Trial access lifecycle

Trial workspaces now have a clear seven-day limited-access period after the trial, followed by a pause until a paid plan is selected.

Now you can:
  • Every new workspace starts with a seven-day trial.
  • After the trial, bots can remain available in limited mode for seven more days.
  • After the limited period, bot automation is paused until access is extended.
  • Deployments do not restart an existing workspace trial or limited-access countdown.
  • A dedicated guide explains the trial, seven-day limited-access period, and what happens when access is not extended.
BillingTrial access
v1.10.0
June 2, 2026

Lead Scoring

Assign numeric scores to users based on their actions and behaviour. Use scores to segment your audience, personalise flows, and route users to different branches.

Now you can:
  • Three score actions in the Actions node: Add, Subtract, Set
  • Lead score condition — branch flows based on current score
  • Score visible in CRM user profile and sortable/filterable in the user list
  • Score available as {%lead_score%} in Message and Formula nodes
  • Lead score actions in the Actions node. Three operations: **Add** (increases score by N), **Subtract** (decreases score, clamped to 0), and **Set** (sets an exact value). All operations are atomic and clamped to the range 0–2,000,000,000.
  • Lead score condition in the Condition node. Branch flows using operators: equals, not equals, greater than, greater or equal, less than, less or equal. Score is read directly from Redis at evaluation time — Redis miss is treated as 0.
  • `{%lead_score%}` macro available in Message and Formula nodes. Read-only — use Actions node to modify the value.
  • Lead score column in the CRM users table. Sortable and filterable (Add Condition → Lead score). Score visible in user profiles and sidebar.
  • Lead score filter in Broadcast audience builder — send to users above or below a score threshold.
Scenario BuilderCondition NodeCRM
v1.9.0
June 1, 2026

CRM Chat — Media Transcription

Audio and video messages in the CRM chat can now be transcribed on demand. Click a button — get the text. No need to listen to every voice message.

Now you can:
  • Transcribe button on audio, voice, video, and video note messages
  • Transcript appears inline below the media bubble
  • Failed transcriptions show an error with a retry option
  • Added on-demand media transcription in the CRM conversation view. Operators can click Transcribe on audio, voice, video, and video note messages to get a text transcript.
  • Transcripts render inline below the media bubble with a Captions icon. If no speech is detected, "No speech detected" is shown.
  • Transcription runs in the background — a spinner appears while processing, and the result updates automatically.
  • Failed transcriptions display an error message with a Retry button.
CRM ChatAI Transcription
v1.8.0
May 30, 2026

Test Mode — Start Scenario from Any Node

Any node can now be a starting point. Click Test from Node in the editor, scan the QR — and the bot runs the scenario from that exact step. Delays and schedules fast-forward automatically, no publishing required.

Now you can:
  • Test any node directly from the scenario editor without publishing
  • Delays and schedules skip waiting in test mode — the flow continues instantly
  • No analytics pollution — test sessions are excluded from stats
  • Unpublished scenarios can be tested end-to-end before going live
  • Added "Test from Node" mode — start a scenario from any node by scanning a QR code or deeplink, without publishing the scenario first.
  • Delay and schedule nodes fast-forward automatically in test mode. The flow continues immediately instead of waiting, so the entire scenario can be reviewed without delays.
  • Test sessions are marked as test-only and excluded from analytics, AI usage, and conversion tracking. The flow runs faithfully but side effects are gated.
  • External actions like operator handoff are skipped in test mode with a notice, so testing does not wake real support operators.
  • Integrations (Sync HTTP, webhooks, email) and Telegram admin actions (ban/unban) run for real in test mode, allowing end-to-end verification of configured integrations.
Scenario EditorTesting
v1.7.0
May 15, 2026

Scenario Variables — First-Class Across All Nodes

Scenario variables (`var.*`) are now fully supported across Formula, Condition, Question, Sync HTTP, and AI Agent nodes. A new persistent tier (`var.key+`) lets variables survive session restarts without touching the CRM. Most flows that previously required custom CRM fields can now use scenario variables instead.

Now you can:
  • `var.*` variables can now be read and written in every major node type — no workarounds needed
  • New persist tier: `var.key+` survives `/start` and is remembered across sessions without syncing to the CRM
  • Question cards can save answers directly to `var.*` — no CRM field required
  • Condition node can now branch on any scenario variable value
  • AI Agent automatically injects current session variables into the system prompt
  • Added `var.key+` persist syntax in the Formula node. Variables written with a trailing `+` are stored in a dedicated per-user key and survive `/start`. Session and persist stores are mutually exclusive per key — writing to one automatically clears the other.
  • Added a Variable rule kind to the Condition node. Scenarios can now branch on any `var.*` value using the same operator set available for CRM fields. Persist variables take priority over session variables when both are set.
  • Added a Scenario variable save target to Question cards. Setting the target to `var.*` saves the answer to the session store; adding a `+` suffix saves to the persist store. Neither option pushes data to the CRM.
  • Added `var.*` and `var.*+` as response mapping targets in Sync HTTP. API responses can now be mapped directly into scenario variables without creating CRM fields.
  • Added a Scenario variable input mode to the AI Agent node. The node can now read a specific `var.*` value as its main input text.
  • AI Agent nodes now automatically inject all active session and persist variables into the system prompt as a `## Session Variables` block, giving the AI access to scores, levels, and computed values without any extra prompt engineering.
Variables and TagsFormula NodeCondition NodeMessage NodeAI Agent NodeActions Node — Sync HTTP
v1.6.1
May 2, 2026

Calendar Booking Stability and Bot-Level Calendar Defaults

Improved Google Calendar booking reliability with safer reminders, clearer calendar selection rules, and per-bot calendar overrides on top of the workspace default.

Now you can:
  • Bots can now override the workspace default calendar without editing every booking card
  • Calendar reminders survive normal scenario restarts and are replaced correctly after rebooking
  • Booking docs now reflect the actual workspace, bot, and runtime fallback chain
  • Added a bot-level booking calendar override, so one bot can use a different calendar while the workspace keeps a shared default connection.
Calendar IntegrationBot CustomizationMessage Node
v1.6.0
May 1, 2026

Google Calendar Booking in Message Flows

Introduced Google Calendar booking directly inside Telegram message flows, with real-time slot selection, automatic event creation, booking context variables, and workspace-level calendar defaults.

Now you can:
  • Calendar Slot Picker cards let users choose real appointment slots directly in Telegram
  • Workspace Integrations now include Google Calendar connection, booking defaults, and a default calendar selector
  • Booked slots can create Google Calendar events automatically and expose booking variables to the rest of the scenario
  • Bots can branch on booking status and use reminder messages built from calendar context
  • Added Google Calendar integration in Workspace Settings so teams can connect a Google account, choose a default calendar, and configure booking defaults such as working hours, weekdays, slot duration, and conflict retry behavior.
  • Added the Calendar Slot Picker card to Message nodes, allowing users to choose available dates and times directly in Telegram.
  • Added automatic Google Calendar event creation after slot confirmation, with customizable event title and description.
  • Added booking context variables such as `calendar.date`, `calendar.time`, `calendar.event_id`, and `calendar.event_link` for downstream messages and logic.
  • Added calendar booking checks to Condition flows so scenarios can branch when a user already has an active appointment.
Calendar IntegrationMessage NodeCondition Node
v1.5.0
April 30, 2026

Payment Integration: Telegram Stars, Stripe, and Product Catalog

Introduced a full-scale payment and monetization system. Bot builders can now create products, accept payments via Telegram Stars or Stripe, and manage subscriptions directly within scenarios.

Now you can:
  • Accept Telegram Stars (XTR) for frictionless in-chat payments
  • Integrated Stripe Checkout for card and international payments
  • Centralized Product Catalog for managing workspace-level monetization
  • Advanced payment status checks in Condition nodes for gated access
  • Added Telegram Stars (XTR) support for instant digital sales within the app.
  • Added Stripe integration for global card payments and secure checkout flows.
  • Introduced the Product Catalog in Workspace Settings for centralized price management.
  • New "Wait for Input" mode for AI Agent nodes to enable natural multi-turn conversations.
  • Introduced the Scenario Loop Detector to prevent accidental execution loops.
  • Added UTM macro picker for message buttons to simplify marketing tracking.
  • New global {first_name} macro for personalized user interactions.
Message NodeProductsCondition NodeBilling
v1.4.0
April 2, 2026

AI Agent output reliability, Telegram formatting, and timeout recovery

Focused on polish for AI-driven flows: better output handling in later message nodes, safer Telegram formatting behavior, and in-place recovery when idle sessions expire.

Now you can:
  • AI answers are easier to reuse in later message nodes
  • Telegram-facing output got safer formatting behavior for Markdown-heavy responses
  • Idle timeout sessions can recover in place instead of silently going dead
  • Improved how AI Agent outputs are carried forward and reused by later flow steps.
  • Clarified session restart behavior after timeout so users can continue instead of getting silence.
  • Polished node UI details around AI and message flow previews.
AI AgentMessage NodeScenarios
v1.3.0
March 30, 2026

Scenario Templates gallery, preview, and install workflow

Added the first full pass of Scenario Templates so builders can browse a gallery, preview dependencies, and install reusable starting flows into a bot.

Now you can:
  • Scenario Templates now have a dedicated gallery and detail view
  • Templates can be previewed before install, including dependency summaries
  • Install flow creates a scenario draft and checks blockers before setup
  • Added a template gallery with search, category filtering, and template detail pages.
  • Introduced install preflight reporting for fields, tags, globals, assets, AI presets, and integrations.
  • Created a reusable install flow that turns a template into a new bot scenario draft.
Scenario TemplatesScenariosAssets
v1.2.0
March 22, 2026

AI settings, RAG knowledge bases, and Sync HTTP foundations

This release expanded the AI toolset with workspace AI settings, retrieval-augmented responses, and stronger groundwork for Sync HTTP actions inside scenarios.

Now you can:
  • Workspace AI settings became easier to manage centrally
  • AI Agent flows gained knowledge-base-backed RAG support
  • Sync HTTP actions moved closer to production-ready scenario usage
  • Introduced workspace AI settings and knowledge-base-backed RAG support for AI-driven flows.
  • Added the first public-facing building blocks for Sync HTTP scenario actions.
AI AgentAI SettingsSync HTTP
v1.1.0
March 9, 2026

Analytics reporting refresh across performance and audience views

Expanded analytics work across charts, audience reporting, and scenario-focused insights so teams can move from raw bot activity to a more actionable reporting view.

Now you can:
  • Performance and audience reporting received focused updates
  • Analytics filters and drill-down behavior improved across bots and scenarios
  • User analytics and reporting UX continued to mature
  • Refined analytics data flows across message, session, and audience reporting.
  • Improved scenario-oriented analytics behavior and drill-down paths.
  • Polished the reporting experience around users and recent activity.
AnalyticsCRM Users
v1.0.0
February 27, 2026

Asset uploads in message flows and richer media reuse

Started connecting reusable asset management more tightly to the scenario builder, making it easier to work with uploaded media inside message-driven flows.

Now you can:
  • Message flows can rely on reusable uploaded assets instead of one-off file handling
  • Media reuse became a clearer part of scenario building
  • Asset-based content became easier to manage across updates
  • Initial support for asset uploads connected to message-node workflows.
  • A clearer path toward reusable media instead of ad-hoc file usage in each scenario.
AssetsMessage Node

TeleGo.io Docs

Copyright © 2026