WP Customer Reviews stores every review as a WordPress comment in wp_comments with a special comment_type of wpcr3_review. Each review carries a comment_approved column with values 1 for approved, 0 for pending, spam, and trash, plus metadata in wp_commentmeta for the star rating, the review title, the author location, and the linked product or page. The plugin's review admin shows everything as a flat list, which is fine for archive lookups but blind to the live moderation work the support team actually does every day.

SleekView Kanban reads the same review comment rows you would query with WP_Comment_Query filtered to the wpcr3_review type. Pick comment_approved as the group column and every review becomes a card slotted under Pending, Approved, Spam, or Trash. Card fronts show the author name, the star rating from commentmeta, the review title, a short snippet of the review text, the linked product or page, and the date submitted, so moderators see the shape of every review at a glance.

Dragging a card between columns calls wp_set_comment_status with the new value, which writes back to wp_comments.comment_approved and fires the matching transition_comment_status hook. The product page review widget refreshes for the storefront, schema markup updates for SEO, and any extension listening for moderation changes reacts, exactly as it would after a manual approval from the WordPress comments admin screen.

Storefronts running WP Customer Reviews often receive dozens of reviews every day. Some are glowing five-star reviews that should publish as soon as the moderator confirms they are real. Some are detailed honest reviews that deserve a personal response from customer service.

A steady stream are spam, off-policy rants, or one-star reviews that need careful handling before they go live. The default review admin treats them all the same, which means moderators spend hours scrolling through long lists trying to triage what needs attention versus what is fine. The disconnect between what customers submit and what moderators can act on shows up in the worst places.

A five-star review sits Pending for a week because nobody noticed it. A one-star review goes live without anyone reaching out to the customer to resolve the underlying issue. A piece of spam gets approved by accident and pollutes the product page review widget.

A kanban view that reads and writes the same wp_comments rows the storefront reads keeps the team and the moderation queue honest. Every drag is a real status change, every column count reflects the real review pipeline, and the cards themselves carry enough context for a new moderator to clear the Pending queue on their first morning at work.