Dokan turns a WooCommerce site into a multi-vendor marketplace, and the Vendor Subscription module charges sellers a recurring fee in exchange for selling rights. Each pack is a WooCommerce product of type product_pack with postmeta like _no_of_product for product limits and _pack_validity for the renewal interval. Vendors ask the same questions on signup: which pack lets me list 100 products, how often does it renew, what happens if I cancel.

A generic chatbot has no idea any of that exists. SleekAI maps the product_pack meta and the vendor's current subscription state into named variables. The bot quotes the real product limit, the renewal interval, the renewal price, and the days remaining for a logged-in vendor. For prospects browsing the pricing page, the bot compares packs and recommends the right one based on the vendor's expected catalogue size.

Display conditions let a sales bot greet prospective vendors on the pricing page and a vendor-account bot answer subscription questions in the Vendor Dashboard. Both run side by side under multibot with their own system prompts, sharing the same data sources for consistency.

Marketplace operators sell two products at once. The marketplace itself and the right to sell on it. The latter is governed by Dokan's vendor subscription packs, and every vendor has the same handful of questions in both directions: which pack should I pick, how many products can I list, when does it renew, what happens if I cancel.

Generic chatbots cannot answer any of those because packs are stored as WooCommerce product_pack products with postmeta and each vendor's subscription state is on their user object and subscription record. A generic model has no view of either. SleekAI fixes the wiring with point-and-click data sources that map the pack meta and the vendor state into named variables.

The sales bot on the pricing page quotes real limits and renewals to prospects. The vendor bot in the dashboard quotes the logged-in seller's own renewal date and product count. Both reply with the same numbers the marketplace actually charges and enforces.

Every reply lands in the conversation log with the vendor ID, model name, and tokens used, which gives operators an honest view of vendor confusion and a feedback loop into the pricing page and the renewal email.