LatePoint stores every booking as a row in latepoint_bookings with a status column whose values include pending_approval, approved, completed, cancelled, and no_show. The default LatePoint admin shows the calendar grid plus a bookings list filtered per agent, both of which make it hard to see at a glance how many requests still need you to approve them.

SleekView Kanban reads the same latepoint_bookings table and treats the status column as the natural axis to group by. Each card surfaces the customer name, the service, the assigned agent, the start datetime, and the price. Columns mirror your real LatePoint statuses, so the pending stack and the completed stack each read as a single number rather than as labels scattered across rows.

Drag a card from Pending Approval to Approved and SleekView calls the same LatePoint update path the admin dropdown uses, which fires the approval email, the SMS plugin's notification, and the Google Calendar push you already configured. Drag to Cancelled and the refund and notification flows run through LatePoint so any payment gateway integration handles the money side consistently. Per-agent boards mean each provider only sees and writes to their own rows.

LatePoint captures bookings cleanly with statuses that mirror a real service workflow: pending approval, approved, completed, cancelled, no-show. The default admin presents the result as a calendar plus a list, both of which make it hard to see at a glance which bookings still need a human decision today. The board view fixes this by making the only state that matters, the booking status, the primary axis of the screen.

You can see in one glance how many requests still need an approval, how many of yesterday's approved slots actually completed, and how many no-shows need a recovery call. Cards make individual bookings legible at the level of customer, service, agent, time, and money, which is what a front desk needs. Drag is the natural verb for moving a booking from one stage to the next, and because SleekView writes through LatePoint's own functions, every drag still triggers the approval emails, the SMS notifications, the Google Calendar pushes, and the deposit captures you already configured.

Calendar view, list view, and board view become three reading surfaces over the same data, each appropriate to a different question.