Restaurant Table Booking stores every reservation as a row with a status column whose values include pending, confirmed, seated, cancelled, and no-show. The default admin lists those reservations as a flat table sorted by reservation time with the status as a small column per row, which works for a quiet bistro and falls apart on Friday night when every table is turning.

SleekView Kanban reads the same reservation table and treats the status column as the natural axis to group by. Each card surfaces the guest name, the party size, the requested time, the table assignment, and any note from the booking. Columns mirror your real Restaurant Table Booking statuses, so the pending stack and the seated stack each read as a single number rather than as labels scattered across rows.

Drag a card from Confirmed to Seated when the guest arrives and SleekView calls the same Restaurant Table Booking update path the admin uses, which marks the table as occupied so the public booking form stops offering the same slot. Drag to No-show after a grace period and the table is released back to the pool. Per-shift boards keep the floor manager focused on tonight's seating without the back-office noise.

A restaurant floor is a real-time system: confirmations come in, parties arrive, tables turn, no-shows free up seats for walk-ins. Restaurant Table Booking captures all of that already, but the default admin lists reservations in time order with status as a small label, which is the wrong axis for the question hosts actually ask, which is who is seated right now and which tables are about to turn. The board view fixes this by making the only state that matters, the reservation status, the primary axis of the screen.

You can see at a glance how many tables are confirmed for the next slot, how many are currently seated, and how many no-shows have just released seats back to the pool. Cards make individual bookings legible at the level of guest, party size, time, table, and any allergy or anniversary note. Drag is the natural verb for marking a table seated when a party arrives, and because SleekView writes through the plugin's own update path, every drag still triggers the confirmation emails, the table availability changes, and the SMS hooks you already configured.

The list view stays available for the back office while the host stand finally has a board for service.