WC Vendors exposes the current vendor on store templates through query vars and on product pages through post_author. SleekAI reads either signal and loads that vendor's usermeta into the system message. On neutral pages like the homepage or category archives where no specific vendor is active, the bot falls back to a marketplace-wide context.

Yes, on the vendor-facing side. WC Vendors stores commission rows in its own table tied to WooCommerce orders. SleekAI can pull commission status, pending balance, and last payout date into a vendor-dashboard bot, scoped by user role and dashboard URL so only the logged-in vendor sees their own numbers.

Yes. Pro adds extended store features and dashboard widgets but stores data through the same usermeta and table layer. SleekAI reads those fields like any other source. There is no version lock, the bot integrates with whichever WC Vendors version your marketplace is running on.

Yes, with operator approval. Run a multibot setup where each per-vendor bot has its own system prompt, and expose a vendor-side editor that updates only that vendor's prompt template. The marketplace operator can review changes before they go live to keep the brand consistent.

WC Vendors lets each vendor set their own shipping methods, rates, and zones. SleekAI reads the active vendor's shipping config into the prompt so a buyer's shipping question returns that vendor's rate, not a marketplace-wide flat rate or a vendor-averaged figure that is wrong for everyone.

Each vendor can have a small FAQ block included in their bot's system message, covering their processing time, packaging notes, and return window. When the vendor updates their store profile, that update flows into the prompt automatically through the data source mapping, no separate sync needed.

Yes. When a question goes beyond the bot's confidence threshold or matches an escalation pattern, the bot can describe the handoff and trigger a webhook that emails the matching vendor through WC Vendors' contact form or a custom queue. The bot does not message vendors directly, escalation routes through your normal contact infrastructure.

Yes for read context. The bot can reference whether a vendor has connected their Stripe account, when their last payout was scheduled, and whether their store is active for sales. It does not write to Stripe, all payout actions stay in the vendor dashboard, but the bot can answer the common payout-status question without an operator stepping in.