SleekView writes through the same WordPress functions where possible, so SendPress filters and actions still fire on supported edits. List membership changes, status updates, and metadata edits flow through the plugin's own write paths. Direct table writes are reserved for fields that have no plugin function, like internal notes.

Yes. The queue table joins to the subscribers table so you can see who is next in line without leaving the view. While SendPress works through the dispatch, refreshing the view updates the queue position. The pending count drops in real time as sends complete and move from queue to history.

Yes. SendPress installs per site, each with its own wp_sendpress_* tables, and SleekView opens those per-site tables with no cross-site leakage. A network admin can switch between sites and see only the subscribers and sends that belong to the site currently selected. There is no aggregated view across sites.

Yes. Filter to bounced, click export, and the result is a CSV of exactly those rows with the columns you have visible. The export respects the active filter, so a one-week bounced view exports just one week of bounced subscribers, ready for cleanup in a third-party suppression list or your inbox provider's complaint dashboard.

Yes. Pro features write extra columns into the same tables, and SleekView surfaces them like any other column. Premium add-ons that add their own tables can be joined in too, giving you a single grid that covers the free plugin and the Pro extensions without juggling separate admin screens.

Not exactly. The reports page stays for graphs and aggregate stats. SleekView is the row-level data the reports roll up from. The two are complements: reports tell you the campaign achieved a 32 percent open rate, SleekView tells you which 32 percent and lets you extract them as the engaged segment for the next send.

SleekView paginates and indexes server-side. Lists with hundreds of thousands of subscribers stay responsive because each query reads only the visible page. Sorting and filtering use database indexes, not in-memory operations, so the cost stays bounded even on long-running newsletter installs with years of subscriber history.

SleekView row actions can call any registered WordPress hook, so if SendPress exposes a test-send action, you can wire it up. The action then runs through SendPress's own dispatch path. The view itself does not generate or send emails, only triggers what SendPress already supports.