A Telegram bot for a business in Tashkent takes requests and bookings, answers routine questions and hands the data over to a CRM, while the company pays once for development and then every month — for the server and for changes. A bot that collects requests and bookings starts at $1,200, and a process review with an automation plan but no development costs $400.
Key takeaways
The bot takes over repeat enquiries: booking a slot, checking a price or availability, tracking an order, receiving a ticket or a document. A member of staff steps in only where a human decision is needed, not where the same information has to be repeated.
It helps to agree on the limits before the quote. The bot does not sell a complex service in place of a manager, does not replace the website where people study the company before buying, and messages first only those who started it themselves. Those messages to its own users are free by default (Telegram Bots FAQ).
The budget follows the type of task rather than the number of buttons, which is why the price list has four separate lines and the bot is only one of them.
The scope behind each line is on the AI and automation service page. The lower bound buys a working bot with a scenario, request handling and filing into the customer database, not a demo dialogue. Above it, the price grows with the number of scenarios and external systems.
The difference between a form bot and a bot that holds orders and payments is not in the styling but in the number of places where the bot is tied into the business. Quotes are compared along exactly these lines.
| What we compare | Form bot | Requests and bookings bot | Bot with catalogue and payment |
|---|---|---|---|
| Scenario | One path, 3–5 questions | Branching: service, specialist, time | Catalogue, cart, delivery, payment |
| Where requests end up | Manager’s chat or a spreadsheet | CRM with a source tag | CRM and accounting system, stock write-off |
| Roles and rights | None, everyone sees everything | Manager and administrator | Manager, warehouse, accounting |
| Payment | No | Sometimes a prepayment | Yes, through a payment provider |
| Who edits texts and prices | A developer, in the code | An administrator, in the admin panel | The accounting system over an API |
| What pushes the price up | Number of questions | Branches and CRM exchange | Payment, stock, refunds |
Moving between levels costs more than it looks: a form bot with texts in the code does not become a booking bot by adding one button, because it has neither an admin panel nor stored dialogue state. If bookings and payments are on your roadmap for the next six months, it is cheaper to design for them from the start.
The price is driven not by buttons or styling but by the places where the bot touches money, documents and other systems. The order is roughly this.
The platform does not invoice you for a bot: it sends messages to its own users for free. What you pay for is the server, bulk broadcasts above the free limit and the acceptance of money.
Two more limits matter for reminders: a bot sends no more than one message per second to a single chat and no more than 20 messages per minute to a group (Telegram Bots FAQ). An evening broadcast across the base is therefore designed as a queue rather than a single “send to everyone” button, and that queue is part of the work too.
Once handed over, the bot becomes an ordinary working system: it lives on a server, its scenarios change along with your services, and money flows through a provider. That is what the monthly bill is made of, and prices for infrastructure and for keeping an eye on it are on the services pages.
Where the server stands is a separate question. Biometric and genetic data, along with data on subscribers of telecom operators, must be stored inside Uzbekistan — this is set by article 27-1 of the Law on Personal Data No. ZRU-547. A customer’s name and phone number are not on that list, yet the law requires them to be protected in any case, so the hosting choice is weighed together with speed and backups: how to make that calculation is covered in the article on cloud or a server in Uzbekistan.
What usually differs is not the hourly rate but the scope: a cheap offer describes the dialogue, a full one also describes what the company is left with after launch.
A short quote normally has no admin panel: texts, services and schedules are hard-coded, and every edit turns into a developer task again. It has no exchange with the customer database — requests stay in a chat, and a month later nobody can say how many there were and how many reached payment. It has no handling of malformed input, so the bot trips over the first person who writes a phone number in words.
The second part of the gap is ownership. The bot is created in @BotFather from the company’s account, the code and the dialogue history stay on its server, and under our contract the rights to the code pass to the client after full payment. If none of that is in the quote, the company is paying for a system it does not own.
Mistake A bot created in the personal account of a contractor or of an employee who has since left cannot be moved without access to that account: subscribers and message history go with it.
A quote has to show the scenario, the list of external systems, the server, the rights to the code and the line between the project and later changes — only then are offers comparable. Collect these points and give them to every contractor in the same form.
The last point looks like the least technical one, yet it decides more than the rest: a request nobody answers costs the company more than the money saved on development.
Syntra Systems starts not with a price but with a review of enquiries: we look at what the flow of messages and calls consists of and work out which part can be closed without a member of staff. That produces a scenario, and the scenario produces a quote by line: dialogue, exchange with systems, payment, admin panel, support. It is then visible what exactly the company is paying for and what can wait for a second stage.
If it is unclear where to start, the process review and automation plan is a separate piece of work at $400: after it the company has a prioritised list of tasks with a budget for each, and it can be followed with us or in-house. How the development itself is organised is covered in the article on Telegram bot development for business, and the link between a bot and the customer database in the article on Telegram bot integration with a CRM.
Let’s discuss your project
Tell us what you need, and we will estimate the timeline and cost and suggest a solution.
No, the platform charges nothing: by default a bot sends messages to its own users for free. A bill appears only for bulk broadcasts above 30 messages per second, where paid broadcasting applies at 0.1 Stars per message. The remaining costs are the server, support and the payment provider’s commission.
On the development side it is separate work — the invoice, the pre-checkout step, refunds and receipts. The contract with the provider is signed by the company itself, and the commission comes out of its turnover: with Click that is 1.5–2.5 % on Uzcard and Humo cards for an online integration.
Because the short offer has no admin panel, no exchange with the customer database and no handling of malformed input, and sometimes no rights to the code either. The dialogue looks identical in both quotes, but one leaves the company with a system it can change itself and the other with a conversation it pays a developer to edit.
Yes, and that is the usual route: first the request and booking scenario with filing into a CRM, then payments, a storefront and roles. The one condition is that the boundaries between stages are visible in the quote, otherwise second-stage work quietly turns into “extras”.
While the server is paid for, the bot keeps answering along the old scenario. The trouble starts with the first change in the business: a new service, a different price, a change of payment provider or of platform rules — somebody has to enter all of that, and without support those edits turn into a project of their own.
Under article 27-1 of the Law on Personal Data No. ZRU-547, only biometric and genetic data and data on subscribers of telecom operators must be stored inside the country. A customer’s name and phone number are not on that list, so the hosting is chosen by speed, backups and price — while the data has to be protected either way.
That is the base line of the price list: a bot for requests and bookings with filing into a CRM starts at $1,200. The price moves above that lower bound once there is more than one system involved: 1C, telephony, a warehouse or a payment provider are counted separately.
Sources
Cover photo: Je Hwan Lee, Pexels