Event Tickets writes RSVPs and ticket orders into wp_tribe_tickets with attendee meta in wp_postmeta on the ticket post, plus any comment an attendee leaves on the event in the standard wp_comments table joined to the tribe_events post. The default Event Tickets admin gives you a manifest and a sales total per ticket type, which is fine for door check in but useless when a future attendee wants to read what real people thought of the VIP tier last year.

SleekView Feedback reads the same comments and ticket meta, groups them by event, ticket tier, or session, 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 VIP tier or General, and a status pill that tracks whether your organiser team has acted on the note. Filter chips let visitors narrow to a single event, ticket type, or status so the loudest signal sits within one scroll of the page hero.

When a future attendee clicks Upvote on a comment that matches what they want next time, the count writes back into Event Tickets meta, so the sorting reflects real demand instead of recency. Organisers see at a glance which ticket tiers 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 Event Tickets.

Most organisers running Event Tickets 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 VIP pass has no way to see which complaint your team actually fixed last year, or which new tier 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 tier 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 Event Tickets, 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 programme listens to its audience, and that portfolio converts skeptical visitors into ticket buyers far better than a sold out badge ever could.