WPCafe stores each reservation as a custom post type with meta for party size, date and time, table, and a status field whose values include pending, confirmed, seated, completed, and cancelled. The default admin lists these as a flat WordPress posts table sorted by date. That works for browsing tomorrow but makes it impossible to see how tonight's service is actually progressing: how many guests are pending confirmation, how many are seated right now, and how many tables have turned.

SleekView Kanban reads the same WPCafe reservation records, treats the status field as the natural axis to group by, and renders one column per value. Cards show the guest name, the party size, the requested table, the booking time, and any special requests. Filters scope a board to a single restaurant, service shift, or floor section so the host stand sees only what is happening at the front door right now.

Drag a card from Pending to Confirmed and SleekView writes the new status through WPCafe's update path. The confirmation email or SMS configured in WPCafe fires. Drag to Seated when the host walks the party to their table and the kitchen sees the change in real time. Drag to Completed when the table turns. Every write goes through WPCafe's own endpoint so reporting stays accurate.

Tonight's service is a sequence of stages: a guest requests a table, you confirm, they arrive, they sit, they eat, they leave. The default WPCafe admin treats every reservation as a row in a list sorted by time. That works for browsing the week ahead but makes it impossible to see, in the middle of service, how many guests are still pending confirmation, how many are confirmed and arriving in the next hour, and how many tables are already seated.

A kanban view puts that information on the screen as four columns of cards with counts on top. The host stand can clear the Pending column in the morning. The floor manager can see, mid-service, that ten reservations are confirmed but not yet seated and adjust the door queue accordingly.

The kitchen sees the same Seated count and knows how many courses to expect. Drag becomes the verb that moves each party through service, and because the writes go through WPCafe's own endpoints, the confirmation emails and SMS messages continue to fire exactly as they did before.