Table reservations on WhatsApp: a restaurant bot that never gives a busy tone
A restaurant reservation bot on WhatsApp asks date, time and party size through simple buttons and a list menu, checks table capacity from a live sheet, and confirms instantly, something a phone line busy with in-house guests often can't do. A reminder before the visit and a review request after close the loop without extra staff effort.
- WhatsApp reservations don't get a busy tone, unlike a phone line during dinner rush.
- Check real capacity from a live sheet before confirming, not just accepting every request.
- Send a reminder a couple of hours before the booking to cut down no-shows.
- Ask for a review only after a positive signal, not from every guest automatically.
- Route large-party bookings to a manager rather than auto-confirming them.
The problem with phone-only reservations
A restaurant's phone line is often busiest exactly when it's hardest to answer, during service. Callers hear a busy tone, hang up, and try a different restaurant. A WhatsApp reservation flow is always available, and guests are increasingly comfortable booking this way instead of calling, especially younger diners who prefer not to make a phone call at all.
There's also a staffing angle. Whoever answers the phone during service is usually pulled away from something else, seating a guest, taking an order, running food, and a missed reservation call often means a table sits at reduced occupancy that evening for no reason other than nobody was free to pick up. A WhatsApp flow removes that trade-off entirely, since it doesn't need a person standing by.
Designing the reservation flow
Keep the flow to three quick questions: date, time and party size, using Buttons for common party sizes (2, 4, 6+) and a List Menu for time slots. Free-text entry for these fields causes ambiguous replies like 'evening' that need clarification and slow the booking down.
| Step | Input type | Why |
|---|---|---|
| Date | List Menu (next 7 days) | Avoids ambiguous dates like 'this Saturday' |
| Time | List Menu (slots in 30-min blocks) | Matches actual seating turns |
| Party size | Buttons (2 / 4 / 6+) | 6+ routes to a manager, not auto-confirm |
Checking real capacity before confirming
Connect a Google Sheets capacity sheet (or your table management system via HTTP/API request) so the bot checks actual availability for that date and time slot before confirming. Confirming blindly and then calling back to cancel is worse for the guest experience than a slightly slower but accurate confirmation.
Edge case: if the exact requested time is full, offer the two nearest available slots instead of just saying 'not available', most guests are flexible by 30 minutes either way if given the option. Also account for table-turn time in the capacity sheet itself, a table booked for 8 PM typically isn't free again until an hour or more later, and a capacity check that ignores this will overbook without anyone noticing until guests actually arrive.
Confirmation, reminder and review request
- On confirmation, send the booking summary along with the restaurant's location pin.
- Use a Wait / Delay block to send a reminder about two hours before the reservation time.
- After the visit, triggered manually by staff or via a follow-up delay, send a short review request, branching with Buttons so a happy guest gets a Google review link and an unhappy one is routed to a manager instead of a public review request.
This branching step matters more than it looks. Sending every guest straight to a public review link, regardless of how their visit went, risks surfacing complaints publicly that could have been resolved privately. A simple 'how was your visit?' with Buttons for good and not-so-good routes each guest to the right next step before any review is requested.
Large parties and other edge cases
Bookings above a certain size (six or eight, depending on your seating) usually need special table arrangements and shouldn't be auto-confirmed the same way as a table for two. Route these to a Condition branch that notifies a manager for manual confirmation instead. Similarly, treat same-day, last-minute bookings differently, a request for 'tonight in 20 minutes' should check live capacity rather than the general day's schedule.
Another edge case: a guest who reserves but plans to arrive with a different party size than stated. Add a simple line in the confirmation, 'let us know if your party size changes', so the kitchen and floor staff aren't caught off guard by a table of six arriving for what was booked as a table of four. Special occasion bookings (a birthday, an anniversary) are also worth a dedicated question, a quick 'is this a special occasion?' lets staff prepare a small gesture that costs little but is noticed.
Building it on Convo360
Here is how to set this up on Convo360.
- Trigger the flow on keyword ('table', 'booking') or a website enquiry form.
- Collect date, time and party size using Buttons and List Menu.
- Check availability with a Google Sheets lookup and a Condition block.
- Confirm with Send Media for the location pin, and a Wait / Delay reminder step.
- Add a post-visit review-request sub-flow using Call Sub-flow.
What it costs, and measuring it
Reservation flows run on the Starter plan (₹999/month), which covers WhatsApp, the flow builder and the Google Sheets integration needed for capacity checks. A restaurant wanting a small deposit for peak-night bookings can add a Razorpay payment link on the same plan.
Track two numbers over a few weeks: reservation-to-arrival rate (how many confirmed bookings actually show up), and review-request response rate. If arrivals lag confirmations noticeably, tighten the reminder timing or consider a deposit for peak slots.
Also worth watching over time: which days of the week see the most no-shows despite a confirmed reservation. Weekend evening slots often behave differently from a weekday lunch booking, and if one specific slot type consistently under-performs, a targeted fix, an earlier reminder, or a deposit requirement just for that slot, is more useful than a blanket policy applied to every booking.
Example conversation
Industry guide: AI agents for Restaurants & QSR — Reservations, orders & feedback on autopilot.
Set up WhatsApp table reservations
Start free in minutes — no code, no credit card. Bring your own AI keys and pay no per-message markup.
Frequently asked questions
Can the bot handle large party bookings differently from a table for two?
Yes, you can branch the flow so parties above a certain size are routed to a manager for confirmation, since large bookings often need special table arrangements.
What happens if the requested time slot is fully booked?
The bot should offer the nearest available times instead of just saying 'not available', using the same capacity sheet to suggest real alternatives such as a slot 30 minutes earlier or later that still suits the party size.
Can guests cancel or modify a reservation through WhatsApp?
Yes, if the confirmation message includes a 'Modify' or 'Cancel' button that routes back into the booking flow or notifies staff directly, so the guest never has to call the restaurant just to change a time.
Does this reduce no-shows meaningfully?
A reminder close to the reservation time is the main lever for reducing no-shows; some restaurants also request a small deposit via a payment link for peak-time bookings.
Can the same bot also take takeaway orders?
Yes, though it's usually cleaner to keep reservation and ordering as separate flows triggered by different keywords, so each stays simple and focused rather than mixing table bookings and food orders inside a single confusing conversation.
Can guests mention special occasions like a birthday when booking?
Yes, add a short optional question during booking so staff can prepare a small touch for the occasion, and note it clearly for the floor team ahead of the guest's arrival.
Related reading
Available across India — see WhatsApp & AI calling automation by state and city.