TidyCal WP centres on embedding TidyCal booking pages and (in sync-enabled builds) mirrors bookings into a custom post type backed by wp_postmeta. Connection details live in wp_options. The default admin focuses on embed configuration, leaving the deeper scheduling analytics to the TidyCal SaaS.

SleekView reads the synced bookings and pivots host, meeting type, invitee email, scheduled time, and status from wp_postmeta into named columns. One saved view can filter across date range, host, meeting type, and status. Sorting follows booking time rather than post date, so the morning's first booking lands at the top.

Status changes route through TidyCal's API when supported so invitee notifications and host calendar updates fire as usual. Internal notes and CRM-linked IDs stay in wp_postmeta with direct writes guarded by conflict detection.

TidyCal appeals to creators and consultants who want a lifetime-deal scheduling tool tied closely to their WordPress site. The plugin nails the embed, but the deeper ops experience lives in the TidyCal app. For solo operators and small teams whose CRM context lives in WordPress (clients as users, projects as custom posts, invoices via WooCommerce), every cross-app jump is a context switch.

The mirrored booking data carries enough for a real ops grid: host, type, invitee, time, status. SleekView pivots wp_postmeta into named columns and adds the filters daily ops actually need. API write-back preserves TidyCal as the source of truth for what it owns.

Internal notes stay in WordPress. The outcome is one workspace where bookings, clients, and content sit together instead of one tab apart.