Post-event feedback Pro A feedback card per booking.

Once an event has finished, everyone who held a booking for that date is emailed a private link. It opens a card branded with your schedule: a rating from one to five, which is required, and a comment of up to 2,000 characters, which is not. They submit it, and you read it on the Feedback tab of your Sales page. Nothing is asked while the event is still on.

Only somebody who holds a booking. The form sits behind a link tied to that one booking, and the link only travels in the request email, so it is not something a passer-by on your event page can fill in. Paid tickets and free RSVP registrations both count, because a registration is recorded as a booking with a zero total. Followers are not asked: following a schedule is not attending an event.

After that occurrence has ended, plus a delay you choose from 1, 2, 6, 12, 24 or 48 hours. Twenty-four is the default. The end of the occurrence is worked out in the schedule's own timezone, so an evening event does not get asked about a day early. The queue is checked hourly, which makes the times approximate rather than exact, and no request goes out for an event that ended more than thirty days ago.

Not unless you switch it on. "Show feedback publicly" starts off, and with it off every card is yours alone. Turn it on and the event page grows an Attendee Reviews block: an average, a count, and the twenty most recent cards, each showing the attendee's first name only. Attendees are told before they write, because the form carries a notice saying their words may appear on the event page.

No, and it is better to know that up front. There is no per-card approval queue and no way to remove one card from the public list: publishing is a single switch on the schedule, so it is all of them or none of them. That is exactly why it starts off. Fan photos, videos and comments are the feature that does have an approval queue, if per-item moderation is what you need.

One. Somebody who bought six tickets in a single booking is asked once, not six times, and the database holds a unique constraint on the booking so a second card cannot be created. Open the link again after submitting and you get a thank-you page instead of a blank card. Passes and subscriptions are skipped, because they are not tied to a single date. A checkout that covers several events is one booking per event, so each event asks once it is over.

A refund in full takes the booking out of the asking: it is not sent a request, and a link already sent stops opening. If the attendee had already returned a card, it drops out of the public reviews, the Feedback tab's average and response rate, and GET /api/feedback, but it stays in the Feedback tab's list and the CSV export, so what they said is not lost. A partial refund leaves the booking paid, so its card stands.

Yes. Post-event feedback is a Pro feature at 5 NGN a month, included on Enterprise, and selfhosted installations have it too. On the hosted platform it also needs your schedule's own email settings, because the request is sent from your address rather than ours. Once those are saved the toggle unlocks, and there is a button to send yourself a test card before you turn it loose on real attendees.

Three ways. Export the lot to CSV from the Feedback tab. Subscribe a webhook to feedback.submitted and get the event, the date, the attendee's name and email, the rating and the comment posted to your endpoint as each card lands. Or read GET /api/feedback with an API key, filtering by event, subdomain, date, minimum rating and a date range. All three are on the same Pro plan.