Example: a Telegram Booking Bot with Deposit Payment (Salon, Clinic, Tutor)

The pain is not “people cannot find our Instagram.” It is a Tuesday at 11:00 that looked booked and is empty. A Telegram booking bot without payment is still a waitlist. A bot with a deposit turns a tap into a held slot.

This example fits salons, clinics, tutors, consultants, photographers - anyone whose inventory is time. I use a Mini App for the calendar because picking a specialist, a service, and a slot in a text bot is cruelty.

1. The booking + deposit path

The slot is inventory. Until the webhook says paid, it is only a hold.

• Open Mini App from the bot: pick service, specialist, date, time. Show duration and the deposit amount (fixed or a percent of the service).
• On confirm, create a hold with a short TTL (e.g. 10 minutes) so two people cannot pay for the same chair. Then create the payment. If the webhook never comes, the hold expires and the slot is free again.
• Paid: slot is booked, remaining balance shown, calendar for the specialist updates, client gets a Telegram confirmation with reschedule rules.
• Reminders: 24h and 2h before. “Cannot come” with more than N hours left can refund the deposit automatically; later is a policy you write once, not a fight in Direct.

2. Payments in this example

You are collecting a small amount under time pressure. The page must open fast on mobile and support the pay buttons people already use.

• Ukraine: Monobank or LiqPay hosted checkout with Apple Pay / Google Pay. Deposit as a separate invoice; remainder at the venue or a second link after the visit.
• Abroad: Stripe Payment Intents. Do not start subscriptions here unless the product is a membership - a deposit is a one-off.
• Partial refunds: the provider API must be in the design. “Keep 200 UAH, return the rest” is a support path, not a spreadsheet.

3. What I wire besides the pay button

Payment without a calendar still double-books. Payment without a refund path still fills Direct with arguments.

• Staff calendar: Google Calendar or a simple admin Mini App. Double-booking is a product bug, not a “please check Instagram”.
• Timezone and working hours in one place. Telegram users are often in another city than the chair.
• No-show report for the owner: deposits kept vs refunded, empty slots after TTL. That is how you know the 30% deposit is enough.

Conclusion: stop giving away the calendar for free

A booking bot with a deposit is one of the cleanest Telegram payment examples: small ticket, clear inventory, immediate operational win. I build the Mini App calendar, the hold, Mono / LiqPay / Stripe, reminders, and the refund path. If your no-show rate is the real P&L leak, write via the form and we will size a first version around one specialist and one service.