Yes. SleekAI reads WooCommerce stock data live, so it only recommends variations that are available. If size 38 charcoal is in stock but 36 has sold out, the bot does not pretend otherwise. For shoppers in the wishlist mindset, it can flag 'size 36 is currently sold out, want me to note your interest?' instead of inventing availability.

Yes. SleekAI supports multiple bots, each with its own system prompt, knowledge base, and display conditions. Menswear runs on /men/ with a different tone and a different sizing reference. Womenswear runs on /women/. Sale runs on /sale/ with cross-sell turned off. The 28+ display conditions handle the routing - no custom code required.

Yes. Upload PDFs or text files into the OpenAI Files vector store and the bot retrieves the relevant section during a conversation. Brand-by-brand sizing tables (Acne runs large, Toteme runs true-to-size) are common - the bot pulls the row that matches the brand the shopper asked about, not a generic EU-to-US conversion.

Yes. SleekAI was built around WordPress, so any product CPT including WooCommerce slots in via display conditions and context fields. Variations, attributes (size, color, material), stock status, and price all feed into the prompt automatically. Custom fields like 'fit notes' or 'season' can be added to the context bundle as needed.

Yes. Every conversation is logged in WordPress so you can spot popular questions, sizes you do not stock that shoppers ask for, and gaps in your catalog. If 30 shoppers in a month asked for petite blazers on a brand you only stock in regular, that is a buying signal - not just a service log.

Your own. SleekAI is bring-your-own-key for OpenAI, so you keep full control over costs, model choice (GPT-4.1, GPT-4o, GPT-4o-mini), and data. Usage hits your OpenAI account directly. There is no per-message markup or platform fee on top of the API cost.

Yes. If your size guides include cross-region tables, the bot resolves a shopper's stated size into the brand's sizing convention. EU 38 to UK 10 to US 6 is a typical conversion; Japanese brands often size differently and the bot follows whatever your guide publishes rather than guessing.

If your products carry a custom field for arrival date or pre-order status, the bot surfaces that. A shopper looking for the next Lemaire drop can hear 'the spring drop arrives April 30, want me to flag your email?' instead of getting a generic 'we will email when available' line that goes nowhere.