Your restaurant answers WhatsApp and holds the table during the rush

• Connect the restaurant's WhatsApp and load your menu. The same number already listed on Google Maps, printed on the flyer and shown on your Instagram, and Instagram too if you want, so reservations can start there. Each dish is loaded with a name, description, price and photo, or pulled from your store if you already sell online with Shopify or Jumpseller.
• Define how booking works. Each table size is loaded with how many you have of that size, how long a reservation lasts, the gap you need between one seating and the next to clear and reset, how much notice you accept and how far ahead people can book. Your hours, the days you close and public holidays load once and are subtracted on their own.
• Switch the agent on and it works. It answers what comes in, shows only the times you genuinely have free, holds the table and sends the WhatsApp reminder before the reservation.

This is management setup, not technical work: it happens in the platform, using what is already written on your menu. There is one decision worth making on day one: out of the box the agent hands over your booking link and the guest picks the time there. If you would rather it close the reservation inside the conversation, you switch the calendar to conversational mode in the settings. Both paths read exactly the same availability.

• Each table size is loaded with how many you have. A table for 4 counts as full only once every table that size is taken, not when the first reservation comes in.
• It never offers a taken time, and it checks again that it is still free right before holding it.
• It holds the exact time the guest asks for. Ask for 8:45 and you get 8:45, and if it truly does not fit, it offers the nearest genuinely free time instead of a list of round hours.
• Every reservation has its own duration and its own buffer: an hour and a half at the table plus fifteen minutes to clear and reset before the next seating.
• Minimum and maximum notice: no bookings five minutes from now, and none eight months out, unless you want them.
• The days you close and public holidays are subtracted for everyone.
• The private room can be booked by range: the guest picks a start and an end within what is free, instead of a fixed block.
• The agent cannot invent a time. If a message claims availability that did not come from the system, that message is corrected before it goes out and replaced with real times.
• If you want a deposit for large parties or for the private room, you turn that on in the calendar settings: the agent shows times but will not hold anything until the proof of payment arrives, and if you connect MercadoPago it can send the payment link.

Here is the fine print, said before you discover it yourself: there are two ways to set reservations up and they are not equivalent. If the table is loaded as a space with how many you have of that size, which is the natural fit for a restaurant, the reservation lives in TBit's own calendar, the confirmation is the agent's message in the chat and the reminder goes out on WhatsApp. If a person hosts the reservation instead, the events coordinator for example, and that person connects their Google account and activates it on this agent, you also get the Meta-approved confirmation template, the email with the reservation attached and the event in their Google Calendar, which is read and written both ways: anything they block in that calendar stops being offered.

This thread runs with the calendar in conversational mode, which is not the out-of-the-box mode. Out of the box the agent hands over your booking link and the guest picks the time there. Both paths read the same availability.

The agent does not join two tables and does not split a party: this worked because that restaurant has a table for 6 loaded as another size.

Three things happened there and all three are worth money: the reservation came in on a Thursday at 11 at night with the restaurant closed; the times it offered genuinely existed, because before writing them it is checked that they came out of real availability; and the 8:45 table went back on the board the same second, ready for another group instead of sitting empty. Nobody on your team opened the chat.

So the example does not sell you more than there is: this conversation runs with the calendar in conversational mode, which is not the out-of-the-box mode. And both reminders are written the way the template created on day one writes them, a short line with the date, the time and the address. If you want it to say "your table for 4" or the name of whoever booked, you write that text yourself.

One more important point: the agent does not join two tables and does not split a party. Going from 4 to 6 worked because that restaurant has a table for 6 loaded as another size, with how many it has of that size. And if it had a late-change policy, the 7:02 p.m. message would not have gone straight through: the agent would have explained the free-change deadline and the fee to Andres, and would only have moved the booking if he agreed.