Video Conferencing with Zoom (by Codemanas) stores meetings and webinars as the zoom-meetings custom post type with start time, duration, host, join URL, passcode, and recurrence stored in postmeta. Registrations live in wp_vczapi_registrations with attendee name, email, status, and join time. Recordings are referenced via Zoom's cloud recordings API and cached in postmeta.

SleekView reads the CPT alongside the registrations table and surfaces meeting title, type (meeting, webinar, recurring), host, start time, duration, registration count, recording availability, and status as first-class columns. Saved views like upcoming webinars this week, meetings with cloud recordings, or recurring meetings past their last occurrence load with one click.

Inline edits cover host assignment, start time, passcode, and join URL through the plugin's own update functions, which keeps the Zoom API in sync via the plugin's existing sync logic. The registrations view shows per-attendee status (registered, attended, no-show) and supports bulk approve, decline, or email actions through the plugin's registration API.

Running webinars and meetings through WordPress works well until the catalog grows beyond ten or twenty active sessions. The default Video Conferencing with Zoom admin shows meetings as posts, which is fine for one-off sessions but underpowered for an events programme with weekly recurring meetings, monthly webinars, and on-demand training sessions across several hosts. The questions an events team has cut across meetings: which webinars need a capacity check this week, which recurring meetings have no scheduled host for the next occurrence, which past sessions have cloud recordings worth reusing, which hosts are double-booked on Tuesday.

SleekView pivots the existing CPT and registrations table into a flat dashboard with type, host, start time, registrations, and recording status as columns. Events teams use it for capacity and host planning. Customer success teams use it to balance per-host meeting load.

Marketing teams use it to roll registrations up to campaign and topic. The plugin keeps owning the Zoom API sync, the registration emails, and the recording cache exactly as it does today; SleekView just gives the events ops layer the columns that turn a busy meetings calendar into something observable instead of something that has to be opened one meeting at a time.