It can quote whatever you publish. Most brunch spots use a 'typical wait by hour' table on a busy-times page, and SleekAI reads that and gives a sensible range. For a live current-minute wait you would need to push that figure into a small field on the page (most wait-list tools can do this via webhook), and the bot will read it. Without a live source the bot stays honest and gives the typical range with a 'check Resy Notify for the live figure' nudge.

Yes, as long as the rules are published. SleekAI reads your bottomless page (time window, price, food minimum, last seating cut-off, per-table maximum) and explains them in one short reply. If you change the window from 90 to 120 minutes the bot reflects it the next minute, with no retraining.

Yes. SleekAI does not run a wait-list itself, but it links guests to Resy Notify, Yelp Waitlist, NextMe, Wisely, or your own form at the right point in the conversation, with party size and time already in context. The wait-list stays the single source of truth so the host stand is not juggling two queues during the rush.

Yes, from your menu posts and allergen tags. Tofu benedicts, gluten-free pancakes, and dairy-free latte options get listed accurately, and the bot defers to staff for severe allergies. We recommend tagging each menu post with diet flags so the bot can filter in one question rather than guessing across descriptions.

Yes, any language the underlying model supports. Tourist-heavy brunch spots get walk-ups speaking French, Spanish, Italian, or Japanese, and the bot replies in their language while keeping dish names and prices verbatim. The wait-list link is the same in every language, so the funnel does not split.

SleekAI is a one-time WordPress plugin licence plus your own OpenAI, Anthropic, Google, or OpenRouter usage. A typical brunch spot doing a thousand conversations a month on a gpt-4o-mini class model lands well under 20 USD a month in API fees. Compared to monthly per-seat brunch-chat tools, the total cost stays manageable even on a single-location budget.

Yes. Multibot supports a separate chatbot per URL pattern or page template, so /brunch and /dinner can have different tones, knowledge scopes, and presets. The host-stand experience stays unified because conversations log to the same WordPress admin, with the page URL noted on every transcript.

All published on your house-rules or family page get read by the bot. If you have two high chairs and a stroller-friendly patio area, the bot says so; if dogs are only allowed on the outside terrace, the bot says that too. Vague claims are not invented. If a guest asks about a policy you have not published, the bot offers to take a message rather than guessing.