Yes. SleekView joins latepoint_bookings with latepoint_services, latepoint_agents, latepoint_customers, and latepoint_transactions so each booking surfaces with its full context on a single row. The agent UI detects each table's columns and exposes them as joinable fields.

Yes. LatePoint's custom booking-form add-on stores extra answers in booking meta. SleekView lists the meta keys actually in use — intake answers, allergies, project briefs, special requests — and adds them as columns so the data the agent needs at the start of the appointment is on the row, not behind a click.

Yes. SleekView writes through LatePoint's booking update flow, so customer notifications, agent notifications, slot-release logic, and any wired-up custom actions fire as expected. Bulk operations iterate through the same flow so the side effects match a manual edit.

Yes. latepoint_transactions stores gateway, amount, and status per transaction with a booking reference. SleekView joins on booking ID and surfaces transaction columns so a finance view shows booking, service, customer, amount, and status side-by-side — useful for daily reconciliation.

LatePoint supports both repeating series and group bookings (one service slot, multiple customers). SleekView reads each pattern — a series view shows every instance flattened, while group bookings expand to a sub-table per slot listing each attendee. Pick the pattern that matches the workflow.

No — it's an additional admin surface. The default LatePoint screens stay where they are for the calendar UI, agent dashboards, and customer-facing flows. SleekView gives staff, reception, and finance teams the row-level views they actually need without disturbing the booking flow your customers use.

Queries hit indexed columns on latepoint_bookings directly (id, status, start_datetime, agent_id, customer_id). Joins use the related tables' primary keys. 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 tabs for bookings (by date), customers (by lifetime spend), and transactions (by gateway). Customer name on the booking view links through to the customer's detail view with their full booking history.