It writes back. Every drop updates the subscriber_status, confirmed_at, or unsubscribed_at column on the underlying WP Subscribers contact row, the same way the plugin's own UI does. There is no separate local table and no sync job. The card and the contact row are the same row, which keeps the kanban and the next newsletter send perfectly aligned.

Use subscriber_status for the primary lanes since it carries the exact lifecycle states WP Subscribers tracks. For richer hygiene boards, compose the group-by from subscriber_status plus a derived field that flags inactive contacts based on last_open_at older than ninety days so a Cold lane surfaces revival candidates.

Yes. Add a list_id filter to the kanban view so the board only shows contacts in that list. Save the filtered URL for each list and every list owner gets a focused board on their own contacts while the underlying WP Subscribers tables stay unified. A single subscriber on multiple lists shows up on each filtered board correctly.

The card moves to the Unsubscribed lane on the next board refresh or polling tick. The kanban reads from the same WP Subscribers contact row so every change made by the public unsubscribe link, the WP Subscribers admin UI, or the API shows up on the board without manual intervention. The card stays in sync with reality.

No. Double opt-in keeps working exactly as before. When a new subscriber lands in Pending the confirmation email is still triggered by WP Subscribers. The kanban just gives the list owner a faster path to manually confirm contacts that did not click for legitimate reasons like spam filters or already-engaged contacts using the same address.

Each lane paginates independently and only loads card data for the slice currently in view. The Confirmed lane lazy-loads on scroll, so a quarter million confirmed contacts sit comfortably in the column. The active hygiene lanes like Pending and Bounced stay fast because they only carry the small slice of contacts actively in lifecycle motion.

Yes. SleekView reads any SQL view, so you can join the contact table to a custom segments table or a postmeta key that stores moderation notes. The joined columns become available as card fields without modifying WP Subscribers itself, and writes can be selectively enabled on a field-by-field basis from the view config.

For day-to-day list hygiene work, mostly yes. The WP Subscribers admin still hosts list creation, form configuration, and template editing which live outside the kanban scope. Most list owners spend their daily time in the kanban for confirmation and hygiene work and only visit the WP Subscribers admin for monthly list and form configuration.