Not by itself. SleekAI reads data that the Trustpilot WordPress integration has already brought into your install: TrustScore, review counts, widget settings, and any cached recent reviews. If a particular field is not surfaced by the plugin on your install, it is not available to the bot. The data-source wizard maps whatever the plugin exposes into the system prompt.

It depends on how the Trustpilot plugin caches data. Most integrations refresh the score and recent reviews on a schedule (hourly or daily) and store them inside WordPress. SleekAI reads the cached values at request time, so the bot reflects whatever the plugin most recently fetched, which is typically what your on-page widget is also showing.

If the Trustpilot plugin caches recent reviews as posts or option records inside WordPress, SleekAI can read them and the bot can paraphrase or quote them. You can also restrict the prompt to themes and aggregates rather than direct quotes, depending on how you want to balance specificity and reviewer privacy.

The bot reads whatever the plugin shows. If you would rather the bot describe a temporary dip in context (for example, after a launch incident) you can include a note in the system message explaining the cause and pointing to the resolution. The bot will acknowledge the dip and contextualize it honestly.

Yes. Display conditions match URL patterns, post types, taxonomies, and user role, so you can run the reputation-aware bot only on the pages where it makes sense: homepage, pricing, product pages, or a particular campaign landing page. Other pages can use a different bot or no bot at all.

The features available to the bot depend on which fields the Trustpilot plugin and your Trustpilot tier expose inside WordPress. Free plans typically expose TrustScore and counts, while paid tiers may expose richer review feeds. SleekAI works with whatever your tier surfaces, no extra account changes needed on the Trustpilot side.

BYO key with OpenAI, Anthropic, Google, and OpenRouter. Usage and billing stay on your provider account. A cheap fast model is usually enough for short reputation answers, and a stronger model can be wired in for the support bot that handles longer recovery conversations.

Inside WordPress, in tables managed by SleekAI. Every message is logged with the user, model, token usage, and the page URL it ran on. Reviewing those logs is a fast way to see which reputation-related questions matter most to visitors and to tighten either the bot prompt or the surrounding page copy.