WebinarPress stores webinars as a WordPress custom post type with registrant records, attendance flags, and traffic source captured alongside each event. The default admin gives every webinar its own registrants screen, its own attendance toggle, its own follow-up tagging. For a single launch that view works. For a recurring demo plus an onboarding cadence plus a quarterly launch series, the cross-event list is what the team actually reads.

SleekView reads the same data WebinarPress already writes. Webinar title, scheduled date, status, registrant count, attendance ratio, and traffic source sit alongside each other as real columns. Sort by scheduled date, filter to live webinars in the next two weeks, or pull every registrant who came from a specific traffic source, all without opening each webinar one at a time.

Inline edits run through the standard WordPress CRUD layer, so WebinarPress hooks fire, confirmation emails route through the plugin's existing flow, and any custom meta stays consistent. Bulk-tag a follow-up status on twenty registrants in one pass, the same triggers run as if each row had been opened by hand.

Webinars are a series, and the registrant data lives across every event in that series. WebinarPress captures the right signals (registrant identity, attendance flag, traffic source, webinar type) but scopes them to one webinar at a time in the default admin. The cross-event list is exactly where marketing, sales, and webinar ops do their daily work.

Treating the webinar CPT and registrant records as one tabular dataset, sortable and filterable across every event, removes the manual export step that sits between the data and the decision. The same plugin powering the live webinar runtime serves the planning table, so the numbers cannot drift between what the runtime knows and what the team sees on screen.