Event Espresso registers events into esp_event, attendees into esp_attendee, and the registrations that connect them into esp_registration with a status code per row. Post-event notes arrive through three channels, comments on the event post, an answer to a custom registration question that the team marked as a feedback prompt, and the add-on rating column that some sites store on the registration. The default reading surface is the registration list, the comments thread, and a CSV from the question report.

SleekView Feedback joins those three sources onto one board. It reads wp_comments on the event post, the feedback-tagged answers from esp_answer, and the rating column on the registration row. Each row renders as 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 registration status so a VIP regret card reads differently from a general comment.

Upvote writes back to the counter meta on the row. Submit lands a new topic request as a comment on the next 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 off the same numbers the audience is voting on.

Event Espresso is a registration plugin first and a calendar second, which means the most reliable post-event signal often lives inside the registration record itself. The team builds a custom question called Topic for next year and reads the answers in a CSV from the question report. Public comments on the event page carry a different slice, usually live takes during or right after the event, and the add-on rating column carries scores.

SleekView Feedback brings those three sources onto one board with upvotes, categories, and statuses so the audience ranks requests in public and the team reads them in the same order. A speaker rating that got a rebooking has a Shipped pill, a confirmation email bug has Open, and a topic that did not make next year's cut has Declined with a short reason. The audience stops asking the same question on three forms and the team stops merging three reports into a planning sheet that lives in another tool.