Scheduling by Bookafy primarily stores connection settings in wp_options and caches recent appointments either as a custom post type or in a plugin-specific cache table, depending on the version. The default admin shows a basic list of upcoming appointments and a connection panel; deeper filtering and history live in the Bookafy SaaS dashboard.

SleekView reads the cached appointment rows and pivots their meeting URL, host, service, status, and start time into proper columns. Where the plugin uses postmeta, SleekView surfaces those keys as named columns; where it uses a custom table, SleekView reads the table directly and exposes the same fields. The default admin's single-screen list becomes a filterable grid covering hosts, services, and date ranges in one place.

Edits route through the Bookafy API for reschedules and cancellations, so changes propagate to Bookafy's own systems and notifications fire as expected. Direct writes are reserved for local-only audit fields that the plugin keeps in postmeta, such as internal notes or ops tags.

Scheduling SaaS like Bookafy is excellent at booking flows but the WordPress side often becomes a thin sync layer. Teams that run support tickets, CRM notes, and finance in WordPress end up tab-hopping between the SaaS dashboard and the admin to answer the same question twice. The plugin caches the appointments locally, but the default UI only shows them as a list.

The data needed for filtering (host, service, status, internal notes) is already in wp_postmeta or the plugin's cache table. SleekView pivots those fields into named columns and combines them with WordPress role gating so each team sees the slice they need. Edits route back to Bookafy where they should, and stay local where they should not.

The result is a WordPress-first ops view that respects the SaaS as the source of truth without forcing everyone to live in it.