Appointment Booking

Perfect for any service business — salons, clinics, consultants, repair shops — where booking still means a phone call or a missed message. Customers get a menu to book, reschedule, or cancel in a few taps at any hour, your team gets notified the second a request comes in, and nothing gets confirmed as done until a real person — or a connected calendar — has actually checked availability.

Flow Preview

Appointment SupportAppointment MenuNew AppointmentManage Appointment

Overview

Let customers book, reschedule, or cancel an appointment straight from Telegram — every request lands with your team instantly, with a reference number for both sides to track.

Who It's For

Perfect for any service business — salons, clinics, consultants, repair shops — where booking still means a phone call or a missed message. Customers get a menu to book, reschedule, or cancel in a few taps at any hour, your team gets notified the second a request comes in, and nothing gets confirmed as done until a real person — or a connected calendar — has actually checked availability.

Setup Requirements

  • Which services should customers be able to book?
  • Should availability be checked through a calendar API, or will staff confirm requests manually?
  • What customer details do you need before you can confirm a booking?
  • Connect your Telegram bot: Settings → Bots → paste the token @BotFather gave you.
  • Open Variables and list the services you offer so the booking menu matches your business.
  • To notify staff about new booking, reschedule, and cancellation requests without a calendar API, tag them with the "staff" tag on the Contacts page — each notification goes to everyone carrying that tag (keep this to a small team; recipients are capped).
  • If you have a booking or calendar system, connect it to replace the placeholder availability check and confirm bookings automatically.
  • Press Deploy, then book a test appointment on your own bot to confirm the request, the reference number, and the staff notification all arrive.

Node Breakdown

  • Someone opens your bot and picks: book an appointment, reschedule, cancel, or get help
  • For a new booking, they choose a service — or type one in if it's not listed — then send a preferred date and time
  • A quick availability check runs before anything is confirmed
  • They give their name and phone, and get a booking reference plus "request received" — never a false "confirmed" before a real check happens
  • Your staff are notified immediately with the customer's name, service, and preferred time
  • For an existing booking, they give the reference and can request a reschedule or cancellation the same way
  • If a slot doesn't work or they need help, the bot offers another time or opens a live conversation with your team

Details

Good to know

  • Out of the box, availability and booking creation are placeholders — nothing is marked confirmed until you've reviewed it or connected a real calendar. That's the safe default, not a limitation.
  • Connect a booking or calendar API afterwards to check real availability and confirm automatically — that's a setup step, the conversation itself doesn't need to change.
  • If you'd rather confirm bookings by hand, keep the placeholder step as is — your team reviews each request through the same notification.
  • Live support opens as a real conversation inside your workspace whenever a customer needs staff help, no separate app required.
  • Everything is editable afterwards in the visual editor — the service list, the questions asked, and who gets notified are all plain settings, not code.

Keep in mind

  • The bot never claims an appointment is confirmed unless a real booking check has actually run — until you connect one, it says "request received," which is the honest version.
  • If an availability check fails, the customer is always offered another time or a way to reach staff — they're never left stuck.
  • Keep staff notifications on a small, real team; the recipient list is capped by design so alerts stay useful.