WP Booking System stores every form submission as a row in wpbs_bookings with a status column whose values are pending, approved, declined, expired, or trashed. The default admin lists those submissions as a flat table sorted by submission date, which is fine for two bookings a week but hides the work once you have a busy property calendar and a steady stream of inquiries.

SleekView Kanban reads the same wpbs_bookings table and treats the status column as the natural axis to group by. Each card surfaces the guest name, the calendar, the check-in and check-out dates, and the total. Columns mirror your real WP Booking System statuses, so a glance tells you how many submissions are waiting on you, how many you have already approved, and how many have expired and need a follow-up.

Drag a card from Pending to Approved and SleekView calls the same WP Booking System update path the admin dropdown uses, which fires the approval email and updates calendar availability so the date no longer shows free. Drag to Declined and the rejection email fires with the wording you have configured. Saved views per calendar mean a property manager only sees and writes to the rows for their cottage.

WP Booking System turns a calendar into a lead capture form. The submissions land cleanly, the auto-emails go out, and the table fills up. What the default admin does not show you is which of those submissions 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 at a glance how many pending submissions still need an answer, how many of yesterday's approvals actually paid the deposit, and how many submissions have expired and need a polite recovery email. Cards make individual submissions legible at the level of guest, calendar, dates, and money, which is exactly what a property manager needs to triage a stack of inquiries.

Drag is the natural verb for moving a booking from one stage to the next, and because SleekView writes through WP Booking System's own update path, every drag still triggers the approval emails, the calendar availability changes, and the extension hooks you already rely on. Table view and board view become two reading surfaces over the same data instead of a tradeoff between them.