Bookafy WP exposes its data through a custom post type (commonly bookafy_appointment) backed by wp_postmeta, plus connection settings in wp_options. The default admin presents a single appointment list and a settings screen; deeper analysis, history, and integration logs live in the Bookafy SaaS.

SleekView reads the local cache, pivots host, service, meeting URL, and status into named columns, and joins integration log entries when the plugin stores them. A single filter on date range, host, and service replaces the SaaS dashboard for day-to-day ops. Sorting on start time matches the way reception thinks about the morning, not the way the plugin sorts by post date.

Updates to status and time write through the Bookafy WP integration so the SaaS receives them and notifications fire. Local-only fields (internal notes, ops tags) stay in wp_postmeta with direct writes. Conflict detection prevents two operators from silently overwriting the same appointment.

Teams that adopt Bookafy WP usually do so because WordPress is their daily home. The plugin caches appointments locally, but the default admin treats them as ordinary posts sorted by post date instead of by appointment time. That single mismatch forces ops back to the Bookafy SaaS for anything beyond a glance.

The data already exists in wp_posts and wp_postmeta: host, service, time, status, customer. SleekView pivots those fields into named columns and adds the filters reception, sales, and support actually need. Edits write back through the Bookafy API so the SaaS stays authoritative for what the SaaS owns.

Internal notes and ops tags stay in WordPress because they belong to WordPress. A team running ten or two hundred bookings a day finally gets the daily-ops grid the plugin's local cache always implied was possible.