Yes. The bot reads your live WordPress menu posts at conversation time, so the moment you publish the new menu du marche or swap the plat du jour, the answers reflect the change. There is no retraining step and no risk of quoting last week's carte. For bistros that print a daily ardoise or rotate seasonal plats, this is the most useful capability on the page.

Yes. SleekAI replies in whatever language the guest writes in. A regular in Paris asking in French gets a French reply using your real plat names verbatim. A tourist asking in English gets the same plat names with translated descriptions, which keeps the spoken carte and the chat aligned when the guest sits down at the table.

Boeuf bourguignon, coq au vin, blanquette de veau, and cassoulet are quoted as you describe them on the page. If you note that the bourguignon uses Charolais shoulder or that the cassoulet follows the Toulouse method with duck confit and Tarbais beans, the bot repeats that detail. It will not invent a regional fact, so if a guest asks about a sourcing detail you have not specified, the bot suggests they ask the team.

Yes. If your wine list is published on the site, the bot reads it. It can recommend by region (Bordeaux, Burgundy, Rhone, Loire, Alsace), by grape, by price band, or as a pairing for a specific dish. It will not invent producers or vintages that are not on the list, so the recommendation is always something the sommelier can actually pour from the cellar.

The bot quotes the allergen note from the dish post, then recommends the guest confirm with staff before ordering. For nut-free, dairy-free, and gluten-free guests the answer is direct because most kitchens treat those clearly. For shellfish or rarer allergens like celery and mustard, the bot defaults to a confirm-with-the-team note so the guest gets a human check before service.

Yes. SleekAI supports multibot, so each bistro, brasserie, or hotel restaurant in the group has its own chatbot scoped to that kitchen's carte, wine list, and hours. Cross-location confusion, like a Lyon menu quoted at the Paris location, never reaches a guest. Shared brand-wide notes like the cancellation policy can sit in a shared knowledge layer used by every bot.

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 brasserie 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 and timing already in context. That keeps your booking data in one place, avoids creating a parallel booking channel, and lets the chatbot focus on discovery and qualification rather than calendar mechanics or table assignment.