Yes. The bot reads your live WordPress menu posts at conversation time, so the limited shoyu-aji weekend special or the seasonal miso shows up the moment you publish it. There is no retraining and no manual sync. For shops that run one or two daily specials alongside the standing menu, the bot can answer specifically about each one without quoting yesterday's broth.

Yes. SleekAI replies in whatever language the guest writes in. A Japanese-speaking guest gets a Japanese reply using your real bowl names verbatim. An English-speaking guest gets the same bowl names with translated descriptions of broth and toppings. This is useful for shops in cities with large Japanese expat communities or strong tourist traffic where regulars and first-timers mix.

If you tag a bowl as vegan or vegetarian on the menu post, the bot reads that tag and quotes the broth (kombu-shiitake, miso, vegetable) and toppings. It will not claim a tonkotsu can be made vegan, because pork-bone broth cannot be adapted. For shops that run only one or two plant-based bowls, the bot can recommend topping additions that round out the bowl without overstating the menu.

Yes. If your policy is walk-in only with typical queue times by daypart published on the site, the bot quotes that. It can answer 'is it busy at 7pm Saturday' with your real estimate. For shops that take reservations on specific nights or for groups above a threshold, the bot quotes that policy and hands off to your booking form when the request matches the criteria.

Most ramen noodles contain wheat, so the bot quotes that clearly. Some broths contain soy sauce with wheat (most shoyu does), so the bot flags which bowls can be made gluten-free. It defaults to a confirm-with-the-team note for celiac diners, because cross-contamination on the noodle line is hard to rule out in a shop running standard wheat noodles all day.

Yes. SleekAI supports multibot, so a flagship and three express locations each have their own chatbot scoped to that shop's menu, hours, and queue policy. Cross-location confusion, like the flagship's tsukemen menu quoted at an express shop that does not serve it, never reaches a guest. Shared brand-wide notes like the broth process 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 shop doing 200 chat conversations a day on GPT-4o-mini, that runs well under what a per-location SaaS chatbot subscription would charge.

SleekAI does not place orders on Uber Eats, Deliveroo, or your own takeout system. It links the guest to your existing ordering page at the right point in the conversation, with the bowl already chosen if the guest specified one. That keeps order data in one place and lets the chatbot focus on bowl recommendation and policy questions rather than running a parallel order channel.