Only as far as you publish it. If your daily counter list is a custom field on the menu page, the bot reads it. For counters that change with the morning market, we recommend updating the field daily or marking specific items as 'subject to availability'. The bot will not invent a fish that is not on the page, which keeps answers honest even when the chef makes last-minute substitutions.

Yes. If your omakase course count, lead time, seating policy, and optional sake pairing are on the site, the bot quotes them. It can mention that the omakase follows the chef's choice based on the day's market, that there is a 48-hour cancellation rule, and that the sake pairing is poured by your sommelier. It then routes the guest to your reservation form with party size and date in context.

Standard soy sauce contains wheat, and the bot relays that explicitly. If your counter keeps gluten-free tamari for celiac guests, the bot quotes which preparations can use it: nikiri brush, table soy, ponzu replacement. Tempura batter and panko coatings are wheat-based and not gluten-free. For severe celiac, the bot routes to confirm with the chef so the brushes and stations can be set aside.

Yes. SleekAI replies in whatever language the guest writes in. Japanese-speaking guests get answers in Japanese with your real fish names in kanji or romaji, depending on how you publish them. English-speaking tourists get translated descriptions. The chat answer uses the menu's exact dish names so the printed menu and the chat line up when the guest arrives at the counter.

If your menu has a cooked-only section (anago, tamago, ebi, vegetable maki, agedashi tofu), the bot quotes it. For pregnant guests asking about raw fish safety, the bot offers the cooked options and recommends confirming with their doctor. It will not give medical advice. For mercury concerns in tuna, it relays what your menu page says and otherwise points the guest to their own doctor.

Yes. SleekAI supports multibot, so each sushi restaurant in the group runs its own chatbot scoped to that counter's fish list, omakase, and hours. A high-end omakase counter and a casual sushi-roll location each get their own bot with appropriate tone and menu scope. Shared brand items like the loyalty program and cancellation policy 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 usage cost is just model tokens, typically a few cents per conversation. For a busy sushi restaurant doing 200 chats a day on GPT-4o-mini, the monthly run cost stays well below per-location chatbot SaaS pricing.

SleekAI does not connect directly to reservation systems. The bot deep-links to your TableCheck, OpenTable, Resy, SevenRooms, or custom reservation page at the right moment in the conversation. For takeaway and chirashi orders, it links to your ordering page on Toast, ChowNow, or your custom WooCommerce flow. The chatbot answers questions and routes intent while booking capture stays in your existing systems.