Bookly stores each appointment as a row in bookly_appointments and the customer-side link rows in bookly_customer_appointments, each with a status column holding values like pending, approved, cancelled, rejected, and done. The default admin view is a calendar plus a flat list, both of which surface time as the primary axis. That is fine for browsing tomorrow but useless for triage: you cannot see at a glance how many appointments are still waiting on your approval or how many of yesterday's approved slots actually closed out as done.

SleekView Kanban reads the same Bookly tables, treats the status column as the grouping axis, and renders one column per status value. Cards show the customer, the service, the staff member, the appointment start, and the total. Per-column counts surface the real backlog so you can see whether today is mostly approved or mostly pending without scrolling. Filters let each staff member open their own board and only see their own appointments.

Drag a card from Pending to Approved and SleekView calls Bookly's appointment update endpoint, which means the customer notification email and SMS configured in Bookly fire, Google Calendar sync runs, and any addons that listen for status changes behave exactly as if you had used Bookly's status dropdown by hand. Drag to Cancelled and the cancellation flow runs, including any refund hook your payment gateway exposes.

Bookly already does the hard parts: it captures the slot, takes the payment, sends the reminder, and links the customer record. What it does less well is help you see the stages those appointments move through. A pending appointment needs approval.

An approved appointment needs to actually happen. A done appointment needs to be marked done so reporting reflects reality. A cancelled appointment may need a refund and a follow-up.

Those four verbs are the entire workflow, and the calendar grid hides them inside a tiny status badge in the corner of each event. A kanban view promotes status to the primary axis of the screen, which means the day's actual workload becomes visible in one look. The team sees how many pending requests are still waiting and reaches for them first.

They see how many approved slots are still outstanding by close of day. They see how many done appointments accumulated. Drag becomes the verb that moves the work forward, and because the writes go through Bookly's existing endpoints, the customer experience and the reporting stay identical to what your staff already trusts.