No. The verified-buyer flag is stored in wp_commentmeta by CusRev when a reviewer is matched to a completed order, and SleekView only reads that meta to render the badge on the card. The CusRev matching logic, the reminder-email scheduler, and the verification rule all keep running exactly as they did before the kanban view was added.

SleekView issues an update on the wp_comments row for that comment_ID, setting comment_approved from 0 to 1. WordPress fires the standard wp_set_comment_status hook, so any CusRev or WooCommerce listeners that respond to review approval (like the rich-snippet rebuild) trigger automatically. Nothing else is rewritten.

Yes. comment_approved has four canonical values (0, 1, 'spam', 'trash') and SleekView renders one column per distinct value found in the filtered result set. You can hide a column with a toggle if your workflow does not use it, for example collapsing Trash on the day-to-day moderation board.

Yes. Akismet still runs at submission time and marks suspicious reviews with comment_approved = 'spam'. Those rows land in the Spam column automatically. Dragging a card back to Approved updates the row and your Akismet decision history through the comments-edit path WordPress already exposes.

Yes. The board respects SleekView's column filters, so you can scope by comment_post_ID for a single product, by comment_date for a date range, by rating (a CusRev meta key) for high-rating-only triage, or by verified flag for a verified-only curation pass.

It does on stores where the rich-snippet pipeline listens to comment_status transitions, which is the default CusRev wiring. SleekView fires the standard WordPress comment-status hook on every drop, so any plugin that hooked into that transition (CusRev included) reacts the same way it would to a moderation action in the comments admin.

The Table view keeps the checkbox bulk-action workflow for cases like 'approve all verified buyers with rating 5 from last week'. The kanban view is for incremental moderation across the day where dragging single cards is faster than scoping a bulk action. Both views read and write the same wp_comments rows.

Yes. When the optional audit log is enabled, every drag write is recorded with moderator, old state, new state, and timestamp in a SleekView log table. The table is exposed as a SleekView data source like any other, so you can render it in Table view, filter by moderator or date, and export to CSV for compliance handover.