Team Booking stores every appointment as a row in tbk_reservations with a status column whose values are pending, approved, completed, cancelled, or refused. Each row is linked to a Google Calendar event so changes round-trip between WordPress and the staff member's calendar. The default admin lists those rows as a flat table sorted by booking ID with the status as a small column per row.

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

Drag a card from Pending to Approved and SleekView calls the same Team Booking update path the admin uses, which fires the approval email, marks the Google Calendar event as confirmed, and triggers any payment hook you have configured. Drag to Cancelled and the linked Google Calendar event is removed alongside the WordPress row, so the staff member's schedule stays consistent.

Team Booking ties WordPress bookings to staff Google Calendars, which is exactly the integration small teams need. The default admin lists reservations in booking-ID order, which is the order they came in, not the order they need attention. That order makes sense for accounting and useless for team operations.

The board view fixes this by making the only state that matters, the booking status, the primary axis of the screen. You can see at a glance how many requests still need an approval, how many of yesterday's approved slots actually completed, and how many were refused so the team can review the criteria. Cards make individual bookings legible at the level of customer, service, team member, start time, and money.

Drag is the natural verb for moving a booking from one stage to the next, and because SleekView writes through Team Booking's own functions, every drag still triggers the approval emails, the Google Calendar event updates, 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.