It actually sends. When a card lands in Scheduled, SleekView calls the SmartrMail API with the new schedule time and the broadcast queues for delivery. When a card moves to Sending the broadcast starts processing on SmartrMail. The local mirror table and the SmartrMail account stay in sync because the same drag both writes locally and fires the API.

Use campaign_status for the primary lanes. That mirrors the four real states SmartrMail tracks for broadcasts: draft, scheduled, sending, and completed. If you also run automations, split them into their own board grouped by automation_status so broadcast and automation pipelines stay legible without one drowning the other.

Yes. Each SmartrMail store maps to a separate WordPress site or to a filterable store_id field on the campaign mirror. Add a store filter to the kanban view and the board scopes to that store. Save the filtered URL for each store and the team running each shopfront gets their own focused board.

Nothing harmful. SleekView reads native WordPress capabilities and you set which roles can drop into which lanes. For writers and editors the Sending lane behaves as a non-drop target and the card snaps back to its previous lane. You can also require a typed confirmation for that specific lane to add a second guardrail.

No. The kanban writes only the campaign_status and scheduled_at fields that SmartrMail already updates from its own dashboard. Open, click, and revenue tracking continue to run inside SmartrMail exactly as before, and the revenue numbers on completed cards are read from the same source the SmartrMail analytics page uses.

Each lane paginates independently. The active lanes carry only a small number of in-flight broadcasts so they always render instantly, while the Completed lane lazy-loads as you scroll. A two-year archive of historical sends sits comfortably in the Completed column without slowing the boards used for daily pipeline work.

Yes. SleekView reads any SQL view you point it at, so you can join the campaign mirror to a custom approvals table, a postmeta key that stores the assigned editor, or a planning sheet imported via WP-CLI. The joined columns appear as card fields without modifying SmartrMail itself and writes can be enabled selectively per field.

Yes. The kanban config stores column references against logical SmartrMail field names, not row IDs, so when the mirror table refreshes the same lanes still render against the new rows. Plugin updates that add new SmartrMail states show up automatically as new lanes the first time a campaign in that state lands in the mirror.