• Chatbots · LEO Chat

Bot for answering common questions: only what is really in your knowledge base

A bot for answering common questions is the simplest honest kind of chatbot: it answers recurring questions from your knowledge base — delivery terms, availability, sizes, opening hours. Order checkout and payment are not part of this scenario; there is a broader service for them. The key property we put at the center is the boundary: the bot answers only within what it knows and hands over to a person where there is no answer. On a reference set of 45 questions on 4 July 2026 this gave 89.7% accurate answers and not a single invented one outside the knowledge base.

See how it works
Price
after a free audit
Guarantee
30 days after project sign-off
Accuracy
89.7% on a reference set of 45 questions
after a free audit
Price
Guarantee

days after project sign-off

Accuracy

on a reference set of 45 questions

Answers outside the knowledge base

of 45

Telegram and a website widget
Channels
free review of the task
Start
What's included

Complete list of work and what you get as a result

  • a knowledge base with your common questions and answers — terms, opening hours, delivery, returns
  • checking the bot on real questions before launch, not only on test ones
  • handing the enquiry to a live person where the base has no answer
  • connection to Telegram and the website widget, sharing one knowledge base
  • instructions on how to add to the knowledge base yourself after launch
  • a 30-calendar-day warranty 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

  • order checkout in the chat — there is a separate service with a broader scenario for that
  • payment in the dialogue — this bot only answers, it does not lead to a cart
  • demand generation or advertising — the bot answers those who have already written
Who it's for

Situations where this service delivers results

Scenario 1 of 3

Most enquiries are the same three to five questions

Opening hours, delivery terms, how to return an item — typical support spends most of its time on this.

We'll review your situation in a free audit

Free review: which questions will make up the knowledge base

We look at real enquiries over the last month and pick out the recurring ones — they are what goes into the bot's knowledge base.

What we measure

  • Common questionswhich enquiries recur most often
  • Source of answerswhether there is already a ready FAQ or documentation to take the facts from
  • Volume of enquirieshow many common questions a day a person handles now

What you get

  • a written list of questions for the knowledge base
  • an estimate of the share of enquiries the bot will handle

Timeline: 1–3 working days

Why is it free

The size of the knowledge base and the cost depend on the number and complexity of the common questions — 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

Trusted by: Kvant Energy, GYPSUN, Naturel Cosmetics, Pancer Protection, LUGI, BeeTech

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

  • Number of topics in the knowledge basefive common questions and fifty mean different amounts of work on the wording
  • Source of factsa ready FAQ or documentation is cheaper than collecting answers from scratch by interviewing your team
  • Number of channelsTelegram only, or Telegram and the website widget together
  • How varied the wording of questions iscustomers ask the same question in different ways — this affects how much checking is needed before launch
Cases

Tasks and results in numbers — all metrics measured by us

LEO Chat

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

Task
Answer common questions accurately and not make things up where the answer is not in the knowledge base.
Solution
A knowledge base with the store's facts, a check against a reference question set before launch, handing complex enquiries to an operator.
Result
89.7% accurate answers on a reference set of 45 questions, 0 answers outside the knowledge base (measured 4 July 2026).

Did not find your case?

Describe how it works on your side — we will tell you whether “Bot for answering common questions” 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

  1. Reviewing the task

    1–3 days

    We collect common questions from real enquiries over the last month and set the line between “the bot answers” and “it hands over to a person”.

  2. Knowledge base

    3–5 days

    We write the answers based on company facts and check them against the real wording of customer questions.

  3. Testing

    2–4 days

    A run on the reference question set, checking that the bot does not make things up where there is no answer.

  4. Launch

    1–3 days

    Connecting the channels, instructions for your staff member on how to add to the knowledge base on their own after launch.

Technologies & integrations

What we build on and what it connects to

Stack

  • LEO Chat — the agency's own product
  • a knowledge base built on company facts
  • Telegram Bot API and a JS widget

Integrations

  • Telegram
  • website widget
  • handing enquiries to an operator
A knowledge-base bot versus a static FAQ page

How this option differs from the alternative

A question phrased in the customer's own wordsthe bot finds the right fact even when the customer's words do not match the section heading
A question the base does not coverthe enquiry goes to a person; on the reference 45 questions on 4 July 2026 not a single answer outside the knowledge base
Updating an answeryou edit the knowledge base once — the text is the same in Telegram and in the widget
You can see what is missinga list of unanswered questions builds up by itself and shows what to add to the base
What we need from you

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

  1. common questions from the last month — examples of real customer enquiries
  2. a ready FAQ or documentation, if you have one
  3. a person responsible for enquiries outside the knowledge base
  4. approval of which company facts may be shown publicly

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 is this bot different from a bot that takes orders?

This bot only answers common questions — about opening hours, delivery, return terms — and does not lead to a cart or payment. If you need order checkout in the chat, that is a separate service with a broader scenario.

What happens if a customer asks something outside the knowledge base?

The bot does not make up an answer — it passes the enquiry to a person. On the reference set of 45 questions (4 July 2026) there was not a single answer outside the knowledge base.

Can we add to the knowledge base ourselves after launch?

Yes, together with the launch we hand over instructions on how to add new questions and answers without us.

How many common questions does such a bot usually handle?

It depends on the niche and the volume of enquiries — the exact figure comes from the free review of your real enquiries over the last month.

Do we need a ready FAQ to launch the bot?

No. It speeds up the work, but the knowledge base can also be built from scratch — from real customer enquiries over the recent period.

Can this bot be connected to full order checkout later?

Yes, the knowledge base we build now becomes the foundation for a broader scenario with a cart and payment, if you need it later.

How long does the launch take?

7–15 days as the sum of the stages: 1–3 days reviewing enquiries, 3–5 days knowledge base, 2–4 days testing on the reference question set, 1–3 days launch and handing over the instructions. Warranty: 30 calendar days from the date the acceptance act is signed; we reply to requests within 2 hours.

Let's see which questions will go into your knowledge base

We will go through real enquiries from the last month and tell you what share of them the bot will handle. The review is free, we reply within 2 hours.

From measured cases89.7% accurate answers on a reference set of 45 questions, 0 answers outside the knowledge base (measured 4 July 2026)

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.