Yes, if you flag cuts as sold-out on the menu post or via a daily-status field, the bot reads that flag and quotes accordingly. A guest asking about brisket at 15:00 on Saturday gets an honest answer when it's sold through, not a hopeful one. For pits that update sold-out status mid-service, the bot reflects the new state on the next conversation without any retraining.

Yes. If you publish wood type, rub composition, and sauce options on each cut's page, the bot quotes them exactly. Post oak versus hickory versus pecan, dry rub versus wet rub, vinegar sauce versus tomato versus white, all read from the page. It will not invent a wood or a rub recipe you have not specified, so the answer is always something the pit actually does.

If you publish standard pounds-per-person guidance, the bot reads it and applies it to the party size in the chat. Typical defaults are around a third of a pound of meat per adult as part of a mixed meal with sides, or half a pound if meat is the main attraction. The bot can also recommend family packs that match the party size and meat preference more directly.

Yes. If your catering page lists minimums, lead times, delivery windows, and pricing, the bot reads it and answers within those parameters. For inquiries above your floor cap or with custom requirements (cocktail-style service, on-site pitmaster, late-night delivery), the bot routes to the events email rather than booking through the standard channel. That keeps the events team in the loop on the right leads.

Most rubs and sauces are gluten-free by default in BBQ, but if you use a soy-based or beer-based component on certain cuts, the bot quotes that exactly. Sides vary: mac and cheese contains dairy, slaw can be made dairy-free if your kitchen does it that way. The bot quotes those tags from each side post and defaults to a confirm-with-the-team note for celiac diners.

Yes. SleekAI supports multibot, so each pit in the group has its own chatbot scoped to that location's menu, wood, hours, and sold-out flags. Cross-location confusion, like the flagship's burnt ends quoted at a satellite that does not serve them, never reaches a guest. Shared brand-wide notes like the smoking process can sit in a shared knowledge layer.

SleekAI is a one-time WordPress plugin license. You bring your own API key (OpenAI, Anthropic, Google, or OpenRouter), so the running cost is just the model tokens, typically a few cents per conversation. For a BBQ restaurant doing 200 chat conversations a day on GPT-4o-mini, that runs well under what a per-location SaaS chatbot subscription would charge each month.

SleekAI does not place orders directly. It links the guest to your existing ordering page, Toast, Square, or your custom checkout at the right point in the conversation, with the cuts already chosen if the guest specified them. That keeps order data in one place and lets the chatbot focus on cut availability, portion math, and catering routing rather than running a parallel order channel.