The PeepSo Chat add-on layers messaging on top of PeepSo's core tables. Threads land in peepso_chat_threads with participants stored as a joined row per participant, and messages live in peepso_chat_messages with thread_id, sender_id, content, and date_sent. Profile data for both sides lives in PeepSo's peepso_users joined to wp_users.

The default PeepSo Chat admin handles threads as a flat list, but cross-thread message audit (every message from a flagged account in the past 7 days, every unread thread older than 30 days for cleanup) needs direct SQL. Filtering by sender profile fields combined with message recency isn't a built-in screen.

SleekView reads the chat tables directly, joins both sides' PeepSo profiles, and exposes thread state, message content preview, and per-user message volume as proper columns. Inline edits flag messages or delete them with conflict detection; routes through PeepSo's chat API where exposed so any registered handlers fire.

Private chat is where moderation is hardest because almost nothing is visible until a complaint lands. A community can run for months without anyone reading what's actually happening in DMs, and then an abuse report arrives and the question is the same every time: what else has this account sent, when, to whom. The default PeepSo Chat admin can answer that one thread at a time, which is the wrong unit of work.

The data exists, because every message row has sender, thread, recipients via the participants table, content, and timestamp. The gap is composition. SleekView's pivot turns chat into a flat moderation table where sender profile fields join onto the message row and per-user volume rollups expose spike accounts before complaints arrive.

Moderators get the live abuse queue, support gets the per-user investigation surface, community managers get the volume rollup for advocacy programs. For any community running PeepSo Chat at real scale, that's the operational difference between catching abuse early and learning about it from churn.