FluentBooking Pro stores every meeting in wp_fcal_bookings, with linked meeting type configs in wp_fcal_meetings and host data in wp_fcal_calendar_events. Each completed booking row holds the host, the meeting type, the duration, the timezone, the form responses, and the conferencing link used at the time. Once that meeting passes its end time, the row turns into real post-stay context that the admin alone never publishes to the public site.

SleekView Feedback reads those FluentBooking rows, joins them to the meeting and host tables, and renders one card per finished booking as a public review. Each card shows the attendee first name, the meeting type, the host name, the date of the call, and an Upvote button. Returning attendees vote up the meetings they want to see repeated, so the board doubles as a public review feed and as a live signal for the host about which call formats are landing.

Filters by host, meeting type, and category sit at the top of the board, and status pills map straight onto a custom booking status column. A feedback card that asks for a longer Q and A slot can move through Open, Planned, In progress, and Shipped as the host iterates, and every state change writes back to the same FluentBooking row so reports never disagree with the board.

FluentBooking Pro is built to make scheduling friction free, but the story of what actually happened on the call almost never makes it back to the public website. A public review board built straight from the same database changes that overnight. New visitors land on a page that shows real, recent meetings with real attendee first names, real meeting types, and real votes from peers, and that signal beats any static testimonial wall for buying confidence.

Returning attendees who would otherwise leave silently after a great call now have one click to vote up the format they want again, which gives the host a live read on what is landing without sending another survey. Filters by host and meeting type turn the board into a working dashboard for sales, coaching, and customer success teams, and status pills tied to a booking lifecycle close the loop on any feedback card that lands. The whole board is one query against existing FluentBooking tables and one shortcode on a public page.