Five Star Restaurant Reservations is one of the most-installed restaurant booking plugins on wordpress.org. It already does the hard part: schedule, exception rules, dining-block length, party-size limits, table layouts on Ultimate, optional deposits, and the rtb-booking custom post type that holds every reservation. What it does not do is talk to your visitors before they reach the form.

SleekAI fills that gap. The bot reads the rtb-booking post type plus its postmeta, the schedule settings, your exception calendar, the per-location maximums, and (on Ultimate) the table sections and seat counts. It can quote real availability for tonight at 7:30 for a party of four, then create the reservation directly through the same hooks the booking form uses.

It also reads your menu wherever it lives, including custom post types from companion menu plugins, so allergen, course, and dietary questions get answered inline. The visitor never bounces to a separate page just to find the gluten-free options.

Five Star Reservations is mature. The schedule logic is tight, the notifications work, the table-and-section feature on Ultimate handles real-world layouts. The piece that nobody packaged well is the conversation that happens before a booking.

Visitors do not arrive on the booking form already knowing what they want. They want to know if you can do Friday at 8, whether you can manage a peanut allergy, whether the patio is open, whether the kid menu has anything for a picky six-year-old. Most of that is decidable from data you already store.

A generic chatbot turns those questions into vague reassurances and a link to the booking page. SleekAI turns them into a confirmed reservation in your admin. The bot reads the schedule and exceptions, so the times it quotes are real.

It reads existing rtb-booking entries, so it knows when the dining-block is full. It reads your menu and knows which dishes are peanut-free. It can create the booking through the standard plugin hooks, so the admin sees it like any other reservation and the standard email goes out.

Hosts spend less time fielding the same questions on the phone. The kitchen sees dietary flags before service starts. Repeat guests get faster responses because the bot can look up their email in past bookings and pre-fill the next reservation.

The plugin keeps doing what it is good at, the chatbot does the thing the plugin was never designed to do, and the visitor ends the evening with a confirmation already on their phone.