Yes. Resources (staff, rooms, equipment) are typically separate post types referenced by ID in appointment meta. SleekView joins on the resource ID and surfaces the resource title and any meta you choose — role, room number, capacity — as inline columns so the front desk sees who and where without a second screen.

Yes. Bookings Pro stores deposit and balance amounts plus gateway and transaction reference in postmeta. SleekView surfaces these as columns so a finance view can reconcile Stripe or PayPal against appointment status — useful for catching pending deposits at the start of each day.

Yes. SleekView writes through the post update flow, so save_post_booking and any plugin-specific hooks fire as expected. Status changes still trigger customer emails, cancellations still release the time slot, and integrations still receive their webhook payloads.

Indirectly — SleekView shows what's booked, not the empty space between bookings. For an availability heat-map, switch to the kanban view grouped by date and resource so the gaps visualise naturally. The default appointment calendar in Bookings Pro stays available for booking-against-availability work.

Bookings Pro stores recurring series either as separate appointment posts linked by a series ID or as a single record with recurrence meta, depending on the version. SleekView reads either pattern — you can show a flat list of every instance, or filter to a series ID for a per-series view.

No — it's an additional admin surface. The default Bookings Pro screens stay where they are for booking creation, calendar viewing, and customer-facing flows. SleekView gives staff and finance teams the row-level views they need without disturbing the booking flow your customers already use.

Queries hit indexed postmeta keys directly (start datetime, status, resource ID). Date-range filters use the indexed start-time meta. For very large calendars, opt-in materialised columns can push frequently-filtered meta keys into dedicated indexed storage to keep queries fast.

Each table is one view, but views are switchable inside a single SleekView page. Build a tabbed setup with one tab per source — appointments by date, customers by lifetime spend, payments by gateway. The customer column on the appointment view links through to the customer detail.