Restaurant Table Booking

• Someone opens your bot and taps to book a table
• They send the number of guests, then pick today, tomorrow, or another day
• For today or tomorrow they pick a time; for another day they send a date and time directly
• The bot runs an availability check — a placeholder that lets every request through until you connect your reservation system
• They send the request with their name and phone, and your host team is notified to confirm it
• If it's full, they're offered another time or a way to reach staff — never a dead end
• Your host team is notified immediately with the party size, time, and guest's name and phone

• Connect your Telegram bot: Settings → Bots → paste the token @BotFather gave you.
• Open Variables and set your restaurant's name and booking hours so the bot shows guests the right information.
• To alert your floor team about new reservations, tag host contacts with the "host" tag on the Contacts page — the Notify host action messages everyone carrying that tag.
• If you want reservations logged to a spreadsheet, install the Google Sheets module and connect it in place of the placeholder save step.
• If you have a reservation system, connect it to replace the placeholder availability check with real capacity.
• Press Deploy, then send a test booking request on your own bot to check the request message and the host notification.

Good to know

• Availability runs on a placeholder by default: every time shows as open, and guests send a request your host team confirms. Connect a real reservation API afterwards if you want the bot to check live capacity.
• There's an optional Google Sheets connection: if you install the Google Sheets module, each reservation can be logged to a spreadsheet automatically as an extra record alongside the in-bot notification.
• Guests never have to type a command to move forward — every step uses buttons for date, time, confirmation, and support, so it feels like tapping through a form, not chatting with a script.
• Everything is editable afterwards in the visual editor — your restaurant's name, booking hours, the questions asked, and who gets notified are all plain settings, not code.

Common questions

• Should availability be checked through a real reservation system, an installed module, or the built-in placeholder for now?
• What date and time format do you want guests to use for custom reservations?
• Should large parties be routed straight to staff instead of the automatic flow?
• What details do you need from a guest before you'll confirm a reservation?

Keep in mind

• A fully-booked slot is never a dead end — guests are always offered another time or a way to reach staff.
• The bot doesn't ask guests to type spreadsheet or column names — that mapping lives in the module setup, not the conversation.
• Every step uses tappable buttons instead of asking guests to type commands, so booking stays fast on mobile.