Telegram Bot Development — Sales Bots, Mini Apps and Lead Bots

• Web Admin Dashboard +750 000 UZS Manage products and orders via browser Learn more
• In-bot Payment (Click, Payme) +900 000 UZS Accept payments directly inside Telegram Learn more
• Broadcast Newsletter +500 000 UZS Send promo posts to all users with 1 click Learn more
• Google Sheets Sync +450 000 UZS Orders auto-saved in Google Sheets Learn more
• Channel Subscription Gate +250 000 UZS Require channel join before using bot
• Analytics & Stats +400 000 UZS User activity and leads reporting

Prices are in UZS, excluding VAT. The final amount depends on the options you choose and is shown before you place the order.

• The bot's name and @username

  The bot is registered through BotFather under your own Telegram account, so the @username belongs to you. Choose it early: short, readable and close to your business name. The good usernames are taken quickly, and changing one after you have printed it on something is awkward.

• The token, or the right to create it

  The token issued by BotFather is what allows code to act as the bot, and nothing can be built or deployed without it. You can create the bot yourself and send the token over, or give temporary access so it is created for you and still owned by you.

• What the bot is about

  The actual material the bot hands to a user: the list of products or services, the prices, the steps somebody goes through, the questions the bot asks and the answers it should give. The more precise this is, the closer the finished bot lands to what you had in mind.

• Who the admins are

  The Telegram accounts that receive orders and notifications. Name more than one of them. A single admin means every order stops the moment that person's phone is off, and adding another one afterwards is a change on our side rather than something you can click yourself.

• Merchant details for payments

  Only if you chose the payment option. A Payme or Click merchant account has to exist and be approved before the bot can be connected to it, and that approval is between you and the provider rather than something development can speed up, so start it early.

• The channel or group

  Only if you chose the mandatory-subscription option. The channel has to exist already and the bot has to be an administrator in it, otherwise it has no way to check whether a user is subscribed. The same applies to any group the bot is expected to post into.

• A bot is not an app

  Telegram decides what the interface can look like and how large a file can be. A design that needs its own screens, long forms or heavy media does not fit inside a chat, and forcing it produces something worse than either option. That kind of work belongs in a Mini App or an application.

• Forcing a subscription

  Requiring a channel subscription before the bot will answer does raise the channel's numbers, and it does lose you people who only wanted to place an order. Decide honestly which of the two matters more for this particular bot. The requirement can always be added later on.

• Too many buttons

  A menu three levels deep loses people. A bot works when the next step is obvious from the screen the user is already on, which usually means a handful of buttons and short text. Everything that is rarely used can sit behind a single extra entry instead.

• Launching payments untested

  Walk the payment path through yourself with a small real transaction before any customer sees it: pay, receive the confirmation, check the money arrived, then check what happens when a payment is cancelled halfway. A failed first payment costs more trust than the delay of testing ever costs time.

• No server, no bot

  A bot needs a machine that is permanently online. Running it from an office computer or somebody's laptop means it goes silent the moment that machine sleeps or loses its connection, and nobody finds out until a customer complains. Decide where it lives before launch, not after.

• Who sees the data

  Orders, phone numbers and messages have to be stored somewhere and read by somebody. Agree at the start who holds admin access, what is kept and for how long. Rearranging all of that after the bot has been collecting information for months is harder than deciding it now.

• Bot vs mobile app Both live on a phone, but they reach people in different ways and they are capable of different things. Six criteria, no marketing filler.