FluentCRM stores email campaigns and broadcasts in fc_campaigns and the linked fc_campaign_emails queue, each carrying a status value drawn from draft, scheduled, processing, sent, paused, and archived. The default admin gives you a list view with status tabs, which works for editing one campaign but never shows the shape of the send queue at a glance, especially when a busy account is juggling broadcasts, sequences, and triggered emails in parallel.

SleekView reads the same campaign rows and the per-recipient fc_campaign_emails log. The natural status column is status on the campaign record, with the schedule time, the recipient count, and the open rate on completed sends surfaced as card metadata. The board can also be retargeted at the per-email queue when the marketing team needs to triage rows that failed to dispatch instead of looking at campaigns in aggregate.

Dragging a card calls the FluentCRM campaign API to schedule, pause, or archive a campaign, so the in-flight send queue and any linked automation funnels stay in sync. The board respects the same staff capability checks as the FluentCRM admin, and a failed write snaps the card back with the underlying validation message displayed inline so the operator can see exactly why a state change was rejected by the plugin.

FluentCRM is a sending pipeline built on top of WordPress, and the campaigns it stores are stateful records in the truest sense. A campaign moves from draft to scheduled to sending to sent, and the marketing team thinks about its work in terms of where the active broadcasts are in that lifecycle. The default admin presents campaigns as a tabbed list, which is fine for editing one row but hides how the send pipeline looks across all the running work.

A weekly send calendar review on a tabbed list turns into clicking each tab in turn and counting rows, and the team usually gives up and exports the campaigns to a spreadsheet just to get an overview. With SleekView Kanban the campaign pipeline is the interface. The status of every broadcast is visible at a glance, drag-and-drop writeback means a pause or a reschedule is one motion, and the underlying FluentCRM hooks fire exactly as they would in the standard admin so the campaign automations and recipient queues all stay healthy.