DEV Community

Veilvex
Veilvex

Posted on Originally published at veilvex.com

Telegram booking bots: 5 things that break in production

Every small business owner who lives in Telegram eventually asks for the same thing: "Can clients just book through a bot?" The answer is yes, and the first version usually takes an afternoon. The trouble shows up a week later, when a reminder never arrives, two clients turn up for the same 6 pm slot, or the morning reminder batch hits a rate limit.

Here are five things that break Telegram booking bots in production, and what to do about each one.

1. A bot cannot write first

This is the rule that surprises business owners most. A Telegram bot can only message a user who has opened it and pressed Start. There is no way to send a reminder to a phone number.

So a client who booked by phone gets no Telegram reminder until they open the bot themselves. In practice:

  • Make the bot the start of the booking, not an add-on. Put the bot link or a QR code wherever a client books: the site, the Instagram bio, the receipt, the confirmation SMS.
  • When an admin books someone by phone, send them the bot link right away and ask them to tap Start. Then attach the booking to their chat once they arrive.
  • Keep a fallback channel (SMS or a call) for clients who never open the bot.

2. One source of free slots, and only one

The most common bug isn't in the bot at all. The bot reads free slots from Google Calendar, while the admin still writes phone bookings in a paper diary. Sooner or later the same time gets booked twice.

Pick one source of truth and route every booking through it, whether it comes from the bot, a phone call or a walk-in:

Source Good for Watch out for
Google Calendar / Outlook One or a few specialists Service length and breaks have to be rules, not manual blocks
Booking system or CRM Several specialists or branches Check that it has an API the bot can use
Spreadsheet A pilot with few bookings Two bookings at the same moment can clash

On the code side, treat "check slot → write booking" as one atomic step. Re-check that the slot is still free right before you write, or use whatever locking or conditional write your calendar or database offers. Two clients tapping the same button a second apart is a normal Tuesday, not an edge case.

3. Reminders go out in a queue

Telegram limits how fast a bot can send. The Bots FAQ says roughly 30 messages per second to different users. A salon with 40 bookings a day will never notice. A chain that sends every reminder at 09:00 sharp will.

  • Queue reminders and spread them over a few minutes instead of firing them in one loop.
  • Handle the "too many requests" error by waiting the time Telegram tells you to wait, then retry.
  • Use buttons in the reminder itself (Confirm, Reschedule, Cancel). If there's no confirmation by a set time, free the slot or alert the admin, depending on the business's rules.

4. Prepayment for a visit is not paid in Stars

Telegram Stars are for digital goods and services. A haircut, a dental check-up or a massage is an in-person service. The deposit for it goes through a payment provider connected to the bot (see the Bot Payments docs), and the business needs a provider that works in its country.

If prepayment matters to the client, check provider availability before you promise it. It's the item that most often pushes a launch back.

5. You are storing personal data

Names and phone numbers are personal data. If any clients are in the EU, GDPR applies: you need a data processing agreement with your hosting and with any AI service you call (Art. 28). Store only what booking needs, and decide how long you keep it.

If the bot uses an AI model to understand free text like "Can I come Thursday after six?", there is one more rule. From 2 August 2026, the EU AI Act (Art. 50) requires telling people they are talking to an AI system. One line in the first message covers it.

What to agree on before writing code

Most rework comes from questions nobody asked at the start:

  1. Services with their duration and price, and who performs each one.
  2. Working hours, breaks and holidays.
  3. Where free slots live, and who may change them by hand.
  4. Whether there is prepayment, through which provider, and the cancellation rules.
  5. Who gets the booking (calendar, CRM, a team chat) and who handles non-standard requests.
  6. Whose account the bot is created on. It should be the business's account, not the developer's.

We wrote a longer guide for business owners, covering the four ways to get a booking bot, the Telegram rules and what you pay once versus every month: Telegram booking bot: what it does and costs.

Top comments (0)