Event Tickets Plus stores attendees as posts in tribe_tpp_attendees tied to a WooCommerce order, with per-ticket questions saved as attendee meta and check-in writing to _tribe_qr_ticket_checkedin. Comments on the event page carry the public post-event takes, and the per-ticket questions often include a feedback prompt the team set up to gather topic requests at the door. The default reading surface is the Attendees screen, the comments thread, and a per-ticket question CSV.

SleekView Feedback brings those three sources onto one board. It reads wp_comments on the event post, the attendee meta from tribe_tpp_attendees for any question tagged as feedback, and the linked WooCommerce order status. Each row becomes a card with a title, the 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 ticket type, and the check-in flag so a checked-in attendee's note reads differently from a no-show 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, ticket type, and event so the planning round reads the same numbers the audience voted on.

Event Tickets Plus is the rare ticket plugin that captures custom answers per attendee, not per order, which means each ticket can carry its own slice of feedback. The default workflow is to read those answers in the per-ticket question report and the public comments thread separately, then merge them in a planning meeting weeks later. SleekView Feedback turns the answers and the comments into one board with upvotes, categories, and statuses, and the card front carries the ticket type and the check-in flag so a checked-in VIP weighs more than a no-show general admission.

A topic that climbs across many attendees gets a Planned pill on the public board, a bug that hit the QR scanner gets an Open pill until the team fixes it, and a request that did not make the cut gets a Declined pill with a short reason. The audience stops repeating the same ask in three forms and the team stops merging reports because everyone reads the same surface.