AI Reservation Handling for Restaurants
Reservation calls cluster in the two hours when the dining room is fullest, and a party asking for an 8pm table for six does not leave a voicemail; it calls the next restaurant on the list. This workflow puts the agent on the phone and on WhatsApp during service, takes the party size, time, and special requests, checks the real availability in your knowledge base, and confirms the table in writing before the caller goes elsewhere.
The Friday night call flood
The booking calls arrive exactly when the host is seating a line of guests and the floor plan is already live. A request for a window seat for four, a high chair, an early 6pm for a family, all land at the same instant and the host can only answer one. The calls that go unanswered are the ones that become tables at a competitor across the street, because a dinner reservation is decided in the moment, not after a callback.
How the booking conversation works
The agent opens with the three facts that define a booking: party size, date, and time. It then works through what the host would ask on the phone, high chair, booth or table, allergy flags on a specific dish, a birthday candle, and reads the floor from the knowledge base before offering a slot. When the guest accepts, it writes the reservation to the shared calendar and a WhatsApp confirmation lands in the guest's chat with the time, the party size, and any note taken. Changes later in the week, a party shrinking from six to four or a time moving later, are handled in that same thread instead of a new phone call.
No-shows and reminders
Every booking receives a reminder ahead of the day so the host knows who is actually coming. A guest who replies that they cannot make it frees the table immediately, and the agent offers the slot to the first name on the waitlist in the same minute. Parties that need to cancel or shrink can do it by replying to the reminder, and the agent updates the floor plan rather than leaving a six-top ghost on the book. The no-show list stays flagged for the manager without anyone dialing back each party by hand.
A Friday at 6pm
At 6pm the floor is filling and two calls come in at once: a table for eight at 8:15 and a quiet booth for four at 7. The agent checks the live floor in the knowledge base, offers the best of what is actually open, and books both while the host seats a walk-in.
A WhatsApp message asks to move a 7:30 table for two to 9pm after a late showing. The agent checks the late seating policy in the notes, confirms the new time, and updates the floor plan.
A party of five books a birthday table and mentions a nut allergy; the agent notes it on the reservation and flags the kitchen note, then confirms the booking on WhatsApp with the time and party size.
At 7:45 the 8pm party for six replies to the reminder that they cannot make it. The agent releases the table and offers it to the first waitlist name, so the seat never goes empty.
Illustrative example — not a customer testimonial.