Akismet writes its verdict to the standard wp_comments table, setting comment_approved to spam, 0 (pending), or 1 (approved), and stamping wp_commentmeta with akismet_result, akismet_history, and the source IP. Each comment carries a content body, author name and email, a comment_post_ID, a comment_date timestamp, and the Akismet history showing why the comment was flagged. The default comments screen lists comments in a long sortable table grouped by status, fine for periodic moderation and weak when a lead runs a daily false-positive review.

SleekView reads the same wp_comments rows the moderation queue queries. Pick the comment_approved column as the grouping field and every comment becomes a card grouped under Pending, Spam, Reviewing, or Approved. Card fronts show the author, the comment excerpt, the originating post title, and the Akismet score from comment meta so a lead can prioritize false-positive checks.

Dragging a card writes the corresponding comment_approved value and stamps the Akismet history with the moderator's decision. A move from Spam to Approved flips the comment to live and feeds Akismet a training signal via the plugin's ham submission API.

Akismet catches the vast majority of spam comments before they reach the moderation queue, which is exactly what makes the small false-positive rate hard to manage. The default comments screen is great when an admin is approving a handful of genuine comments and almost useless when a lead is coordinating a daily false-positive review across hundreds of flagged comments. Most teams either ignore the spam folder entirely, missing the occasional legitimate question buried inside, or export it to a spreadsheet and tag false positives by hand.

The spreadsheet drifts within hours. New comments keep landing without a workflow tag, the spreadsheet records approvals nobody applies, and by the end of the day the two views disagree. A kanban view keeps the team and the source of truth aligned across the moderation cycle.