Five Star Restaurant Reservations Pro registers a rtb-booking custom post type and stores reservation details in postmeta: _rtb_party, _rtb_date, _rtb_email, _rtb_phone, _rtb_message, plus location and table assignments when those Pro features are enabled.

The default WordPress posts list shows the reservations one click at a time. Front-of-house staff confirming tonight's bookings, hosts running the door at peak service, and managers reviewing the week's no-shows all need party size, date, time, location, and table inline, but those fields live in postmeta and aren't sortable from the list screen by default.

SleekView reads rtb-booking directly, pivots postmeta into proper columns, and groups by date so each service period (lunch, dinner, brunch) becomes a saved view. Status changes route through the plugin's API so confirmation emails and any connected SMS workflows still fire. Multi-location restaurants scope per site without bouncing through filters.

Restaurant reservations are time-shaped, party-sized data, and the default WordPress posts list isn't either of those. Front-of-house staff confirming tonight's bookings, managers reviewing the week's no-show patterns, and reservation support looking up a returning customer's history all live or die on seeing party size, date, time, location, and notes side by side. Those fields are stored in postmeta on each rtb-booking post, which is fine for the data model but inefficient for the operational rhythm of a restaurant.

SleekView pivots the postmeta into proper columns, groups by service period, and lets each role pin the saved view that matches their work. Confirmations and cancellations route through the plugin's status API so the configured emails and SMS workflows still fire. Busy venues with hundreds of covers a night get a grid that already knows party size belongs in a column, not behind a row click.