Yes. Each cocktail post stores its full ingredient list, allergen tags (egg white, nut, coconut, dairy), and dietary flags. "No coconut, low sugar, rum-forward" returns the cocktails where all three constraints are true on the post, not items where the description happens to not mention coconut. Cross-contamination notes ("shaker is shared") read the same way if you've stored them.

Yes. Group bowls store recommended party size, base spirit, sweetness, theatrical element (fire pour, dry ice, lit garnish), and price. The bot recommends by party size and intent (birthday energy gets the Volcano Bowl, low-key date night gets the Treasure Chest for two), then notes presentation and ordering rituals. Allergens on bowls work the same way as on individual cocktails.

Yes. Mug club perks (15% off cocktails, free birthday cocktail, exclusive menu releases, personal mug stored at the bar, members-only events) live as policy fields. The bot quotes the perks accurately to members and gives non-members the sign-up link with the perk list. Tier-based clubs (silver, gold, founders) have their own perk fields if you have multiple tiers.

Yes. Birthday parties, bachelor or bachelorette parties, retirement parties, and corporate buyouts route to the events coordinator. The bot captures party size, date, signature bowl preference, dietary constraints, and any theme requests in chat, then forwards. The captured brief means the coordinator's first reply is already informed.

Yes. Friday Aloha Nights, Sunday luaus, fire-show schedules, and themed-cocktail pop-ups live on the events calendar with start time, special menu, cover (usually none), and dress code (usually optional tropical). The bot quotes the right event for the requested date and surfaces any special pricing or food pairing tied to the night.

Yes, in a measured way. Each signature cocktail can store a short origin or backstory field (the bar's own twist on the Mai Tai, the Donn Beach inspiration), and the bot quotes the stored text rather than inventing history. For canonical tiki cocktails with well-documented origins, the bot can quote the stored backstory in the bar's voice without making up source material. Wikipedia-style claims are kept out unless they're in your field.

Yes, with multibot. Some tiki operators run a downstairs tiki bar and an upstairs speakeasy, or a tiki room and a separate rum library. Each concept can run its own bot scoped to that menu, that events calendar, and that dress code. Guests on the tiki page see tiki cocktails; guests on the speakeasy page see classic cocktails. The two bots don't bleed into each other.

Yours. SleekAI is BYO API key, so you bring an OpenAI, Anthropic, Google, or OpenRouter key and the model bills you directly. There's no per-message markup. A single tiki bar usually spends $10 to $30 a month in API usage. The cocktail-history questions benefit slightly from a stronger model, so some operators step up to GPT-4o or Claude Sonnet for the menu-Q&A portion while keeping cheaper models for routine intake.