What drives the price
A bot’s price depends on what happens behind the buttons, not on how many there are. The Start level covers a menu, answers to common questions, lead capture and an instant alert to a manager: enough to stop losing enquiries at night and on weekends. Business adds a catalogue with a cart, payments, an admin panel and broadcasts, so the bot starts selling on its own. Platform is for chains: bots per branch, CRM handoff, funnel analytics and AI that answers from your knowledge base. Bookings, referrals, loyalty points, channel autoposting and voice-to-text can be added to any level. The configurator adds it up and the total goes into the contract.
How the work runs, week by week
Week one is the script. We map every step of the dialogue, including the awkward ones: a voice note, a change of mind at checkout, a typed question instead of a button press. You approve the flow and the copy in every language. Then we build on a test bot that your team uses from their phones as customers would. You get a working version every two weeks, so feedback lands on a live bot, not a document. Before launch we switch on live payments, run a real card through checkout and train managers on the panel. The timeline from 2 weeks is in the contract; every day of delay cuts the invoice by 2%, up to 10% of the contract in total.
Payments, languages and local rails
In markets where Telegram is the everyday messenger, people expect a bot to behave like a good sales assistant: answer in their language and accept the payment method they already use. We build multilingual bots with a language picker on first launch. In Uzbekistan that means Uzbek and Russian, with payments through Payme, Click and Uzum: the customer pays without leaving the chat, gets a receipt, and the order is marked paid automatically. Digital goods sold inside Telegram use Telegram Stars, as Telegram requires. Voice messages can be transcribed to text, which matters wherever customers prefer talking to typing. Orders can flow into Excel, Google Sheets or your CRM.
Where cheap bots break
A bot can be assembled in an evening with a no-code builder or an AI assistant, and at first it may even work. Trouble arrives with real customers. The token sits in public code and a stranger reads your conversations. A payment confirmation is lost because the server answered late, or it is counted twice. The bot runs on someone’s laptop and silently stops replying. The admin panel has no proper login. We keep the token on the server only and process payment retries so a second charge never appears. Bugs are fixed free with no time limit, and your own engineer may audit the code against the contract: any unfulfilled item means a 10% refund.