Chatbots · LEO Chat

Telegram chatbot: the channel your buyer is already in, no trip to the website

A Telegram chatbot continues the conversation where the buyer has already written: in the store's channel, in a group, or directly to the bot. Unlike a website widget, the person doesn't need to open a page — they simply write in Telegram and get an answer from the catalog, a cart and checkout. We built this channel for our own product LEO Chat and run it in production: the Telegram Bot API and a message queue with retries, which we checked with a chaos test on 17 August 2026 on a test stack.

See how it works

Price: after a free audit
Guarantee: 30 days after project sign-off
Channel: Telegram Bot API

after a free audit
Price
Guarantee: Telegram Bot API
Channel
Reliability
Accuracy
Timeline: free review of the task
Start

What's included

Complete list of work and what you get as a result

connecting the bot to the Telegram Bot API under your account
the same catalog knowledge base as on the website — answers don't diverge between channels
checkout and payment in the chat through your own payment provider account
handing a complex request to an operator without losing the conversation history
a message queue with retries and deduplication — the same one checked with a chaos test on 17 August 2026 on a test stack: not a single confirmed message was lost or duplicated
a warranty of 30 calendar days from the date the acceptance act is signed

When this service isn't right

What's not included — so there are no surprises at delivery

Instagram, Viber, WhatsApp — these are separate channels, not currently supported by the product
running marketing campaigns and advertising in Telegram — the product has segmented broadcasts, but you launch them yourselves; they are not part of this service
administering your Telegram channel or group — the bot works as a separate bot account

Who it's for

Situations where this service delivers results

Scenario 1 of 3

Your audience is already in Telegram

Orders already come through a Telegram group or channel, but a person handles them manually — the bot takes over the typical requests.

We'll review your situation in a free audit

Free review: is your Telegram ready for a bot

We look at where Telegram requests come from now and how many of them are typical — often these are exactly what take up most of a manager's time.

What we measure

Source of requestsa channel, a group, or direct messages to the bot
Typical questionswhich requests repeat most often
Placing an orderhow a purchase is confirmed in Telegram now

What you get

a written review of the channel's readiness
a list of the requests the bot will handle

Timeline: 1–3 working days

Why is it free

The cost depends on the volume of requests and the complexity of the flow — without a review any figure would be guesswork.

What's next

After that — an estimate broken down by stage and a contract with a fixed amount.

Short form: your contact and site URL

We work officially

Contract, act and invoice — for every project, not just large ones.

Trusted by6 brands

Terms fixed in writing8 points

01
Contract, act and 30-day warranty
Every project gets a written contract: scope, deadlines, amount, acceptance procedure. After delivery — act and invoice, then 30 calendar days of warranty.
02
Sole proprietor & bank transfer
The contractor is a registered sole proprietor. Payment by invoice with closing documents.
03
Rights & access — yours
Code, design and materials transfer to you after full payment. Domain, hosting, repository and analytics are registered to you.
04
Client portal instead of email chains
During the project you get access to a portal: contracts, invoices, acts and project status in one place.
05
Sites in nine countries
Our sites run in nine countries: besides Ukraine — Poland, Germany, Austria, England, Norway, Bulgaria, Moldova and Spain.
06
Verifiable numbers
Every case in the portfolio comes with a link to a live site and a technical measurement.
07
Audit first, then pricing
There is no price list on the site intentionally: the scope of the same work differs multiples between clients.
08
We say "no" when unsure
If the task isn't ours or the deadline is unrealistic — we tell you upfront.

01
Contract, act and 30-day warranty
Every project gets a written contract: scope, deadlines, amount, acceptance procedure. After delivery — act and invoice, then 30 calendar days of warranty.
02
Sole proprietor & bank transfer
The contractor is a registered sole proprietor. Payment by invoice with closing documents.
03
Rights & access — yours
Code, design and materials transfer to you after full payment. Domain, hosting, repository and analytics are registered to you.
04
Client portal instead of email chains
During the project you get access to a portal: contracts, invoices, acts and project status in one place.
05
Sites in nine countries
Our sites run in nine countries: besides Ukraine — Poland, Germany, Austria, England, Norway, Bulgaria, Moldova and Spain.
06
Verifiable numbers
Every case in the portfolio comes with a link to a live site and a technical measurement.
07
Audit first, then pricing
There is no price list on the site intentionally: the scope of the same work differs multiples between clients.
08
We say "no" when unsure
If the task isn't ours or the deadline is unrealistic — we tell you upfront.

We sign NDAs on request. After completing the work, we delete our access to your services ourselves.

What affects the price

Why two seemingly identical tasks are priced differently

Complexity of the checkout flowa simple confirmation or a full cart with payment — a different scope of work
Volume of requestsmore messages a day means higher demands on the reliability of the queue and retries
Number of channels at onceTelegram only, or Telegram and the website widget together — a different price because of the shared knowledge base
State of your existing Telegram channela ready bot account with history costs less than launching from scratch

Cases

Tasks and results in numbers — all metrics measured by us

LEO Chat

LEO Chat — the agency's own chat-commerce product

Task: Keep the Telegram channel available at any time, with no lost or duplicated confirmations even under a load spike.
Solution: A bot on the Telegram Bot API with a message queue and retries; it answers from the catalog knowledge base and leads the buyer to checkout.
Result: 0 lost and 0 duplicated confirmed messages in a chaos test at 300 messages per second with the engine, NATS and Redis forcibly killed (17 August 2026) — a load test on a test stack, not in production; 89.7% accurate answers on a benchmark set of 45 questions and not a single answer outside the knowledge base (4 July 2026).

Did not find your case?

Describe how it works on your side — we will tell you whether “Telegram chatbot” fits and what it means in your situation. No brief and no call: one question, one answer.

Process steps

Transparent stages with approval at every step

Task review
1–3 days
We analyze typical requests in the Telegram channel or group and set the line between “the bot answers” and “the bot hands over to a person”.
Connecting the bot
3–5 days
We register the bot via the Telegram Bot API, connect the catalog knowledge base, and check it on test conversations.
Ordering flow
3–5 days
Cart, delivery by Nova Poshta, payment initiated in the chat through your own payment provider account.
Launch
1–3 days
Handing complex requests to an operator without losing the conversation history, instructions for your staff member.

Technologies & integrations

What we build on and what it connects to

Stack

LEO Chat — the agency's own product
Telegram Bot API
a message queue with retries; in the chaos test on 17 August 2026 confirmed messages were neither lost nor duplicated

Integrations

Nova Poshta for arranging delivery
the store's own payment provider account
CRM via webhook

What we need from you

We can't start without this — best to prepare in advance

the ability to create a Telegram bot under your account (a token via @BotFather)
typical requests from your existing channel or group for the last month
payment and shipping details — the same ones the store already uses, if you have a website
a responsible person who takes over complex requests in the chat

If something is missing — let us know, we'll help you gather it or do it as a separate task.

FAQ

Most frequently asked questions — with concrete answers

How does a Telegram bot differ from the widget on the website?

The knowledge base and ordering flow are the same, but the form of the conversation differs: in the website widget it is a step-by-step wizard with voice input, in Telegram it is a conversational mode. The main difference for the buyer: there is no need to go to the website — they write where they already are.

Will the bot cope with a surge of requests, say during a sale?

The chaos test on 17 August 2026 loaded the stack with 300 messages per second and forcibly killed the engine, the NATS queue and Redis — 0 lost and 0 duplicated confirmed messages. This is a load test on a test stack, not in production; it doesn't replace production monitoring, but it gives a sense of the level of reliability.

Can we have a bot in Telegram and on the website at the same time?

Yes, both channels read the same catalog knowledge base, so answers don't diverge between them — the buyer gets the same information whichever channel they use.

Does the bot send messages on its own, without the buyer asking?

On its own initiative, no: in a conversation it answers those who wrote. Segmented broadcasts exist in the product as a separate feature, and the store launches them deliberately, within Telegram's limits; revenue from a campaign appears in the report under a last-touch model within the configured window — this is attribution, not accounting. Within this service we set up a bot that answers; we do not run marketing campaigns — that is separate work.

What do you need from us to launch a Telegram bot?

A bot token via @BotFather, access to the product catalog, and examples of real requests from the last month — the knowledge base is built from them.

How long does it take to launch a Telegram bot?

8–16 days in total across all stages: 1–3 days reviewing requests, 3–5 days connecting the bot and knowledge base, 3–5 days on the ordering flow, 1–3 days launch. Warranty — 30 calendar days from the date the acceptance act is signed; we reply to requests within 2 hours.

Let us see whether your Telegram channel is ready for a bot

We will go through your typical requests and say what the bot will handle. The review is free, we reply within 2 hours.

View cases

Reply within 2 hours
No commitment
We work under a contract

There is no price list on the site on purpose: the same work differs several times over between two clients, and a “from” figure explains nothing in that case. First a free audit — we count your pages, duplicates and speed — then we name the sum and the deadline and fix both in the contract.