Scenario
A menu, questions and answers. A person reaches a request without an operator.
Telegram bots
A bot takes a request and passes it on: into a record, a payment, a CRM or an admin desk.
- from 1 Week to launch
- 1 Month of support
- 1 Dialogue
What is included
The set depends on the scenario. The bot does the steps you already walk people through by hand.
Requests
A message from the bot becomes a record: name, contact and the point.
Payment
An invoice or a payment link inside the dialogue, when you need one.
CRM
The request lands in your CRM instead of staying in the chat.
Admin and broadcasts
Who wrote, what the bot answered, and a message to people already in a dialogue.
Selected work
VPN service in Telegram with automatic key delivery
A bot through which the client sells VPN subscriptions: customers pick a plan, pay and instantly receive a key — no administrator involved. Built from scratch, later with a separate version for VK. What was built: • Three protocols: WireGuard, Outline and VLESS. The key is delivered right after payment — as a file, a link and a QR code. • New servers are added from the admin panel: the bot connects over SSH, installs and configures the VPN itself, and alerts administrators immediately if something fails. • Choice of location and protocol; switching can be offered as a paid option. • Eight payment methods: YooKassa, YooMoney, Tinkoff, Telegram Stars, Cryptomus, WalletPay, FreeKassa and AAIO — with automatic payment checks and subscription auto-renewal. • Trial period, promo codes and a partner programme with payout tracking. • An admin panel right inside the bot: users, payments, charts, server speed tests, backups. • All bot texts live in a separate file and can be edited without a developer. • A separate version of the bot for VK built on vkbottle. Result: the service runs on its own — from payment to key delivery and renewal; the administrator only adds servers and watches the stats. Stack: Python, aiogram, pyTelegramBotAPI, vkbottle, SQLite, Paramiko (SSH), WireGuard, Outline, VLESS, YooKassa API, Plotly.
Formats and prices
A bot with a scenario starts at the figure below. Payment, a CRM and broadcasts are priced separately.
Scenario
A menu, requests and a notice to you.
From $250
Payment and CRM
A payment in the dialogue and a request in your system.
By quote
Broadcasts and admin
The list of dialogues, replies and messages to that base.
By quote
The first month of support is included. After that, by agreement — the same as for the other services.
How we work
Every stage ends with a result you can check.
- Task review — A call or a chat: your process, goals and where leads get lost today.
- Structure and estimate — We fix the scope, stages, timeline and price before development starts.
- Development — We show results stage by stage, not only at the end. Changes go in along the way.
- Launch and support — We publish, connect analytics and watch it for a month to make sure everything works.
Questions about bots
Can we start with a menu and requests?
Yes. Scenario covers the dialogue and the notice. Payment, a CRM and broadcasts are added once requests are already arriving.
Whose bot account is it?
The bot is created on your Telegram account. Access to it stays with you.
How long does a launch take?
Usually from one week: the scenario, the build, a check of the dialogue, and the handover.
Let's talk
Tell us about your task — we will reply within a day with questions or a first estimate.