Clients book a service in under a minute, day or night — and the request is waiting for your staff with everything they need to confirm it.
If your clients book by messaging you, you know the pattern:
1. The client books in under a minute. The bot opens with a menu: book, reschedule, cancel, or get help. To book, the client picks a service from buttons (or types one that is not on the list), then sends a date and time, a name and a phone number. The bot checks that the date and the phone number are real before moving on, so you do not get "sometime next week" or a number with a digit missing.
2. Your staff get the request immediately. The moment the client finishes, the bot sends the request — service, preferred time, name, phone and a reference number — to everyone you tagged as staff, in Telegram. The client sees "Request received, we'll confirm shortly" with the same reference.
3. Reschedules and cancellations reach you too. A client who needs to move or cancel taps the menu, gives the reference and the new time, and your staff get a separate alert. "Help" opens a live conversation with your team in the same chat, through the live chat inbox.
Be clear about this before you launch: the template does not see your schedule. The availability step is a placeholder that always answers "available", so every booking is a request your staff confirm, and the bot words it that way. For most small businesses that is exactly right — you keep control of your calendar and still stop typing the same questions.
If you want the bot to check real free slots, replace that placeholder with your booking system's API through an HTTP request step, or connect the Google Calendar module, which can check free/busy time and create events. Neither is wired in the template; you add it yourself. Reminders before the visit are not part of the template either.
A salon is the typical case: many services, several masters, and clients who write at 11 p.m. Rename the sample service buttons to your real services — haircut, colouring, manicure — and add one more button question if clients choose a master. The "Other service" button stays, so a client can still type something unusual. Tag each administrator as staff, and every request lands with the person who manages the schedule.
Table reservations need different questions: how many guests, which day (today, tomorrow or another date) and what time. The restaurant template asks exactly that, collects a name and phone, saves each reservation as a row in Google Sheets through the Google Sheets module, and alerts your hosts.
If what you collect is not a time slot but a general enquiry, the lead bot is the better starting point.
Not out of the box. The template collects the preferred date and time and sends the request to your staff to confirm. To check real availability, replace the placeholder step with your booking system's API or connect the Google Calendar module yourself.
Yes. The menu has Reschedule and Cancel. The client gives the booking reference and, for a reschedule, a new time; your staff get a separate alert for each.
Not in the template. It handles the booking request, reschedules and cancellations. Reminders would have to be added to the flow separately.
Yes — the flow is the same for any business that books clients for a service. Rename the service buttons, tag the people who manage the schedule as staff, and publish.
Yes. There is a free plan and no card is required to build and test a bot.
Start from a template on the free plan. No card required.
Clone the booking bot template