Telegram Bots for Business in Uzbekistan: Uses, Limits, Integrations and How to Brief a Developer

For many businesses in Uzbekistan, customers write on Telegram before they ever open a website, so a Telegram bot for business looks like the obvious next step. Often it is. But a bot has hard limits that adverts for quick Telegram bot development rarely mention: it cannot write to anyone first, it is rate-limited, and digital goods sold through it can be paid for only in Telegram Stars. This guide is for companies in Tashkent and across Uzbekistan weighing up a bot or a Telegram Mini App. It covers what businesses use bots for, where the platform stops, how a bot connects to your CRM, 1C and payment providers such as Click and Payme, who should own it, and what to put in a brief so that the quotes you receive can be compared.

What businesses in Uzbekistan use Telegram bots for

• Orders from a catalogue. The customer browses categories, fills a cart, chooses delivery or pickup and shares a phone number with a button instead of typing it.
• Bookings and appointments. Clinics, salons and training centres let customers pick a service, a specialist and a time slot, then send a reminder before the visit.
• Lead capture with hand-over. The bot asks the qualifying questions a manager would ask, then passes the conversation to a person with the answers attached.
• FAQ and support. Opening hours, delivery zones, return rules and the questions staff answer over and over, with a clear way to reach a person.
• Order and delivery status. Accepted, dispatched, delivered: updates for customers who have already started the bot.
• Internal staff bots. Approval requests with approve and reject buttons, daily reports from branches, check-ins from field staff with location and photos.
• Mini Apps when the chat gets cramped. A catalogue with filters or a booking calendar is awkward as a sequence of messages. A Telegram Mini App is a web interface that opens inside Telegram from the bot's menu button, an inline button or a direct link.

The lightest option is not a custom bot at all. Telegram Business, offered with Telegram Premium at the time of writing, adds opening hours, location, quick replies, and greeting and away messages to an account. Telegram now also lets any account, with or without Premium, connect a chatbot that answers on its behalf; check the current conditions in the app. For a small team answering the same questions, that can be enough to start.

What a bot can and cannot do

• It cannot start a conversation. A user must message the bot first or add it to a group. A bot cannot write to a list of phone numbers or to people who never started it, so plan the entry points: a QR code at the counter or on the receipt, a link on your website and social accounts, a button after an order is placed.
• In groups it sees little by default. Bots added to groups run in privacy mode by default and see only the commands and messages relevant to them; a bot added as a group admin receives all messages. If a bot must read every message, change that deliberately and tell the members.
• It is rate-limited. Telegram asks bots to avoid more than one message per second in a single chat, allows no more than 20 messages per minute in a group, and limits bulk notifications to about 30 messages per second. Paid broadcasts can lift that limit, but only for bots that meet Telegram's eligibility conditions. Notices to a large customer list therefore go through a queue that retries failures.
• Files are capped. On the cloud Bot API a bot can download files up to 20 MB and send files up to 50 MB. A self-hosted Bot API server raises these limits.
• Digital goods are paid in Stars. Digital goods and services sold in bots and Mini Apps must be paid for exclusively in Telegram Stars. Physical goods and services, such as a delivery or a repair, can use other payment providers.
• Telegram is the interface, not the record. Chat history is not a ledger. Orders, bookings, approvals and their audit trail belong in your own system.
• Users can block a bot. After that it cannot reach them, so a bot should not be the only channel for critical notices such as payment reminders or changed appointments.

Telegram bot, Mini App, website or mobile app

A bot or Mini App is a cheap way to test a workflow with customers who already message you on Telegram: you learn what they order and where they drop off before you build more. A website serves people who search for what you sell and have never heard of you, which a bot cannot do. A mobile app earns its install when people use it often or need device features; see how to build a mobile application. Many businesses need both: a website for search and a bot for existing customers; see web development.

Connecting a Telegram bot to CRM, 1C and Click or Payme payments

CRM. Leads and conversations from the bot should land in the CRM against the client record, not on managers' personal phones, so the history stays when a manager leaves. See CRM development and what a CRM system costs.

1C. Stock and prices come from 1C, and orders go back to it, so nobody retypes them. Decide which system owns each piece of data and what the bot does when an item sells out between two syncs. Our guide to 1C integration with a website and CRM covers the options.

Payments. There are two routes.

1. Telegram Payments API. A payment provider is connected to the bot in BotFather and the bot sends the customer an invoice. Telegram does not process the payment, store card details or take a commission; the provider charges its own fees. Click documents this route, with a test mode and a live mode, and requires the seller to be a legal entity or an individual entrepreneur that has signed a payment-acceptance agreement with one of the banks connected to Click; check the current terms with Click and your bank. A 2017 Telegram announcement also lists Paycom (Payme) as a provider, so check the current provider list in BotFather. Before the customer is charged, the bot must confirm or reject the order within 10 seconds, so stock and price checks have to be fast.
2. A provider's payment page or a Mini App checkout. The customer pays on the provider's own form. Uzum Bank, for example, describes Uzum Checkout as a payment form that can be built into a website, an app or a bot.

Either way, an order is marked as paid only when your server receives the confirmation from Telegram or from the provider, never because a screen on the customer's phone says so. Fiscal receipts are covered in our guide to Click, Payme and Uzum payment integration.

AI answers. A bot that answers free-text questions should answer from your own knowledge base, such as prices, delivery rules and policies, and hand over to a person when it is unsure. See AI development and how businesses can use AI automation.

How a production bot is built

• Webhooks or long polling. Telegram delivers updates either to a webhook on your server or through long polling. The two are mutually exclusive; pick one.
• A backend with a database. Users, orders, bookings and conversations live in your database, not in the chat.
• An admin panel. Staff change the catalogue, prices, texts and opening hours without calling a developer.
• Server-side validation of Mini App data. The initData that Telegram passes to a Mini App is checked on the server with an HMAC-SHA-256 signature based on the bot token, and its auth_date is checked so that old data cannot be reused.
• Conversation state. The bot remembers each user's step, survives a restart, and copes when someone taps an old button or types instead of tapping.
• Logs and alerts. Failed messages, failed syncs and payment errors raise an alert instead of disappearing.
• Languages. Texts in Uzbek (Latin and Cyrillic) and Russian, edited in the admin panel, with the language chosen by the user.
• A maintenance budget. Telegram updates the Bot API regularly, and libraries and integrations need to keep up.

What drives cost and timeline

There is no honest price for "a bot" without a scope. What moves the estimate:

• the number of scenarios and user roles, staff roles included;
• the admin panel and what it must manage;
• how many integrations there are and how good their APIs are;
• payments and fiscalisation;
• custom interface design for a Mini App;
• AI features and the knowledge base behind them;
• the number of languages and scripts;
• whether the catalogue, texts and images are ready;
• third-party onboarding, such as the merchant agreement and API access to your CRM or 1C, which often sets the calendar more than the code does.

After a discovery call we send a quote with scope and milestones.

Who owns the bot

• The bot account. Create the bot from a Telegram account the company controls, or have ownership transferred in BotFather at handover. The transfer is permanent, and the receiving account must have interacted with the bot first, so check BotFather's current requirements in advance.
• The token. Store it as a secret, share it only with people who need direct access, and generate a new one in BotFather if it is exposed or a contractor leaves.
• The code. Keep the source code in the company's own repository from the start.
• Accounts. Hosting and payment merchant accounts are registered in the company's name; the developer is added as a user.
• The data. Agree in writing how users, orders and conversation history can be exported if you change developer.

How to brief a Telegram bot developer: a checklist

• Goal: what the bot should change, and how you will measure success.
• Users: customers, staff, managers and administrators, and what each may do.
• Scenarios: each flow step by step, including errors, cancellations and hand-over.
• Languages: Uzbek Latin, Uzbek Cyrillic, Russian, English.
• Content: who supplies the catalogue, prices, photos and texts.
• Integrations: CRM, 1C and other systems, and who grants access to each.
• Payments: which provider, and whether your merchant agreement is signed.
• Admin panel: what staff must be able to change themselves.
• Notifications: who receives what, and the expected message volumes.
• Data: what is stored, for how long, and who may see it.
• Accounts: who owns the bot, token, repository, hosting and merchant accounts.
• Support: what you expect after launch, and how quickly.

How BITS Technology can help

We build Telegram bots and Mini Apps, with the backend and admin panel behind them, as software development projects. As part of business process automation, approvals and notifications can reach staff on Telegram while the record and audit trail stay in the system. Our AI development work includes assistants on Telegram that answer from your knowledge base and hand over to a person when unsure, and we connect bots to your CRM through CRM development. We deliver source code and documentation. Our team is in Tashkent and works in Uzbek, Russian and English, and after a discovery call we send a quote. The rest of what we do is on our solutions page; if you have a brief, or the start of one, contact us.