REVIEWS.io is a SaaS reviews platform. The WooCommerce plugin caches each product's REVIEWS.io score and review count as product postmeta (typically under keys like _reviewsio_score and _reviewsio_count), refreshed via a scheduled sync or webhook. The plugin also stores the per-order review-collection state and the merchant's overall trust score in plugin options. SleekAI maps those values through its data-source wizard so the system message exposes the active product's REVIEWS.io score, the merchant's overall rating, and the customer's review status as named variables resolved at request time.

That gives shoppers consistent answers. When a visitor asks the product's REVIEWS.io rating, the bot quotes the cached score with a freshness note and points to the widget for individual reviews. When a customer asks why they got a REVIEWS.io email after an order, the bot reads the collection log for their order and explains the schedule. When they ask if their review is live yet, the bot reads the collection status and gives a clear answer instead of an evasive maybe.

Display conditions scope the bot to product pages or the order dashboard, multibot lets a separate prospect bot answer trust-mark questions on the homepage, and conversation logs capture each message with model and token usage so the team refines prompts and the sync cadence based on real friction.

REVIEWS.io carries trust because it verifies orders and runs the collection itself. The questions that show up on a product page are precise and personal. What's the score.

Are these real customers. Why did I get a review email after my order. A generic chatbot bolted onto a WooCommerce store cannot read the cached REVIEWS.io postmeta, has no idea what the merchant trust score is, and ends up either ignoring REVIEWS.io altogether or, worse, quoting a different number than the widget right next to the chat.

That contradiction undermines the very trust REVIEWS.io exists to provide. SleekAI fixes that by reading the same cached values the widget reads. Product scores match.

Merchant scores match. Email timing gets explained against the actual collection schedule, not as a mystery. Review-status questions get answered against the collection log instead of an evasive 'check your email.' Support teams stop fielding the same five questions every Monday and start using the log to tune the sync cadence or the email copy where the bot felt confused.

Because SleekAI never writes back to REVIEWS.io, the platform stays the source of truth and verification, moderation, and reward issuance all execute through REVIEWS.io's normal flow. The bot summarizes and guides while REVIEWS.io runs the corpus. Combined with multibot, the same install can run a homepage bot for prospect trust questions, a product-page bot for score answers, and an account bot for collection-log questions, all on an LLM key the merchant controls and pays for directly.