No. The free Search & Filter plugin works entirely on standard WordPress tables. Taxonomies live in wp_term_relationships, wp_term_taxonomy, and wp_terms. Post fields used as filters live in wp_postmeta. The plugin reads those tables to build the form and to query results. That makes SleekAI's job straightforward, since the Wizard already supports the same standard schema.

Yes. The Wizard exposes the term-count and term-overlap functions over wp_term_relationships, so the system prompt can resolve questions like how many posts a single term has or how many posts two terms share. That lets the bot quote real counts rather than guessing, useful for narrow archives where a few posts vs many posts changes the visitor's next move.

Yes. The shortcode accepts post type, taxonomy, and custom field arguments that define which filters the form exposes. SleekAI does not interpret the shortcode itself, but the Wizard lets you map the same set of taxonomies and fields. As long as the bot knows which taxonomies the shortcode exposes, its answers stay aligned with what the visitor can actually filter by on the page.

Yes. Multibot mode runs several chatbots on one site with independent system messages, data sources, and display conditions. A common Search & Filter setup is one bot for the editorial archive and another for a course catalog, both coexisting under the same SleekAI install with their own taxonomy mappings and term-count functions exposed to the prompt.

SleekAI works with both free and Pro. The Pro version adds AJAX results, more field types, and S&F Cache. The underlying data still flows through standard WordPress tables, so the Wizard's mapping is the same. AJAX results just change how the grid refreshes on the page, not how SleekAI reads taxonomy or postmeta data on the chat request itself.

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 term-count questions and a stronger one for reasoning about intent across filter combinations under the same chatbot without changing the integration.

No. Search & Filter queries the database on form submission. SleekAI runs over a separate chat endpoint with bounded queries against term and postmeta tables. The chat widget is lazy and only initializes when the visitor opens it, so neither the initial archive load nor the form refresh round-trip is affected by SleekAI being installed and active on the same template.

Yes. The SleekAI JS API can read query-string parameters and pass them into the chat request as initial context. Since Search & Filter encodes selections as URL parameters by default, the bot knows which category, tag, or date range is active and can answer or suggest moves grounded in the visitor's actual filter state rather than speaking generically about the whole archive.