• Chatbots · LEO Chat

Chatbot for an online store: from a product question to a confirmed order

A chatbot for an online store takes the buyer from a product question to a placed order without a manager: it answers from your catalog, shows price and availability, builds the cart and passes it on to checkout with Nova Poshta delivery — all in one conversation. Launch takes 9–22 days as the sum of the stages. The limit is the same as for any chatbot: it only answers within what it knows — your catalog and knowledge base — and hands anything complex or unusual to a person. We built this for ourselves: LEO Chat sits in the corner of this page, and the figures below are measurements of the product itself on the stated dates; they don't describe the business results of any particular store.

See how it works
Price
after a free audit
Guarantee
30 days after project sign-off
What it does
catalog answer → cart → checkout in one chat
Price
after a free audit
Guarantee
30
days after project sign-off
What it does
catalog answer → cart → checkout in one chat
Channels
Telegram and a website widget
Answer accuracy
89.7%
on the 45 reference questions
Timeline
9–22
days from the catalog review to a working bot
Start
a free review of your task
What's included

Complete list of work and what you get as a result

  • connection to your product feed or catalog — the bot answers from real data, not from an invented description
  • conversation flow: product question → clarification → cart → Nova Poshta delivery → confirmation
  • payment in the chat through your own merchant account (by card or cash on delivery) — without going to a third-party site
  • handing a complex request to a live manager in the same chat, without breaking the conversation
  • an attribution report: which orders were paid after a conversation with the bot — this is a last-touch model within a configured window; it doesn't prove the order wouldn't have happened without the bot
  • connecting the Telegram channel and the website widget to a single data source
  • instructions for your manager: how to view the conversation history and take over a conversation
  • 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

  • writing the product descriptions themselves — if the catalog needs rewriting, that's separate work (AI rewriting of descriptions)
  • Instagram and WhatsApp channels — only Telegram and the website widget are supported now
  • demand generation or advertising — the bot answers people who have already written in; it doesn't bring in new buyers
  • replacing your CRM: requests go into your system by webhook rather than living only in the bot
  • legal responsibility for answers outside the knowledge base — the bot hands such questions to a person instead of making things up
Who it's for

Situations where this service delivers results

Scenario 1 of 4

The manager answers the same questions over and over

Availability, size, delivery time — dozens of identical messages a day eat up time that could go to complex orders.

We'll review your situation in a free audit
Free audit

Free review: is your catalog enough for a bot

Before estimating we look at the catalog structure and buyers' typical inquiries — often half of the manager's load is covered by basic answers from the catalog, not by complex AI.

What we measure

  1. Catalog formatwhether there's a Horoshop, Prom.ua or CSV feed, or the catalog will have to be read by a scanner of the site's microdata
  2. Typical inquirieswhich questions come up most often — they are what goes into the bot's knowledge base
  3. Payment and deliverywhich payment and delivery methods are already connected on the site
  4. Volumehow many inquiries a day the manager currently handles by hand

What you get

  • a written review of how ready the catalog is
  • a list of the inquiries the bot will handle and those that stay with a person

Timeline: 1–3 working days

Why is it free

The cost depends on the size of the catalog and the number of integrations — without a review any figure would be invention.

What's next

Then an estimate broken down by stage and a contract with a fixed amount.

Short form: your contact and site URL
Contract and paperwork

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

  • 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.

  • 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.

What affects the price

Why two seemingly identical tasks are priced differently

  • Catalog sizemore items — a longer knowledge base and more attention to data quality
  • Number of channelsTelegram and the widget together cost more than one channel
  • Checkout complexitya simple confirmation or a full cart with payment — different amounts of work
  • Catalog conditiona clean feed costs less than a catalog that first has to be put in order
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 conversation going from a product question to a placed order without losing the buyer in the pause between messages and without made-up answers outside the catalog.
Solution
The bot in Telegram and in the site widget answers from the catalog knowledge base, manages the cart, arranges Nova Poshta delivery and takes payment through the store's own merchant account; anything not in the knowledge base goes to an operator.
Result
89.7% accurate answers on a reference set of 45 questions and not a single answer outside the knowledge base (4 July 2026); 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; 0.21 s — time to first response of the LEO Chat landing page at 153 KB of HTML (7 September 2026, external curl measurement from Ukraine).

Did not find your case?

Describe how it works on your side — we will tell you whether “Chatbot for an online store” 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. Task review

    1–3 days

    We analyze the catalog and typical inquiries and set the line between “the bot answers” and “it hands over to a person”.

  2. Knowledge base

    3–7 days

    We connect the catalog as the source of answers and test it on real questions.

  3. Order flow

    3–7 days

    Cart, delivery and payment in the conversation — through your own merchant account and your own delivery-service account.

  4. Launch and training

    2–5 days

    Connecting the channels, handing complex requests to a person, and instructions for your manager on how to view the conversation history and take over a conversation manually when needed.

Technologies & integrations

What we build on and what it connects to

Stack

  • LEO Chat — the agency's own product, Telegram Bot API and a website widget
  • catalog source: a Horoshop, Prom.ua or CSV feed on a schedule, or a scanner of the site's microdata
  • webhooks into the CRM to pass on requests
  • the store's own merchant account (Monobank, LiqPay, cash on delivery) — no gateway of our own

Integrations

  • Horoshop, Prom.ua, a CSV feed and a scanner of the site's microdata as catalog sources
  • Nova Poshta for arranging delivery in the chat
  • payment systems through the store's own merchant account
  • CRM via webhook
A bot versus a manager on the same routine questions

How this option differs from the alternative

A live managerOur approach
Response timeduring working hours, in the message queueinstantly, at any time
Catalog accuracydepends on the person's memory and attentionverified data only, 89.7% accurate on the reference set
Complex questionhandled by a person straight awayhanded to a person with the context intact
Workloadquality drops towards the end of the daydoesn't get tired or mix up models at the end of a shift
What we need from you

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

  1. a product feed or access to the catalog (Horoshop, Prom.ua, CSV — or site pages with product microdata)
  2. buyers' typical inquiries — examples of real questions from the last month
  3. the delivery and payment details already connected on the site
  4. a responsible person on your side who takes over complex requests
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

Can a customer order entirely in the chat, without going to the website?

Yes — the bot shows the product, builds the cart, arranges Nova Poshta delivery and takes payment through the store's own merchant account right in the conversation. Harder cases (an individual price, a disputed return) are still closed by a person.

What does the bot say when it doesn't know the exact answer?

It hands the conversation to an operator with the context intact instead of making things up. On a reference set of 45 questions (4 July 2026) the bot gave 89.7% accurate answers and not a single answer outside the knowledge base.

Which channels are supported now?

Telegram and a widget on the website. Instagram and Viber are on the product roadmap, so if your store's main channel is Instagram, this solution won't fit yet.

Do product descriptions have to be rewritten for the bot?

No, the bot works with the catalog you already have. If the descriptions need updating for better answers, that's separate work (AI rewriting of descriptions), not a precondition for launch.

How do requests from the chat get into our CRM?

By webhook and through the public API — without native integration with specific CRMs (KeyCRM, SalesDrive and others are on the product roadmap, not a current feature).

How long does the launch take?

9–22 days as the sum of the stages: 1–3 days for the catalog review, 3–7 days for the knowledge base, 3–7 days for the order flow, 2–5 days for launch and training your manager. The warranty is 30 calendar days from the date the acceptance act is signed; we reply to requests within 2 hours.

Does the bot work with a store on Horoshop?

Yes, the bot takes the catalog from the Horoshop feed on a schedule — it's one of LEO Chat's sources alongside Prom.ua, CSV and a scanner of the site's microdata. It answers from that feed, so a new price or stock status shows up in the bot after the next update, not instantly. For chat orders to also appear in the Horoshop admin panel, the platform's API is needed — we check separately at the start whether your plan includes it.

Let's see whether your catalog is enough for a bot

We'll go through the catalog structure and typical inquiries and tell you honestly what the bot will handle and what stays with the manager. The review is free, and 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.