WP Customer Reviews stores reviews as standard WordPress comments with custom comment_type and meta. Each review carries a star rating in commentmeta under the wpcr_qna or rating key (depending on version), an author name, and a moderation status managed through the WordPress comments queue. The plugin uses a per-page shortcode to render reviews, so the page where the form lives, the page's review count, and the average rating are all queryable from the comments tied to that post ID. SleekAI maps those structures through its data-source wizard so the system message exposes the active page's review count, average rating, and the most recent approved reviews as named variables.

That makes the conversation useful for service businesses. When a visitor asks how previous clients rated the service, the bot summarizes the most recent reviews instead of inventing testimonials. When a visitor asks how to leave a review, the bot reads the shortcode location for that page and links to the form. When the visitor is logged in and previously submitted a review, the bot can confirm whether it has been approved or is still pending moderation.

Display conditions scope the bot to service pages or testimonial pages, multibot lets a moderation bot run for admins in the WP comments queue, and conversation logs capture every message with model and token usage so the team refines prompts based on real visitor questions.

WP Customer Reviews powers reviews for thousands of service businesses precisely because it stays on the page where the shortcode lives. The questions visitors ask there are concrete. What do real clients say.

How do I leave a review. Is my submission live yet. A generic chatbot bolted onto a service site cannot see the comments tied to this page, has no idea where the form is, and ends up reciting either marketing copy or, worse, made-up testimonials that contradict the reviews right below the chat.

That contradiction is the start of trust loss at the exact moment a visitor is sizing up whether to book. SleekAI flips that. The bot reads the same comment rows the shortcode renders, so summaries match what's on the page.

Submission help points to the actual form below the reviews list, not a generic 'contact us.' Moderation status answers honestly because the bot reads comment_approved. Support teams stop forwarding the 'is my review live' question and start using the log to spot which service pages need stronger proof. Marketing sees which reviews come up most in chat and either pins them in the widget or builds case studies around them.

Because SleekAI never writes to the comments table, WP Customer Reviews stays the source of truth and moderation, spam checks, and schema output all execute through the standard WordPress flow. The bot summarizes and guides while WordPress and the plugin run the corpus. Combined with multibot, the same install can run a visitor bot on service pages and an admin moderation bot in wp-admin, both on an LLM key the business controls.