Telegram bots & Mini Apps

Your customers already live in Telegram — so they order, book and pay right there, without installing anything. From the smallest automation to a full storefront, inside a bot or Mini App.

← All services

Who it is for

Shops and Uzum sellers whose catalogue lives in a Telegram channel and whose orders arrive as voice messages
Clinics, salons and training centres that book by phone and lose no-shows in silence
Cafés, delivery and subscription services that take payment by card-transfer screenshot
Football schools, kindergartens and language centres that still send parents the schedule, attendance and invoices by hand
Any business whose customer conversation already happens in a chat that has stopped coping with growth

Problem

Our whole shop is a Telegram channel: 300 posts with prices, and customers write "is this still available?" under a photo from March.

Your Telegram

✓ 13:05 · arrived

Order paid right in Telegram. Nothing to install.

What it looks like today

The manager answers by voice message, writes the order in a notebook, asks for a card-transfer screenshot and then hunts for it in the bank app. On a good day we lose two orders; on Uzum the same goods sell in two taps.

We keep being told to build a separate app, while our customers already have Telegram open twelve hours a day. They will not download, register and remember a password. What we need is not an app: it is a place inside the chat where the order is finished, the payment is taken and all of it is written down.

What changes in your business

A Telegram Mini App customers open from your own channel: catalogue, cart, booking or subscription — no install, no new login
Payme and Click built in: the order is paid before a manager sees it, and the receipt lands in the same chat
Every order, booking and payment in one database with an admin panel — "who paid?" becomes a filter instead of phone calls
A reminder bot: a nudge the day before a booking, order status, unpaid-invoice reminders
An interface written properly in Uzbek (Latin) and Russian — chosen once and remembered
Tested on the oldest phone we can find: big buttons, one question per screen, works on a weak connection

Three steps, in this order.

Step 1
We pick one flow
We read a week of your chat and find the most repeated question: is it available, how much, can I book. The first project has to nail that one flow. The rest comes later, once the first one works.
Step 2
We build and connect payments
We build the Mini App on your real catalogue and prices: Payme and Click in test mode first, then live payments. Then we measure with real customers: orders through the app versus the chat, time from post to paid, no-shows. You launch to your own channel, not to an empty store.
Step 3
Scale
Once the numbers hold, we add the next flow — loyalty, subscriptions, a parent portal, sync with your accounting program — keep the app monitored and hand over the code as we go. The app keeps running if you stop.

What you sign off on

A process map and a module breakdown: what gets built, and in what order
The Telegram bot or mini app itself — whichever fits how your customers buy
Integrations with the systems you already use, as far as those systems allow
Documentation and user instructions in plain language
Training for each role on your team

The price depends on the type of application: web, desktop or mobile.

Less than the problem costs you — or we tell you straight.

By agreement

We count what this costs you now — hours, missed customers, errors. The quote comes after, set against that number. The final price is agreed individually with each client.

Questions we get in the first chat.

What is the difference between a Mini App and a plain bot?

A bot is a conversation: question, answer, buttons. A Mini App is a screen that opens inside that same chat: catalogue, cart, calendar, payment. For simple scenarios a bot is enough and costs less; when people need to choose, filter or pay, you need a screen. Most often they work together: the bot notifies, the Mini App does the work. Write to us on Telegram and we'll tell you which is enough.

Where are our customers' data and payments stored?

Card details never reach us: Payme and Click handle the payment on their side and send us a confirmation, and that is all we keep. Orders, names and phone numbers live in a database in accounts registered to your company, not ours. Uzbekistan's personal-data law requires citizens' personal data to be stored on servers inside the country, so we collect the minimum — name, phone, order — and decide with your lawyer, before we build anything, where the personal-data tables sit.

Our customers use old phones. Will it work?

That is exactly what we test for. We check on the oldest Android we can find and on a slow connection: big buttons, one question per screen, no icons without text, a way back from every step. On the intercity bus product the audience ran from students to grandparents — the design rules came from there.

What if we later need a native app?

It is built on the same backend: the same users, the same subscriptions, the same orders. Nothing is thrown away and the bot keeps running for the people who prefer it. A native app makes sense only when you need background location, offline mode or your own push channel — we say so plainly on the Mobile apps page.

Contact us.

Describe one process that eats your team's time. We'll tell you what to start with — and what the manual work costs you now.