Xedant Chatbot Agent

Telegram bots and chat on your website: build the dialog with your mouse, test it on the emulator and hand part of the answers to AI

Chatbot Agent is a program for building and managing bots that you run on your own server. The bot is assembled in a visual studio from ready-made blocks, checked on the built-in emulator — without a real Telegram, a token or the internet — and connected to AI with a knowledge base. The same bot answers in Telegram, on a public chat page and as a widget right on your website. And when the ready-made capabilities are not enough, they are extended with a small Python script: your own system is connected to the bot, your own channel like SMS or email — and even your own AI model.

Visual studio: assemble the dialog from blocks with the mouse

18 node types: messages, questions, conditions, AI, knowledge base, HTTP, scripts

Live preview: see how the message looks in Telegram

Bot templates and first-draft generation with AI

Version history: bring back an earlier scenario in one click

Publish checklist: 14 checks that the bot is ready

The scenario is a file: take it out, edit it, move it anywhere

Telegram emulator: test without a real bot, token or network

Dry run: the bot answers but sends nothing to anyone

Single node runs, replay of recorded dialogues, full tracing

Pauses, timeouts and scheduled runs survive a restart

Segment broadcasts with pause and resume

Logs and the status screen: everything visible in real time

Runs on your own server in one container, all data stays with you

Economical in idle: the processor is not loaded, and the memory in use is released after 15 minutes without activity — the product sits comfortably alongside other services on one server

Knowledge base: answers from your documents with a source link

Search the base two ways at once: by meaning and by words

AI never invents: no answer in the base means an honest reply, not a guess

Models: your own keys, a model per node, fallbacks if one fails

Prompts in one place: an edit applies to every bot

Inbox: an operator picks up the dialogue with its history and client card

Chat room and website widget: the same dialogues without Telegram

Bots under your control

The Demo Bot page: running status, the Telegram connection with the emu: emulator token, and cards for the public chat page, website widget, broadcasts and runtime health

A new bot in a minute: a name and a token from @BotFather — and it is in the list

The scenario is an ordinary file: take the bot out and edit it by hand

Version history: any earlier scenario comes back in one click

Publish checklist of 14 checks: is the bot ready for people

The flow studio

The flow studio: the booking scenario on the canvas, the welcome node open in the inspector with its message text and buttons, and the live Telegram preview of the message

Build the dialogue with the mouse: blocks, arrows, separate branches

The inspector prompts you for what to fill in on each block

Live preview: see how the message looks in Telegram

The draft saves itself, undo and redo with the usual keys

A node for every case

The studio palette of node types — messages, media and inputs, logic nodes, AI chat, task and agent, knowledge-base search, HTTP request, script and handoff — beside the canvas with the flow

Messages, media, questions with answer validation and hints

Conditions, variables, pauses, random choice, jumps between branches

AI: dialogue, extracting data from a reply, an agent with tools

Integrations: knowledge base, HTTP requests, your own scripts, handoff

The emulator instead of live Telegram

The Telegram emulator: fake users Alice and Bob in the rail, a finished booking dialogue in the chat, and the conversation panel with the saved phone variable

Test without a real bot, token or internet connection

Fake users: write to the bot as Alice or Bob

A message takes the same path as one from a real person

Failure checks: a delayed reply or a Telegram outage at the touch of a button

Testing and debugging

The test dock: a dry run of the booking flow with the two-step execution trace and per-step timings, awaiting the phone reply on the canvas

Dry run: the bot answers but sends nothing to anyone

Single node run: check one block without walking the whole dialogue

Replay a recorded dialogue: what changed after the scenario edit

Tracing: every step, jump and AI reply with its timing

The inbox: a human takes over the conversation

The operator inbox: the Bot handles list, the Alice conversation with the order lookup, and the client card with tags, session and variables

Handoff from the scenario or by a rule: 3 failed inputs, a keyword

The operator has the whole dialogue history and the client card

Quick replies: a short command expands into ready text

Telegram notification: a message with the handoff summary and a link to the conversation in the inbox

Back to the bot: the dialogue continues from the same place, nothing is lost

The knowledge base

The Knowledge screen with the new-base dialog open: name, chunk size and overlap, and the pinned embedding model — no base is created in the demo yet

Upload documents: text, markup, tables, website pages

Answers from your documents, each with a link to the source

If there is no answer, the bot says so honestly instead of inventing one

Gaps report: what people ask about and the base does not cover

Models and prompts

Model usage: the By model table with zai/glm-4.6 and zai/glm-4.5-air costs and latencies, top spender nodes and the recent calls journal

Your own keys and models: providers compatible with OpenAI

The model is chosen per node, with fallbacks if one fails

Prompts in one place: an edit applies to every bot

Spend tracking: how many tokens and how much money each bot used

Python scripts

The scripts editor: weather.py open, the run panel with the stdin JSON the node delivers, and the run journal with a journaled test run

Your own code in the dialogue: a CRM request, an order check, a calculation

Ten points to plug in: inbound processing, webhook parsing, a custom channel, scheduled jobs

Your own AI provider and custom channels: SMS, email, an in-house gateway

Data comes in and goes out in the clear JSON format

Server settings and secrets are hidden — a script sees only what it is allowed to

Protection from hangs: limits on time, output size and run count

Run journal and the Health screen: every run visible, the environment checked

Contacts, segments and broadcasts

The contacts table with Sam and Alice, and the Segments dialog showing the has phone segment that matches one contact

Everyone who ever wrote to the bot, in one base with their history

Segments: everyone with a phone, those who ordered this month

A broadcast to a segment that respects Telegram limits

Pause and resume: stop sending and continue later

Analytics and logs

The dialogue funnel for the demo bot: welcome, ask_phone, confirm and bye stages with continue rates and drop-off, plus the popular paths

Funnel: where people drop the dialogue and at which step

AI cost per bot and model for the chosen period

Heat map: at which hours people write to the bot

Status: is the bot alive, are there errors, is a queue building up

A chat room on your website

The public chat page in the visitor's browser: the Demo Bot chat with Sam, reply buttons and the saved chats rail — no Telegram needed

A public chat page: visitors talk to the bot without Telegram

Your own bot directory and a short address like /chatroom/help-desk

Anonymous visitors: their dialogues are kept on their own device

Telegram link-up: messenger chats and website chats in one list

A widget on your website

The website widget setup: appearance options beside the live preview with the greeting bubble and the Before we start form with its consent checkbox

One line of code and a chat panel appears on the site

Allow only your own domains: the widget stays hidden elsewhere

A form before the chat and consent to data processing — everything a privacy policy needs

Dialogue rating: the visitor gives a thumbs up or down

Chat with the AI agent

The AI agent chat: a real conversation where the agent runs shell commands, analyses the app and plans fixes — the model picker reads glm-5.3

Connect Xedant Agent and ask for anything in plain words

The Call Agent button right on the bot page

The agent edits the scenario, scripts and bot settings itself

Without the agent everything works except this chat — it is optional

Working without a license

To evaluate the product calmly, request a trial license — the license dialog opens by clicking the license status in the footer of the main screen, and a 30-day trial key is issued on request. Even without a valid license, bots, the studio, the emulator, the knowledge base, operators, the chat room, the widget, broadcasts and analytics work: the license is needed only for the chat with the AI agent. There is no lock-in — the scenario, settings and scripts are stored as plain files and move to another server in full.

Personal license

Every Chatbot Agent feature with no limits for individuals: unlimited installations on any of your computers and servers. $197 one-time payment for a lifetime license. 12 months of free updates, then (optionally) a 50% discount on the next 12 months of updates from the original purchase price. Licensing works offline, and your key is truly lifetime. The matching Xedant Agent license is already included — the Agent is part of the product. The license is needed only for the chat with the AI agent; everything else — bots, the studio, the emulator, the knowledge base, operators, the chat room, the widget and analytics — works without it.

Company license

Every Chatbot Agent feature with no limits for everyone in a company or team, external contractors included. $497 one-time payment for a lifetime license with 12 months of free updates, then (optionally) a 50% discount on the next 12 months of updates from the original purchase price. Licensing works offline, and your key is truly lifetime. The matching Xedant Agent license is already included — the Agent is part of the product. The license is needed only for the chat with the AI agent; everything else works without it.

Service license

Unlimited instances of Chatbot Agent under your domain + the full source code with the right to change it any way you like, update the UI or branding for your company or domain, and integrate it closely with your infrastructure. Any visitor of your domain may use it as part of your services. $970 one-time payment for a lifetime license with 12 months of free updates, then (optionally) a 50% discount on the next 12 months of updates from the original purchase price. Licensing works offline, and your key is truly lifetime. The matching Xedant Agent service license is already included — the Agent is part of the product. The Agent’s source code is available only when you buy the service license for Xedant Agent itself. For smooth upgrades, we recommend changing only the branding and the integration — that keeps the effort of merging new features and fixes to a minimum.

Free licenses

In some cases we are happy to gift a free license:

  • if you found a bug or a security vulnerability in any of our products (we honestly have no budget for a paid bug bounty, unfortunately);
  • if you suggested a sound idea for improving our products (no coding needed — a useful idea is enough; you get a license if we add it to the roadmap);
  • if you are an active contributor to open-source projects (we love open-source — we just have no time to maintain our own products as open-source);
  • if you run a popular blog, Telegram channel or YouTube channel about programming, AI, chatbots, marketing, business or IT in general (no mention or promotion required — it is entirely up to you);
  • if you are an active affiliate partner (sales are not required, but you should have at least some content dedicated to our products).

If any of the above is about you, just write to us on Telegram. Tell us your name and email, and we will generate your personal lifetime license key.