Telegram bot development
A Telegram bot takes over the routine people do by hand today: it takes requests, books customers, sends reminders, answers common questions and tells you about what matters. It works around the clock and doesn’t mix up bookings. I build bots for customer-facing work and for internal team tasks.
Why a bot and not one more person on the phone
Customers don’t need to install anything: they already have Telegram. The bot answers immediately, even at night and on weekends.
Requests don’t get lost between calls and messengers. Everything lands in one database, and you see the full picture: what’s booked, who signed up, what needs confirming.
A bot does it the same way every time: it doesn’t forget a reminder, mix up the time or miss a request.
What a bot can do
- Booking: service, date, time, checking free slots.
- Taking requests and orders with the fields you need, straight to your chat.
- Reminders for customers: bookings, payments, important dates.
- Broadcasts to those who opted in.
- An admin menu for the owner: prices, services, schedule, statistics — no developer needed.
- Internal bots: failure alerts, reports, server control, staff access.
What Telegram gives out of the box
- Buttons and menus right in the chat, no commands to type.
- Payments in the chat through a payment provider, digital goods in Stars.
- Groups and channels: the bot can post, moderate and reply there.
- Mini Apps: when buttons aren’t enough, the bot gets a full interface.
How it works
- The bot runs on a server as a system service. If something crashes, it brings itself back up.
- Data lives in a database, not in memory, so nothing is lost after a restart.
- Roles: customer, staff and admin each see their own menu.
- Before every update the bot goes through automated tests and scenario checks right inside Telegram.
- No open ports needed: the bot itself reaches out to Telegram.
Examples from my projects
A kids' café took bookings by phone and in messengers. Since the bot launched, parties went from 3–4 to 5–7 a week, and 4–5 of them are booked through the bot.
read the development story →cat ./server-office.md19 workstations under control from the owner's phoneThe office owner called the admin over every little thing. Now he has a Telegram bot with a Mini App panel: he sees who's working, shuts off logins, adds people and restarts the server himself, from his phone.
read the development story →How the work goes
- 01Brief
We dig into the task and agree on what counts as “done”.
- 02Prototype
I show a mockup or a demo on a test bench before the main code.
- 03Build
In small stages. A backup before every change, a rollback for each.
- 04Testing
First on a copy of your environment, then on the live one.
- 05Handover
A guide, I explain how to use it, and I stay in touch.
Questions
What do you need from me to start?
Tell me how things work now and what gets in the way. We’ll sort out the rest at the brief: which flows are needed, who uses what, what counts as done.
Where will the bot run?
On a server: yours or a rented one. I’ll suggest what fits and set everything up.
Can I change prices and texts myself?
Yes. The bot has an admin menu for that: prices, services and schedule can be edited without a developer.
Can the bot take payments?
Yes. Physical goods and services use a connected payment provider; Telegram allows digital goods to be paid in Stars.
How much does it cost and how long will it take?
It depends on the task. After the brief I give you the scope, timeline and price. Before the main build I show a prototype or a plan, so you can see what you will get.