Do I need to know how to program?
No. The dialog is assembled with the mouse from ready-made blocks: drag a question, write the text, connect with an arrow — that is the whole scenario. Programming is needed only for your own scripts, and even then optionally: most bots get by without a single line of code.
Do I need a real bot in Telegram to start?
No. The application has a built-in emulator — a replacement for Telegram: you create a test bot with fake conversation partners, open it, write to it and check the whole dialog. No token, no registration with @BotFather and no internet are needed for that. When everything is ready, you simply swap the token for a real one — the scenario does not change.
Do I need Xedant Agent?
No, it is an optional part. Without it only the chat with the AI agent is hidden; everything else works as usual. With it, you can ask for edits in plain words: “add return handling”, “make the greeting friendlier” — the agent finds the right bot file and changes it itself. For that, the address and key of your Xedant Agent are set in the settings.
Where is the data stored?
On your server, in permanent volumes: /apps/chatbot — the database, session keys, the bots’ media library and knowledge bases, /project/apps/chatbot — bot files and scripts. Nothing leaves them except requests to the AI models you choose and calls to Telegram. The data survives container recreation, and when needed moves to another server by simple copying.
How much does the license cost and what does it give?
The personal license is
Can I move a bot to another server?
Yes. A bot is fully described by files: the scenario, settings and scripts are plain text files. The bot’s folder can simply be copied to another server and started there — no export or import is needed. The same works for backups and for keeping versions in Git.
Will Telegram ban the bot?
The application respects Telegram’s limits: broadcasts go through a queue with delays, and the bot receives messages the official way — through the Telegram Bot API. For building and checking the scenario, a real account and a real bot are not needed at all: the emulator serves exactly that. While you are testing, nothing is sent out at all.
How is this different from cloud builders?
The program runs on your server: the data and the clients stay with you, there is no subscription for every dialog, and the scenario can be taken out as files and kept. Cloud builders are convenient at the start, but they tie you to someone else’s service and tariffs. Here a bot can be built in both places — the difference is who owns the data and how much the next dialog costs.
How do I connect a live operator?
The bot hands the conversation to an operator by itself — by a rule (several failed answers, silence, a keyword) — or a Handoff node is placed at the right spot in the scenario. The operator sees the message history and the client card, replies manually and can return the conversation to the bot. Every handoff sends a notification to the service Telegram chat with a link to the conversation. Details in the Inbox section.
What about visitors’ personal data on the website?
The widget asks for consent to data processing before the first message: the checkbox is not pre-ticked, and without it the chat does not start. The consent record itself — time, address and the text shown — is saved and available for review. The platform suggests ready consent wording in the widget settings, exactly what a privacy policy needs. Details in the Website Widget section.