FooEvents builds on WooCommerce, so each ticketed event is a product in wp_posts with FooEvents meta and ticket data stored in wp_postmeta on the product row and as WC_Order_Item_Meta on the order line. Attendees who comment on the WordPress event product page leave standard wp_comments rows joined to the product post. The default FooEvents admin gives you ticket exports and a check in screen, which is great for the gate but useless when a future buyer wants to read what real attendees thought of last year's track.

SleekView Feedback reads the same comments and FooEvents meta, groups them by event product, ticket option, or venue, and renders one card per item sorted by votes. Each card shows the comment title, the running vote count, the attendee first name, a category pill like Ticket or Session, and a status pill that tracks whether your organiser team has acted on the note yet. Filter chips let visitors narrow to a single event product, ticket type, or status so the loudest signal stays one scroll from the page hero.

When a future attendee clicks Upvote on a comment that matches what they want next time, the count writes back into FooEvents comment meta, so the sorting reflects real demand instead of recency. Organisers see at a glance which ticket options get the most love, which session complaints keep coming back, and which new perk attendees keep asking for, all from one board reading straight from FooEvents.

Most organisers running FooEvents already collect great post event feedback, it just never makes it past the admin reports or the inbox. A future buyer deciding whether to grab a backstage pass has no way to see which complaint your team actually fixed last year, or which new ticket option finally shipped after a hundred upvotes. That gap costs trust on every comparison search, because the social proof exists but stays invisible.

SleekView Feedback gives the same data a public surface that feels like a modern roadmap tool. Comments and ticket meta show up as cards with vote counts, statuses, and category pills, so a single board answers questions like which ticket option delivers the best experience, which session complaint keeps coming back, and which new perk attendees keep asking for. The data never moves, the source of truth stays inside FooEvents, and yet the page reads like a Canny board purpose built for ticketed events.

Over a few seasons, that board becomes a living portfolio of how your event listens to its audience, and that portfolio converts skeptical visitors into ticket buyers far better than a sold out badge ever could.