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.
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 auditYou do not always need the whole in-chat ordering feature set — sometimes it is enough to handle simple recurring questions.
A bot that makes things up where it does not know harms trust more than a plain silent form — here this boundary is built in technically.
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.
Timeline: 1–3 working days
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.
After that — an estimate broken down by stage and a contract with a fixed amount.
Contract, act and invoice — for every project, not just large ones.
Trusted by: Kvant Energy, GYPSUN, Naturel Cosmetics, Pancer Protection, LUGI, BeeTech
Every project gets a written contract: scope, deadlines, amount, acceptance procedure. After delivery — act and invoice, then 30 calendar days of warranty.
The contractor is a registered sole proprietor. Payment by invoice with closing documents.
Code, design and materials transfer to you after full payment. Domain, hosting, repository and analytics are registered to you.
During the project you get access to a portal: contracts, invoices, acts and project status in one place.
Our sites run in nine countries: besides Ukraine — Poland, Germany, Austria, England, Norway, Bulgaria, Moldova and Spain.
Every case in the portfolio comes with a link to a live site and a technical measurement.
There is no price list on the site intentionally: the scope of the same work differs multiples between clients.
If the task isn't ours or the deadline is unrealistic — we tell you upfront.
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.
Sole proprietor & bank transfer
The contractor is a registered sole proprietor. Payment by invoice with closing documents.
Rights & access — yours
Code, design and materials transfer to you after full payment. Domain, hosting, repository and analytics are registered to you.
Client portal instead of email chains
During the project you get access to a portal: contracts, invoices, acts and project status in one place.
Sites in nine countries
Our sites run in nine countries: besides Ukraine — Poland, Germany, Austria, England, Norway, Bulgaria, Moldova and Spain.
Verifiable numbers
Every case in the portfolio comes with a link to a live site and a technical measurement.
Audit first, then pricing
There is no price list on the site intentionally: the scope of the same work differs multiples between clients.
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.
LEO Chat — the agency's own chat-commerce product
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.
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”.
We write the answers based on company facts and check them against the real wording of customer questions.
A run on the reference question set, checking that the bot does not make things up where there is no answer.
Connecting the channels, instructions for your staff member on how to add to the knowledge base on their own after launch.
| Static FAQ page | Our approach | |
|---|---|---|
| A question phrased in the customer's own words | the visitor scans the page and closes the tab without seeing their own wording | the bot finds the right fact even when the customer's words do not match the section heading |
| A question the base does not cover | the page stays silent, and the question is lost along with the customer | the enquiry goes to a person; on the reference 45 questions on 4 July 2026 not a single answer outside the knowledge base |
| Updating an answer | you edit the page layout, while the messengers keep the old answer | you edit the knowledge base once — the text is the same in Telegram and in the widget |
| You can see what is missing | you learn about the gap from a disappointed customer's email | a list of unanswered questions builds up by itself and shows what to add to the base |
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.
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.
Yes, together with the launch we hand over instructions on how to add new questions and answers without us.
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.
No. It speeds up the work, but the knowledge base can also be built from scratch — from real customer enquiries over the recent period.
Yes, the knowledge base we build now becomes the foundation for a broader scenario with a cart and payment, if you need it later.
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.
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)
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.