Yes, if your sake and bar list is on the site. The bot reads it and can recommend by category (junmai daiginjo, junmai ginjo, honjozo), by rice polish ratio, by region (Niigata, Hyogo, Akita), or as a pairing for a specific dish. For whisky, it handles Japanese single malts, blends, and highballs. It will not invent producers or vintages that are not on the list.

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

Soy sauce contains wheat in most cases, and the bot relays that explicitly. If your kitchen keeps tamari for gluten-free guests, the bot quotes which dishes can use it. Tempura batter is wheat-based and not gluten-free; the bot recommends grilled fish, sashimi, donburi without tempura, or the gluten-free ramen if you offer one. For severe celiac, it routes to confirm with the kitchen.

Yes. If your omakase menu, course count, lead time, and seating policy are on the site, the bot reads them and quotes them. It can mention that the chef's choice depends on the day's market, that there is a 48-hour cancellation rule, and that the omakase is best paired with the sake flight. It then routes the guest to your reservation form with party size and date in context.

Traditional dashi often uses katsuobushi (bonito) and sometimes niboshi (sardine), which are not strictly shellfish but matter for pescatarian and severe-fish-allergy guests. If your kitchen offers a kombu-only or kombu-shiitake vegan dashi, the bot quotes it. For severe shellfish allergies, the bot routes the guest to confirm with the kitchen, since cross-contamination in busy ramen and sushi lines is hard to fully eliminate.

Yes. SleekAI supports multibot, so each Japanese restaurant in the group runs its own chatbot scoped to that kitchen's menu, broth program, and sake list. A specialised ramen-ya bot at one location reads only its ramen and izakaya menu; a sushi-focused sister location uses its own bot scoped to its omakase and a la carte sushi. Shared brand items 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 ramen-ya or izakaya doing 250 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 POS or reservation systems. For online ordering, the bot deep-links to your ordering page on Toast, ChowNow, Uber Eats, or your custom WooCommerce checkout. For reservations it links to OpenTable, Resy, SevenRooms, TableCheck, or your form. The chatbot answers questions and routes intent while the booking and order capture stays in the systems your team already uses.