Restaurant Table Booking: How to Manage Reservations, Cut No-Shows and Keep Guests
Sales4 min read
How a restaurant should handle table bookings: tables and halls as resources, capacity, bookings from messengers, guest reminders, deposits and no-show losses.

Table booking works without losses when every table is set up as a separate place with a capacity, all bookings are visible in one calendar, and guests are reminded of their visit in advance. Then on a Friday night you won't have two parties at one table — or empty tables "reserved" for people who never came.
Below: how to organise bookings, how much a restaurant loses to no-shows, and how to bring regular guests back.
One-minute checklist
- Set up each table and hall with its number of seats.
- Set a standard booking length — for example, 2 hours in the evening.
- Take bookings from every channel into one calendar.
- Remind guests 24 hours and 2 hours before.
- Take a deposit for banquets and large parties.
Example: what no-shows cost
| Metric | Value |
|---|---|
| Bookings per week | 120 |
| No-show rate | 10% |
| No-shows per week | 12 |
| Average bill per booking | 6,500 ₽ |
| Weekly loss | 78,000 ₽ |
| Monthly loss (4 weeks) | 312,000 ₽ |
If reminders cut no-shows from 10% to 5%, the restaurant gets back about 156,000 ₽ a month — provided the freed-up tables are taken by walk-in guests.
Booking channels
- Phone calls. The host sees free tables immediately.
- Messengers. Guests write in the evening and expect a reply within minutes.
- Website form. The guest picks a date and time, and the request goes to the host.
- Aggregators. These bookings must also land in the shared calendar.
If bookings from different channels live in different places, clashes are inevitable.
Banquets and deposits
For banquets and parties of more than 8, a deposit protects the restaurant from last-minute cancellations. It's best to send the guest the deposit and refund terms in writing and keep them in the conversation.
Regular guests
Booking history shows who comes every month, which table they prefer and when they last visited. A guest who hasn't come for three months can be invited to try the new menu — with their consent to receive mailings, as required by Russia's Advertising Law.
Related reading: CRM for restaurants, booking software, calculating the cost of a dish.
How it works in Mestra

Bookings from messengers in one feed
Mestra is a CRM system: clients, messengers and marketplaces, tasks, finance, analytics and an AI operator in one window.
- Tables and halls as places. Each place has a capacity and a default booking length.
- Calendar by place. The evening's bookings are shown by table, and the calendar warns about clashes and over-capacity.
- Messengers in one window. MAX, Telegram and VKontakte are combined into one feed.
- AI assistant. Answers guests 24/7, confirms the date, time and party size, and records the booking.
- Guest reminders. 24 and 2 hours before, with confirmation or rescheduling.
- Booking form. A calendar field in the form builder; the request arrives in Mestra with the guest's card.
- Mailings. Invitations to regular guests — only to those who have given consent.
FAQ
What booking length should you set?
Lunch — 1–1.5 hours, dinner — 2 hours, banquets — by arrangement. Review the length based on how long guests actually stay.
How can you reduce no-shows without a deposit?
Send reminders 24 hours and 2 hours before and ask guests to confirm. Release unconfirmed bookings 15–30 minutes in advance.
Should you keep booking history?
Yes. It reveals regular guests and helps bring back those who haven't visited for a while.
Can you take bookings at night?
Yes, if an AI assistant answers messages: in the morning, the host sees ready-made bookings.
Bottom line
Table booking means tables as resources, one calendar for all channels and reminders for guests. No-shows cost a restaurant hundreds of thousands of rubles a month, and most of that can be recovered. In Mestra, tables, bookings, guest conversations and reminders are in one window — try it free for 15 days.


