S-04 / Telegram bots & Mini AppsServices

Telegram bots & Mini Apps

From the smallest automation to a full storefront — all inside a Telegram bot or Mini App, where your customers already are.

Book an audit Message on Telegram ↗

S-04.1Problem

What it looks like today

Our whole shop is a Telegram channel: 300 posts with prices, and customers write "is this still available?" under a photo from March. 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.

Every developer offers us a native app for $20,000, 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.

S-04.2Outcomes

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

S-04.3How it works

Three steps, in this order.

01Step 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 pilot has to nail that one flow. The rest comes later, once the first one works.
02Step 2
We build and connect payments
We build the Mini App on your real catalogue and prices, with Payme and Click in test mode by week two and live payments by week three. Week four is measurement 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.
03Step 3
Scale on a retainer
Once the numbers hold, we add the next flow each month — loyalty, subscriptions, a parent portal, 1C sync — keep the app monitored and hand over the code as we go. The app keeps running if you stop.

S-04.4Deliverables

What you sign off on

Flow map and paper screens of the one flow the pilot must nail (PDF, UZ/RU)
Telegram Mini App (Next.js + Supabase) deployed under your bot: catalogue, cart / booking and order history
Payme and Click merchant integration with receipts in chat and a payment ledger — set up in your merchant accounts, not ours
Admin panel: orders, bookings, customers, payments, exports to Excel and 1C
Reminder and notification bot: booking reminders, order status, unpaid-invoice nudges
Measurement sheet: orders through the app vs. chat, post-to-paid time, no-show rate from week four
Repository, credentials and a runbook in plain language; a 2-hour recorded handover for your manager

S-04.5Price

What it costs.

By agreement

Exact quote after the free 30-minute audit.

S-04.6Proof

We run what we build.

Fact 01
The AcademyOS parent portal is a Telegram Mini App: today's schedule, attendance, the month's invoice and a Pay button that opens Payme or Click; the receipt comes back into the same chat. Built and run by us for football schools, in three languages.
Fact 02
A Telegram-first product replacing a 4,000-member intercity bus chat: bot, subscriptions, an interface people of every age can use. "Telegram first, app later" is our own playbook.

S-04.7Questions

Questions we get on the first call.

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. At the audit we 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 at the audit 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.

S-04.8Next step

Start with the free 30-minute audit.

Five questions, one call. You leave with the workflow to automate first and a cost estimate.