A support inbox nobody can staff
Most of what customers ask is the same twenty questions. A bot answers those from your own content, captures order details in a structured form, and hands the thread to a human the moment it stops being routine.
Telegram bot development is the work of building everything behind an @username: the conversation logic, the database it reads and writes, payment handling, and the API calls into your CRM or ERP. Corexy is a small engineering studio that ships bots and Telegram Mini Apps end to end — one engineer owns the project from the scoping call to monthly maintenance, and the source code is yours.
Most of what customers ask is the same twenty questions. A bot answers those from your own content, captures order details in a structured form, and hands the thread to a human the moment it stops being routine.
Checkout happens inside Telegram — Telegram Payments, Stars, a card provider or a crypto rail — and the order status updates itself. The customer never bounces to a web form, and you see the payment and the order in one place.
A bot without integrations is a toy. We connect it to your CRM, ERP, warehouse or database over API, so stock levels, deal stages and delivery status read the same in the chat as in the system your team actually works in.
Deploy alerts, on-call escalation, approval flows, yesterday's numbers pushed to a team chat every morning. Internal bots are small, unglamorous and pay for themselves quickly, which is exactly why they never reach a product roadmap.
A Telegram Mini App is a full web interface inside the messenger: catalogue, cart, profile, payment. No store review, no install step, no push-permission dialog — the user arrives already authenticated by their Telegram account.
Contractor gone, no documentation, one file with three thousand lines in it. We take the repository, get it running locally, write down what it actually does, and tell you honestly whether extending it is cheaper than a rewrite.
A 40–60 minute call: who uses the bot, what it does with data, which systems it has to talk to. You leave with a scope, a price range and a delivery date. It is free and you owe us nothing afterwards.
We write the spec, not you: screen map, message copy, user roles, integrations, and what happens when a payment provider times out. You review and correct it; the build starts only after you sign it off.
Flow skeleton first, then the database, then payments and integrations. A test bot is in your hands from week one, so you click through the real thing instead of approving screenshots of conversations.
We run the ugly paths too: failed payments, double taps, users blocking the bot. Then we deploy to your server with monitoring and auto-restart and move the repository and the BotFather token to your accounts.
For one month after release, bugs in delivered functionality are fixed free. After that: hourly work from $30, or a monthly retainer with a dedicated engineer from $400 covering monitoring and small changes.
We pick the stack for the load and for whoever maintains the bot after us — a request-capture bot does not need Kubernetes, and a Mini App taking payments will not survive on a spreadsheet. Default: Python with aiogram for the bot, PostgreSQL for data, React for the Mini App.
A 5–10 step flow, structured request capture, a minimal admin view, export to Google Sheets or a team chat, deployed on your server. Price moves with the number of branches in the flow and the number of user roles.
Database, user profile, in-chat payments, CRM or ERP integration, roles and permissions, an admin panel for content and broadcasts. The main cost driver is how many systems it talks to and whether they have a usable API.
A full interface inside Telegram — catalogue, cart, checkout, profile — on a backend built to survive a broadcast to your entire list. Event analytics and AI features where they earn their place. Delivered in phases, first phase to MVP.
Prices are indicative and do not constitute a public offer. The final cost, scope and timeline are fixed in a contract or invoice after we have discussed the task.
Hook is a travel bot in Telegram with a CRM admin panel and an AI lead channel behind it. It carries 12+ products across 13 database tables, and its AI runs on Gemini plus a locally hosted Qwen model. It is the reference project for bots where the chat is only the surface and the real work happens in the database and the admin panel a manager logs into.
Read the Hook caseTwo paragraphs about the process you want automated are enough for us to come back with a scope, a price range and a delivery date. We reply within 2 hours during business hours and the scoping call costs nothing.
Discuss your task