How an order flows through the bot
The guest opens the bot, picks a language and sees the menu by category with photos and prices. Using their location, the bot suggests the nearest branch with its address and opening hours. The guest fills the cart, chooses delivery or pickup and pays with Payme, Click or Uzum without leaving Telegram. The order lands instantly in the kitchen or admin chat, and the guest receives status updates: accepted, cooking, out for delivery. After delivery the bot asks for a rating, and a low score is visible to the manager right away. When a dish runs out, staff mark it in the panel and the bot stops offering it. Regulars collect points and receive offers in the same chat.
What drives the price
Full ordering with a cart, Payme, Click and Uzum payments, an admin panel and broadcasts is the Business level, from $4,000, with order status added as a separate line. If all you need is the menu, answers to common questions about hours and delivery, and orders taken as requests with an alert to staff, the entry Start level costs less and still stops you losing enquiries at peak times. Platform is for chains: bots per branch, CRM handoff and funnel analytics. Loyalty points, surveys, nearest-branch lookup, table booking and voice-to-text can be added to any level. The configurator adds it up, and the price and deadline are fixed in the contract before work starts.
A bot, an aggregator or your own app
Delivery aggregators bring in new guests, but contacts and order history stay on the platform and a commission applies to every order. Your own bot serves the people who already know you: regulars order directly, the customer base and order history stay with you, and a promotion arrives in the same Telegram where guests talk to friends and family. The bot is registered to your Telegram account, so the bot and its users stay with the business. You do not need to leave the aggregators for this; the bot complements them. A dedicated mobile app with a courier on the map and a kitchen display is a separate solution, worth moving to once direct orders grow.
How the work runs
Week one is the menu and the script: categories, add-ons, delivery and pickup terms, and what happens if a guest changes their mind at checkout or a dish runs out. We write the copy in Uzbek and Russian. Then we build on a test bot: staff accept trial orders and the cooks see how an order looks in the kitchen chat. You see a working version every two weeks. Before launch we switch on live payments, run a real card through checkout and train staff on the panel. The timeline from 4 weeks is in the contract; every day of delay cuts the invoice by 2%, up to 10% of the contract. Bugs are fixed free with no time limit.