Setmore WP exposes the Setmore booking widget and (depending on version) mirrors recently synced bookings into a custom post type or cache table backed by wp_postmeta. Connection settings live in wp_options. The default WordPress admin focuses on the widget configuration and a brief upcoming list, while the deeper ops live in the Setmore web app.

SleekView reads the local booking mirror and pivots staff member, service, start time, and customer email out of postmeta into named columns. Filters span date range, staff, service, and status in a single saved view. Sorting follows the appointment time rather than the WordPress post date so the morning's bookings appear in the order ops cares about.

Edits route through Setmore's API for status and rescheduling so notifications fire and the SaaS stays the source of truth. Local-only fields (internal notes, ops tags, internal reference numbers) stay in wp_postmeta with direct writes and conflict detection.

Setmore is one of the most adopted appointment platforms for small services businesses, and many of those businesses already run their website on WordPress. The plugin gives them the widget and basic ops, but the daily-ops grid lives in the Setmore SaaS. For salons, therapists, and freelancers running their site, marketing, and bookings from the same WordPress admin, that split creates friction.

The data Setmore WP mirrors locally is enough to drive a real daily-ops table: staff, service, time, customer, status. SleekView pivots wp_postmeta into named columns and adds the filters reception and staff actually need. API write-back keeps Setmore authoritative for what it owns, while internal notes and ops tags stay in WordPress.

The result is fewer dashboards, fewer tabs, and a single workspace where bookings, customers, and content live together.