Yes, as long as you tag fasting items on each menu post. SleekAI reads those tags and surfaces the beyaynetu, shiro, misir wat, gomen, and atkilt without guessing. For Lent or any seasonal fasting week, you can add a note to the menu page and the bot picks it up immediately. There is no retraining step. The bot also handles 'is this dairy-free' style follow-up questions from the same tags.

Yes. SleekAI quotes the published descriptions on your menu posts and adds brief, plain-language context (what injera is, how mesob platters are shared, whether to use hands or cutlery). The tone is set by your system prompt, so a Brooklyn spot can sound playful while a fine-dining Addis-style place stays formal. Guests learn enough to order confidently without feeling lectured.

SleekAI only repeats allergen info you have already published on each menu item. We recommend listing common allergens (peanut, sesame, dairy, gluten) on every dish so the bot can quote them. For severe allergies the bot defaults to recommending the guest confirm with staff before ordering, which is the safe behaviour. Pure-teff injera is gluten-free; mixed-flour versions are not, and the bot will say so if your page says so.

Yes, any language the underlying model supports. Guests writing in Amharic, Tigrinya, French, or German get a reply in that language using your English menu page as the source. Dish names keep their canonical Amharic transliteration so guests can match the spoken or chatted answer to the printed menu without confusion.

SleekAI does not book tables itself, but it links guests to your existing reservation system at the right moment, OpenTable, Resy, SevenRooms, Tock, or a WooCommerce Bookings form. Party size, requested time, and dietary mix get carried in the link or transcript so the host stand has full context. Bookings stay in one system, not split across email and chat.

SleekAI is a one-time WordPress plugin licence. You bring your own OpenAI, Anthropic, Google, or OpenRouter API key, so usage is just the tokens, typically a few cents per conversation on a gpt-4o-mini or claude-haiku class model. Compared to monthly per-seat restaurant chat tools, the total cost stays small even on Saturday-night peaks.

Yes. Multibot supports running a separate chatbot per location, each scoped to its own menu, hours, address, and live music calendar. A planner asking about a downtown location does not get suggestions from the suburb branch and vice versa. Display conditions can scope each bot to the right URL prefix or page template automatically.

Yes. The system prompt sets the voice, and you can feed example replies from past emails or social posts so the bot matches the cadence of the house. Some restaurants want a warm, didactic host who teaches guests about Ethiopian food; others want a brisk, modern Addis-bistro tone. Both work; the bot stays accurate either way because the facts come from your menu posts.