MEC Pro registers events as the mec-events post type with bookings stored as mec-books posts and additional MEC fields saved as post meta on both. The booking form often carries a custom field for a feedback question or a topic request, and the post-event email collects ratings into another meta key. Comments on the event page hold the public post-event takes. The default reading surface is the bookings list, the comments thread, and a custom field report exported as CSV.

SleekView Feedback brings those three onto a single board. It reads wp_comments joined to the mec-events post, the feedback-tagged meta from mec-books, and any post-event rating meta on the booking. Each row renders as a card with a title, a running vote count from a counter meta, the author, a category pill for the topic, and a status pill bound to the organiser response field. The card front carries the event name, the booking tier when tickets are tiered, and the booking status so a confirmed booking note reads differently from a cancelled one.

Upvote writes back to the counter meta on the row. Submit lands a new topic request as a comment on the closest upcoming event with the category preset. The board export writes the top cards to CSV with category, status, tier, and event so the planning round reads off the same signal the audience just voted on.

MEC Pro is a booking plugin first, and the booking form is where the most concentrated audience signal lives. Most teams add a custom field on the booking form for a topic request or a feedback question, then read the answers in the per-event field report long after the event has finished. SleekView Feedback turns those answers into cards on the same board as the public comments and the post-event rating meta, so the audience ranks requests in public and the organiser team reads them in the same order.

A confirmed booking note from a VIP weighs differently from a cancelled booking note, a speaker who got rave answers gets a Shipped pill once rebooked, and a topic that did not make the cut gets a Declined pill with a short reason next to the votes. The audience stops repeating the same ask in two forms and the team stops reading three reports because everyone reads the board.