LatePoint Pro's data spans wp_latepoint_bookings, wp_latepoint_customers, wp_latepoint_agents, wp_latepoint_services, wp_latepoint_locations, and wp_latepoint_transactions. Each Pro feature (multi-location, services-per-agent, payment processors) adds either columns or extra tables.

The default admin presents these through fixed-column lists. Agents managing their own pipeline, ops staff confirming tomorrow's bookings across locations, and finance reconciling a month of Stripe charges all swap between tabs because the schema is split across them.

SleekView reads the wp_latepoint_* tables directly, joins by customer, agent, service, location, and transaction IDs, and surfaces them as regular columns. Status edits route through LatePoint's API so confirmation emails, SMS, and Pro automations still fire. Saved views give each role (agent, ops, finance, support) the slice they need.

LatePoint Pro's well-modelled schema (bookings, customers, agents, services, locations, transactions) is why the default admin can show each table neatly, and also why agents and ops staff need multiple tabs to confirm tomorrow's bookings, look up a customer's history, or reconcile a month of payments. SleekView reads the same wp_latepoint_* tables LatePoint already maintains and joins them into one editable grid. Each role gets a saved view scoped to their work: agents on their own pipeline, location managers on their site, finance on per-processor reconciliation, support on per-customer history.

Status edits write through LatePoint's API so confirmation emails, SMS, and Pro automations continue to fire. The indexes LatePoint already maintains keep query performance predictable as bookings accumulate, and the cost of tab-hopping disappears in favour of a single workspace that already knows how the schema fits together.