Telegram bot for appointments
The bot shows the time that is genuinely free, holds the slot the moment it is picked and sends the reminder itself. An administrator agrees no times by hand.
- Buildfrom $750
- Timeline1–3 weeks
- Supportfrom $420/mo
Who this suits: Salons, practices and individual specialists where booking happens in a chat and agreeing the time takes longer than the appointment.
What is in the first version
- free slots
- reminders
- rescheduling and cancelling
- the administrator’s diary
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 client sees only real availability
Slots come from working hours, taken appointments, the service length and the buffer between visits.
- 02
Picking closes the slot immediately
The tap holds the time and confirms it, or says the slot is gone and offers the next one.
- 03
The reminder arrives in the chat
It carries a button to move the visit and a button to cancel, freeing the slot in time.
What decides whether this works or annoys people
The diary lives in two places
Manual entry and blocking sit in the same database, because a bot with its own picture of the day produces clashes.
A dialogue with no way out
Every step has a step back, and buttons under old messages stop working and say so instead of booking a passed time.
A reminder can fail to arrive
A blocked bot cannot deliver, so the error lifts the booking onto the administrator’s list rather than passing as forgetfulness.
What to measure once it is live
- bookings without an administrator
- reminders that reach the client
- reschedules instead of no-shows
- how full the day is
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 logicPythonFastAPITelegram Bot API
- Schedule and dataPostgreSQLRedisDocker
- Payment and the administrator’s screenStripeTypeScriptNext.js
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
- hosting or a VPS for the bot
- payment provider fees on prepayments
- SMS and telephony for duplicate reminders
- the paid plan of a calendar service
Asked before the first call
- What if a client does not use Telegram?
- An administrator books them from the same diary, and they get the same reminders through another channel. There is one schedule, and it does not care which route a booking takes.
- Can it take a prepayment inside the bot?
- Yes, the payment sits in the step that confirms the slot, which is then held for a limited time. The rule for a cancellation is written in before launch and shown at booking.
- Can we change services, prices and hours ourselves?
- Services, durations, prices, hours, days off and every message are settings in an admin panel. A new mechanic, a waiting list for instance, is a code change, and we name its price first.