Mostly no. Both versions store taxonomy filters in wp_term_relationships and field filters in wp_postmeta. The Pro version adds a search-filter-widget custom post type for storing each configured form. SleekAI's Wizard reads from the standard tables, and the Pro form's CPT is only used to look up which fields a specific form exposes, not as a primary data source for chat answers.

Yes. Search & Filter Pro exposes a JS object that reflects current selections in real time. The SleekAI JS API reads that object and includes the active selections in the chat-request context, so when the visitor refines a filter, the bot's next answer is grounded in the new state immediately without waiting for a URL change or a full archive refresh.

S&F Cache pre-caches result grids for common filter combinations to speed up the visible archive. SleekAI runs on a separate chat endpoint and reads taxonomy and postmeta directly, so the cache does not affect chat correctness. Stale cache entries that show outdated count badges in the form will be quietly corrected by the bot's answers, which always reflect the live database.

Yes. The Wizard joins taxonomy and postmeta lookups, so the system prompt can resolve questions like how many products from a given brand fall under a given price. That mirrors what S&F Pro's own count badges on the form show on the active facets, so the bot's answers stay aligned with the badge numbers the visitor sees on the archive.

Yes. Multibot mode runs several chatbots on one site with independent system messages, data sources, and display conditions. A common S&F Pro setup is one bot per archive template, each with its own field mappings and prompt language tuned to the catalog type, all coexisting under the same SleekAI install on the same site.

Yours. SleekAI is bring-your-own-key, so message costs are billed directly by your provider with no SleekWP markup. Use OpenAI, Anthropic, Google, or OpenRouter, and pick a fast model for routine count questions and a stronger one for complex reasoning about intent across filter combinations under the same chatbot without changing the integration.

No. Search & Filter Pro's AJAX call hits its own endpoint. SleekAI runs on a separate chat endpoint with bounded taxonomy and postmeta queries. The chat widget is lazy and only initializes when the visitor opens it, so neither the initial archive load nor the AJAX refresh round-trip is affected by SleekAI being installed and active on the same archive template.

Pro has a separate posts shortcode for rendering filtered results outside the form template. SleekAI does not need to parse the shortcode itself. As long as the Wizard knows the taxonomies and fields the form exposes, the bot can answer about the underlying data the shortcode renders, regardless of how or where you place the results loop on the page.