Telegram bot for selling courses
The bot shows the plans, takes the payment and opens access in the same moment. Between the payment and the first lesson there is no person adding buyers one at a time.
- Buildfrom $750
- Timeline1–3 weeks
- Supportfrom $420/mo
Who this suits: Courses and intensives sold from posts and webinars, where buying means bank details in a message, a screenshot of the transfer and an admin adding people by hand.
What is in the first version
- plan list
- in-chat payment
- automatic access
- single-use invites
The figures above are the package this sits on: Telegram bot. Anything past its edges the calculator adds before the work starts, not after.
How the path goes
- 01
The plan is chosen in-chat
The bot opens from a channel link and shows the plans, with no jump to a site.
- 02
The provider confirms the payment
The buyer pays in the same dialogue, and the provider’s webhook opens the door, not a screenshot.
- 03
Access matches what was bought
A single-use invite opens the channel of that plan, and what a purchase opens is derived from the purchase.
What decides whether this works or annoys people
The invite link leaks
Invites are single-use and short-lived, every join is checked against a purchase, and anyone unlisted is removed automatically.
The refund nobody closed
A refund or a chargeback withdraws access through the same mechanism that grants it, otherwise the channel fills with unaccountable people.
The platform decides the payment method
Telegram treats digital and physical differently, so where a card inside the bot does not fit, payment moves to your page.
What to measure once it is live
- share who reach the payment
- time from payment to access
- sales spread across the plans
- refunds and the access withdrawn
Why this comes out faster
The shape of this one is known: the states, the edge cases and the things that usually go wrong have been decided before. Nothing here is a template, and the saving is not in your half of the work. It goes into your process, your content and the systems this has to talk to, which is the part nobody can have solved in advance.
A likely stack for this
Picked against the task when we scope it, not decided in advance. This is the shelf it usually comes off.
- Bot and the salePythonFastAPITelegram Bot API
- Payment and accessStripePaddlePostgreSQLRedis
- Screens and running itTypeScriptNext.jsDockerGrafana
Price it yourself, right here
Five steps, and you can see the number without leaving a contact. The estimate accounts for the kind of work, what you already have and what it will need inside.
These bills do not come from us
- payment provider and platform fees
- storing and serving the lessons
- hosting or a VPS for the bot
- email to buyers outside Telegram
Asked before the first call
- What do buyers pay with?
- By payment inside Telegram, a card on your own page, or both at once. Access is opened by the provider’s webhook either way, so a second method is one more handler rather than a rebuild.
- We sell cohorts with a start date. Does that fit?
- Yes: a purchase belongs to a cohort rather than to the bot’s calendar, so before the start the buyer waits in a separate channel. Closing sales and admitting a latecomer are settings.
- What if Telegram blocks the bot?
- Buyers, payments and granted access live in your database, so a new bot hands the same access to the same people. What can be lost is contact, so an email is collected at payment.