Yes. The bot can filter for soy-free AND gluten-free AND nut-free in a single query because tags read independently from each dish post. A guest with multiple avoidances gets a real list of compatible dishes rather than a punt to 'please ask staff.' For combinations with no compatible dish, the bot says so honestly and suggests the chef can prepare a custom plate with notice, which is more useful than a vague reassurance.

Yes. If your wine list flags each bottle as vegan-certified or unfiltered, the bot reads those tags. Many wines use isinglass (fish bladder) or egg whites for clarification, so 'is the wine vegan' is a real question for serious guests. The bot quotes your certification source if you specify (Vegan Society, Vegan Action, BeVeg) so the answer carries the credibility your sommelier already built into the list.

Many vegan fine-dining kitchens use cashews, almonds, and macadamias heavily for cultured cheeses and creams. The bot quotes your kitchen's policy honestly: nut-aware, nut-free with notice, or nut-free always. For severe allergies it defaults to a confirm-with-the-chef note because cross-contact in a shared prep area carries real risk, and a chatbot reassurance is not enough for an anaphylaxis-level allergy.

Yes. SleekAI replies in whatever language the guest writes in. A French-speaking guest gets a French reply using your real dish names verbatim. Tourists get the same names with translated descriptions. This is especially useful for vegan restaurants in tourist neighbourhoods, where international guests planning a trip seek out the city's vegan options ahead of time and want to read the menu in their own language.

If you publish your sourcing partners (local farm, organic milling cooperative, certified-vegan winery), the bot quotes them. It will not invent a supplier you have not listed. For guests who care about the ethics chain (palm-oil policy, fair-trade chocolate, single-origin coffee), this is where vegan restaurants differentiate, and the bot lets that detail surface in chat rather than buried four pages deep in the about section.

Yes. SleekAI supports multibot, so a fine-dining concept and a casual cafe under the same brand each have their own chatbot scoped to that menu, wine list, and prep policy. Cross-concept confusion, like the fine-dining wine list quoted at the casual cafe that does not serve wine, never reaches a guest. Shared brand-wide notes like the sourcing philosophy 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 vegan 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 book tables itself. It links the guest to your existing reservation system at the right point in the conversation, with party size, date, and any dietary detail (soy-free guest, severe nut allergy, mixed diet group) already captured. That keeps booking data in one place and lets the chatbot focus on menu and ingredient questions rather than running a parallel reservation channel that needs reconciliation.