LatePoint Pro stores every booking in wp_latepoint_bookings with a status column that cycles through Pending Approval, Approved, Cancelled, and No Show. Service info lives in wp_latepoint_services, the assigned team member in wp_latepoint_agents, and the customer in wp_latepoint_customers. Payment state lives on the booking row alongside the appointment price. The default LatePoint dashboard is a calendar grid with a separate bookings list, which works for scheduling and forces a modal trip for every status change.

SleekView reads the same rows, joins customer, service, and agent in one query, and uses the LatePoint status field as the natural group column. The four LatePoint statuses become the four kanban columns. Card titles pull the customer name and the service title for the headline, the meta line shows the agent and the appointment time, and the corner of the card surfaces payment status as a colored dot so unpaid Approved bookings are easy to spot.

Drag a card from Pending Approval into Approved and SleekView writes the new status to the LatePoint row, fires the LatePoint action hook for the approval email and Zapier webhook, and the agent's calendar reflects the change. No Show is handled the same way, so receptionists can flag missed appointments straight from the board and trigger whatever follow-up sequence the business has set up inside LatePoint or its Pro add-ons.

LatePoint Pro is built around a calendar primary view, which works for scheduling and works against fast triage. The moment you have twenty appointments waiting on Pending Approval the calendar stops being the right tool, because the dominant question is no longer when each appointment is happening but which ones need a human decision right now. The kanban board flips the primary axis from time to status, which is exactly the question reception needs to answer at the start of every shift.

Drag writeback closes the loop. Every status change on the board writes to the same LatePoint row a modal would write to, fires the same action hook the LatePoint notification engine listens to, and the same agent calendar sync updates as if you had used the back office. The board never replaces the LatePoint calendar, it sits next to it as a triage view.

Owners running multi-agent days get the additional benefit of swim lanes, which let them rebalance load across a team's day with a few drags instead of a list of who has how many bookings where in the back office.