WCFM exposes the current vendor through query vars on store templates and through product authorship on single product pages. SleekAI reads the active vendor on each request and loads that vendor's wcfmmp_ usermeta and product set into the system message. Neutral pages like the homepage fall back to a marketplace-wide context with no vendor specifics.

Yes, scoped to the logged-in vendor. WCFM stores commission rows in its own table tied to WooCommerce orders, plus payout records under usermeta. A dashboard-scoped bot can quote pending balance, last payout date, and next scheduled withdrawal so a vendor doesn't need to drill into separate reports for routine questions.

Yes. SleekAI's multibot mode runs separate bots on the same site, each with its own system prompt and data sources. A common topology is a buyer bot on storefronts and category pages, a marketplace bot on the homepage and search, and a vendor bot scoped to the WCFM dashboard URL pattern with seller-only data sources.

Yes. The single-vendor mode shares the same data layer as the multi-vendor build, so SleekAI's mappings work the same way. In single-vendor setups the bot can lean harder on the one vendor's tone, since you do not need to switch context across storefronts and the multibot toggle stays off.

Each of those modules stores its data in standard WordPress and WooCommerce structures plus WCFM-specific meta. SleekAI's wizard can map those fields like any other source, so a bookings vendor can have a chatbot that quotes the right slot availability and a subscriptions vendor can describe the actual plan and renewal date.

Inside WordPress, with message history, model name, token usage, and the page URL stored per conversation. Operators can filter by URL prefix to see one vendor's chats at a time. Vendors do not get raw log access by default, which protects buyer privacy while keeping marketplace-level QA possible.

Yes, that pattern is common. Run multibot with per-vendor system prompts and let the marketplace operator gate which vendors get a custom prompt as a paid feature. The shared marketplace bot stays free, and premium vendors get a tailored prompt with their tone of voice and FAQ block under the same SleekAI install.

No, when configured correctly. The system message should only load the active vendor's context on storefront pages, and the marketplace-wide fallback should not paste the full vendor list. For order and commission data, the bot only reads records belonging to the logged-in user, so a customer cannot retrieve another customer's sub-order through the chat.