Skip to content
Uzbyte
S-06 / AI agents & support bots

AI agents & support bots

At 09:00 there are forty unanswered messages, and half of those people have already bought elsewhere. Now the agent answers at 23:40 too, in Uzbek and Russian.

S-06.1Problem

What it looks like today

Our operator answers Telegram and Instagram from 09:00 to 18:00. Customers write at 21:00, at 23:00, on Sunday. In the morning there are 40 unanswered chats, and half of those people have already bought from someone else.

We tried a chatbot with buttons. People ignore the buttons and write in free text — in Uzbek, in Russian, in a mix, with typos. The bot replies that it did not understand, and the customer leaves. We need something that actually reads and answers.

S-06.2Outcomes

What changes in your business

  1. Answers in correct Uzbek Latin, Russian and English — in the language the customer wrote in, including mixed and misspelled messages

  2. Target: first reply in under 2 minutes, 24/7, on Telegram, WhatsApp and Instagram Direct from one knowledge base

  3. Bookings, order status and price questions handled end-to-end; the agent writes into your CRM, Google Sheets or 1C

  4. Qualified leads passed to a human with a summary: who, what, budget, urgency — not a raw chat log

  5. Escalation rules you set: refunds, complaints and anything the agent is unsure about reach a person within one message

  6. Weekly monitoring report: conversations, resolution rate, unanswered topics to add to the knowledge base

S-06.3How it works

Three steps, in this order.

  1. 01Step 1

    Dialogue audit

    We read your last 200 conversations, list the 20 questions that make up most of the volume, and collect the documents the agent will learn from: price lists, schedules, delivery rules. You approve the tone of voice in all three languages.

  2. 02Step 2

    Pilot in 30 days

    The agent goes live on one channel with a small group of customers: first with a human approving every reply, then on its own. We measure reply time, resolution rate and where it escalates.

  3. 03Step 3

    Run and improve monthly

    Every unanswered question becomes a knowledge-base entry within the week. We add channels, bookings, payments. The monthly fee for hosting, models and monitoring is agreed with you.

S-06.4Deliverables

What you sign off on

  • Dialogue audit: top-20 questions, answer templates, escalation map
  • Knowledge base built from your documents, in UZ/RU/EN, with an owner on your side
  • Live agent on Telegram (plus WhatsApp / Instagram if in scope) with hand-off to a human
  • Tone-of-voice sheet: how the agent greets, apologises and says no, in three languages
  • Integration with your booking calendar, CRM, Google Sheets or 1C (one system in the pilot)
  • Monitoring dashboard: reply time, resolution rate, escalations, cost per conversation
  • AI usage policy + data rules (1 page): what the agent may store and for how long
  • Runbook for your operator: how to correct an answer, pause the agent, export chats
S-06.5Price

What it costs.

By agreement

Exact quote after the free 30-minute audit.

S-06.6Proof

We run what we build.

  • Fact 01

    A Telegram-first product that replaced a 4,000-member chat — the same UX rules for customers of every age apply to every agent we build.

  • Fact 02

    Every lead from this site is summarised and scored by Claude and posted to Telegram; the target is a reply in under 15 minutes in working hours.

  • Fact 03

    57.9% of surveyed Uzbek businesses say they have integrated AI; the barriers they name are finance, compute, talent and data governance (UNDP, February 2026). The knowledge base and data rules address the last two.

S-06.7Questions

Questions we get on the first call.

Will it write real Uzbek, not a calque from Russian?
Yes. We work in Uzbek Latin with the ʻ and ʼ marks and test on real customer messages — mixed Cyrillic and Latin, typos included. The tone-of-voice sheet is reviewed by a native Uzbek editor and by you. Any reply the agent is unsure about goes to a human — the customer never sees an “I did not understand”.
Customers send phone numbers and medical questions. Where is that stored?
Conversations are stored in a database in your account. The model receives only the current conversation, not the whole history. Personal data is minimised and the retention period is set in the data rules — 90 days, for example. For clinics we can limit the agent to booking and scheduling: questions about diagnosis and treatment go to a doctor.
What if the agent says something wrong?
For the first two weeks of the pilot your operator approves every reply. After that a confidence threshold applies: when the agent is unsure it does not answer, it hands over. Every reply is logged and you can correct it in one click — the correction goes into the knowledge base. Refunds, complaints and price negotiation always stay with a person.
We use 1C / Bitrix24 / Google Sheets — can the agent write there and book customers?
Yes. In the pilot we connect one system — usually the booking calendar or the CRM: the agent books the customer, checks a status, updates the record. We connect to 1C read-only for order status and stock. The remaining systems are added on the retainer.
Who owns the bot and the knowledge base?
The bot and channels are registered to your company, you can export the knowledge base at any time, and the code lives in your repository. If you stop, the agent and the data stay with you; we simply lose operator access. The conversation history is yours: only you can read, export or delete it.
S-06.8Next step

Start with the free 30-minute audit.

Five questions, one call. You leave with the workflow to automate first and a cost estimate.

+ a written plan you keep · We answer within 15 minutes in working hours.