Follow-Up Emails registers each automation as a follow_up_email CPT, writes queued sends to wp_followup_email_queue, archives delivered sends to wp_followup_email_sent and stamps open and click rows into tracking tables. The default surface is a per-campaign report tab, which is right for opening one automation and wrong for cross-campaign moderation, deliverability triage or queue audits.

SleekView reads the queue and sent log directly and renders the rows as a queryable audit table. Filter to pending rows older than an hour to find stalled sends. Filter to one trigger type (order, signup, subscription) to scope a deliverability review. Sort by recipient to spot a customer getting hit by too many automations at once. The same dataset the chart view aggregates becomes a row-level surface for marketing ops, deliverability and compliance.

The plugin keeps owning the cron worker, the triggers and the message rendering. The table view owns the audit surface, so the queue and sent rows Follow-Up Emails already writes stop hiding behind report tabs and become something the team can actually query.

Follow-Up Emails captures every queued and sent message with the campaign, the trigger, the recipient and the timestamp, but the default UI hides those rows behind per-campaign report tabs. That is right for opening one automation and wrong for the cross-campaign questions marketing ops actually asks. SleekView reads the same queue and sent log rows and renders them as a queryable audit table with campaign name, trigger type, status and send_date as first-class columns.

Filters stack into a single query so the stalled-queue audit, the per-recipient over-emailing list and the per-trigger compliance cohort become saved views rather than spreadsheet exports. The plugin keeps owning the cron worker and the message rendering, while marketing ops gets the per-row surface the dataset always deserved.