Yes. The bot reads your live WordPress menu posts at conversation time, so the moment you publish the autumn truffle menu or swap a primo, the answers reflect the change. There is no retraining, no manual sync, and no risk of quoting last week's dishes. For trattorie that change the menu weekly or run nightly specials, this is the most useful feature on the page.

Yes. SleekAI replies in whatever language the guest writes in. If a guest in Milan writes in Italian, the bot answers in Italian using your real menu names verbatim. Tourists in English-speaking cities still get the same dish names with translated descriptions, which keeps the spoken menu and the chat aligned when the guest arrives.

Cacio e pepe, amatriciana, and orecchiette con cime di rapa are quoted as you describe them on the page. If you note that the cacio uses Pecorino Romano DOP or that the pasta is made with semolina from Gragnano, the bot repeats that detail. It never invents an Italian regional fact, so if a guest asks where the Parmigiano comes from and 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 (Tuscany, Piedmont, Sicily), by grape (Sangiovese, Nebbiolo, Nero d'Avola), by price band, or as a pairing for a specific dish. It will not invent vintages or producers that are not on the list, so the recommendation is always something the sommelier can actually pour.

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 rare allergens like sesame, the bot defaults to a confirm-with-the-team note so the guest gets a human check on the line before service.

Yes. SleekAI supports multibot, so each trattoria, osteria, or pizzeria in the group has its own chatbot scoped to that kitchen's menu, wine list, and hours. Cross-location confusion (Milan menu quoted at the Rome 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 restaurant doing 200 chat conversations a day on GPT-4o-mini, that is well under what a per-location SaaS chatbot subscription would charge.

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.