AI Assistant and AI Builder

TL;DR:

• The AI Assistant panel in the Scenario Editor has two modes: Change and Ask.
• In an empty scenario, Change builds the whole bot from your description: a few questions, a plan, then Create scenario.
• In a scenario with content, Change proposes an edit as a card. Nothing changes until you click Apply, and Undo reverts exactly that change.
• Ask explains nodes and your scenario without changing anything.
• Available on all plans and uses AI tokens from your plan.

Who this is for

• New users who want a working bot without learning every node first.
• Builders who want to add a step, a check or a branch by describing it instead of wiring nodes by hand.
• Anyone who wants a quick answer about how a node works while editing.

What you will learn

• How to build a scenario from a description.
• How to change an existing scenario in words and undo a change.
• How to ask questions about nodes and your scenario.
• How to write requests that work well.

Overview

The AI Assistant is a panel on the left side of the Scenario Editor. You talk to it in plain language, in any language.

Under the hood, the AI does not draw nodes directly. It writes a short plan of steps (send a message, ask a question, check a condition, wait, and so on), and the editor turns that plan into real nodes. Every plan is checked before you see it: broken links, unreachable steps and unsafe loops are fixed automatically or reported. This is why changes come out as clean, connected flows.

Key concepts

• Change mode - Builds a new scenario or proposes an edit to the current one.
• Ask mode - Answers questions. Never changes the scenario.
• Plan - The list of steps the AI will create, shown before anything is added.
• Change card - A proposed edit to an existing scenario: where it goes and what it adds. Apply or Discard.
• Selected node - If a node is selected on the canvas, the assistant uses it as context ("add a reminder after this").

How it works

Build a new scenario

1. Create a scenario. The What do you want to build? window opens on Describe with AI.
2. Describe the bot, or pick an example, and click Build my bot. The first two examples — Collect consultation requests and Answer questions and offer a consultation — have [blanks] for your business: type over them.
3. The window closes and the AI Assistant panel continues the conversation.
4. The assistant may ask a few quick questions. Tap an answer, type your own, or skip — unanswered questions are decided for you. If the bot will talk about your services, it also offers a box for your services, prices and terms: paste them, and the bot uses real prices in its messages and its AI answers (the text is saved to a knowledge base you can edit later).
5. Review the plan: steps, buttons, branches, the fields and tags it will add to your workspace, and what the assistant assumed (for example, that payments stay manual). If an assumption is wrong, say so in the message box.
6. Want something different? Type it in the message box ("Also ask for the phone number"). The assistant updates the plan.
7. Click Create scenario. The nodes appear on the canvas, and the panel shows what is left before clients can use the bot:
   • Replace the placeholders: links the assistant could not know (https://example.com) and facts in square brackets such as [price]. Type the real value next to each one and click Apply — the same placeholder is replaced in every step at once (one Undo brings them back). Click a step name to open it on the canvas. To change wording, just write it in the message box ("make the greeting shorter").
   • Give the AI step your prices, schedule and terms (if the bot has an AI answer step): pick a knowledge base you already have, or paste your service description, prices and frequent questions and click Save and connect. The AI step starts using it as soon as the text is read (about a minute). Until then the AI answers only in general terms and offers to pass questions to you.
   • Connect your Telegram bot.
   • Get requests in your Telegram (if the bot passes requests or questions to you): Set up links your Telegram account, asks you to press Start in your bot and turns the notifications on for you.
   • Test it as a client — when you reach the end of a request, the request comes to your Telegram marked 🧪 [TEST] — and Publish.

You can also start from an empty scenario at any time: open AI Assistant, keep Change selected, and describe the bot.

Change an existing scenario

1. Open AI Assistant and keep Change selected.
2. Optionally select the node the change is about.
3. Describe the change. While the assistant works, you see what it is doing (reading the scenario, drafting, checking).
4. Review the change card: where the change goes (for example, After "Start" → Next) and the steps it adds. A new text is shown next to the current one.
5. Click Apply. New nodes are placed next to the spot they connect to, without covering existing nodes.
6. Changed your mind? Click Undo on that card. It reverts only that change; your other edits, including ones you made later, stay.

Ask a question

Switch to Ask and type your question. Answers are based on the TeleGo documentation and your current scenario. When the answer describes a change, it ends with a Make this change button that sends it in Change mode.

In the UI

• Open AI Assistant - The magic wand button at the top left of the canvas. On a phone the panel opens full screen.
• Change / Ask - The mode switch under the message box.
• Apply / Discard - On a change card, add the change to the draft or dismiss it.
• Undo - On an applied change card, revert that change only.
• Create scenario - On a plan, create the nodes in the empty scenario.
• Clear conversation - The trash icon. Clears the conversation for this scenario.

The conversation is saved per scenario in your browser, so it is still there after a page reload.

Examples

Example 1 - Channel subscription gate

Goal: Give a gift only to subscribers of your channel. Request:

Before the gift, check that the user is subscribed to @mychannel. If not, ask to subscribe and add a "Check again" button.

Result: A Condition node with the rule Subscribed to group/channel, a gift message on Match, and a "please subscribe" message on No Match whose Check again button leads back to the check. Make the bot an admin of the channel — see Condition.

Example 2 - Lead magnet from scratch

Goal: Collect contacts in exchange for a checklist. Request (in an empty scenario):

Lead magnet: give a free checklist in exchange for name and email, then offer a consultation two days later.

Result: A plan with name and email questions, the checklist delivery, a 2-day wait and a follow-up offer. The fields are created in your workspace when you click Create scenario.

Example 3 - Small edits

More requests that work well:

After the user leaves a phone number, tag them as lead and notify a manager.

Send a reminder 1 day after the last message if the user did not answer.

Change the welcome text to: Hi ! Pick what you need below.

Example 4 - Questions

How do I send a reminder the next day?

What is the difference between Question and Condition?

Why does my Check again button not lead anywhere? (with that node selected)

Writing good requests

• One change per message. "Add a phone question after the greeting" works better than a full redesign in one go.
• Say where. Mention the node title or select the node: "after Welcome", "on the No Match branch".
• Give exact values. Channel @username, button labels, delays ("2 days"), texts in quotes.
• Say who your clients are. The bot talks in your clients' language, which can differ from yours: "a coach in the US, clients speak English" builds an English bot even if you write in another language. If it is unclear, the assistant asks.
• Iterate. If the result is close but not right, describe what to change instead of starting over.
• Long texts: select the step. To change a part of a long message (a price, a phone number), select that step first. The assistant then reads the whole text and keeps everything you did not ask to change.

Troubleshooting

Symptom: "AI tokens are used up"

Cause: Your plan's AI token budget for this period is spent. Fix: Click Upgrade plan, or continue editing by hand. Daily and monthly AI limits renew automatically.

Symptom: The change card says it could not prepare a valid change

Cause: The request was ambiguous or pointed at something that does not exist in the scenario. Fix: Rephrase with the exact node title, or select the node first and send again.

Symptom: "This change no longer fits the scenario" on Apply

Cause: You edited or deleted the nodes the change relies on after it was proposed. Fix: Send the request again — the assistant reads the current scenario every time.

Symptom: "Select this step on the canvas and ask again"

Cause: The text you want to change is long, and the assistant saw only its beginning. Rewriting it would lose the rest. Fix: Select the step on the canvas and send the request again.

Symptom: "You edited this text after the suggestion was made"

Cause: You changed the same text by hand after the change card appeared. Applying it would overwrite your edit. Fix: Send the request again — the new suggestion starts from your text.

Symptom: A plan or answer failed with an error

Cause: The AI provider did not answer in time or returned something unusable. Fix: Click Try again on that message. Your description, answers and details are sent again — nothing to retype.

Symptom: "AI is turned off for your workspace"

Cause: The scenario has an AI step, but AI is switched off in Workspace settings → AI. The assistant turns AI on by itself only when the AI settings were never saved and you are the owner or an admin. Fix: Click Turn on AI, or ask the workspace owner to turn it on.

Symptom: "The AI assistant … is turned off" or "The AI model of … is no longer available"

Cause: The change reuses an AI assistant (preset) that is switched off, or whose model was retired. Fix: Click Open AI assistants and turn it on or choose another model. Without the right to manage AI assistants, ask the workspace owner.

Symptom: "This change is not on the canvas any more"

Cause: The change was applied, but the page was reloaded before the scenario was saved, so the editor shows the saved version. Fix: Click Apply again. Fields, tags and AI assistants created the first time are reused, not duplicated. Save the scenario afterwards.

Symptom: Undo does not restore a link

Cause: You changed that link yourself after applying. Undo never overwrites your own later edits. Fix: Reconnect the link by hand, or use the editor's own undo.

FAQ

• Q: Does the assistant change or publish my bot by itself?A: No. Changes are applied only when you click Apply or Create scenario, and publishing is always a separate step.

• Q: Which plans include it?A: All plans. It uses AI tokens from your plan.

• Q: Can I edit what the AI created?A: Yes. The result is ordinary nodes — edit, move or delete them like any other.

• Q: The connection dropped while I clicked Apply or Create scenario. Is it safe to click again?A: Yes. A repeated Apply reuses what the first one created, and a repeated Create scenario for the same plan just opens the scenario.

• Q: I pasted my bot token into the chat. Did the AI see it?A: No. The token is removed from the message before it is sent or saved, and the AI sees [TG_TOKEN] instead. The panel offers Connect to this bot: it connects the token to the bot you are editing, with the same checks as Bot settings, and asks first if the bot already has a token.

• Q: Is the conversation shared with my team?A: Not yet. It is saved in your browser for each scenario.

• Q: Does it answer the same way as the support chat?A: Yes. Ask mode uses the same knowledge base as the TeleGo support chat, plus the node documentation.

Related pages

• Scenarios Overview
• Scenario Templates
• Condition node
• Publishing Scenarios

Notes / Limits

• The AI builds with these building blocks: messages with buttons, questions, choices, conditions (fields, tags, lead score, channel subscription), tags, saved values, lead score, operator handoff (a ready request with the client's answers sent to your Telegram), delays, waiting until a date, A/B splits and AI answers. Payments, the calendar slot picker and integrations are added by hand for now.
• Building from a description replaces the empty scenario. A scenario counts as empty when it has only Start, or Start and the untouched first message that Start blank adds. Once you edit that message, the assistant proposes edits instead.
• The plan fits your subscription: the number of nodes and AI answer steps per scenario is limited by your plan (see Plans and limits). If a plan does not fit, the assistant says so before Create scenario.
• The assistant never invents prices, addresses, schedules or links: it leaves placeholders for you to fill in.
• Waits keep their exact length: "wait 36 hours" becomes a 1-day and a 12-hour Delay one after another.