A day after the event ends, everyone who booked gets a card: a rating from one to five, and a comment if they have one. Nobody else can fill it in, and nobody can fill it in twice.
Great night. Sound was spot on. Could the doors open a little earlier next time?
One card per booking. Addressed to the name on it, posted after the event, and returnable once.
Not left out on a table.
Rating 1 to 5Comment up to 2,000 charactersOne card per booking1 to 48 hours after the endYours alone by defaultPer-event overrideCSV exportfeedback.submitted webhookRequests stop after 30 daysRating 1 to 5Comment up to 2,000 charactersOne card per booking1 to 48 hours after the endYours alone by defaultPer-event overrideCSV exportfeedback.submitted webhookRequests stop after 30 days
01
Who gets one
Not the room. The booking.
A card is addressed to a booking, which is why the answers are worth reading. There is no open review box on the event page for people who were never there.
The address
The name on it
The request goes to the email address on a confirmed booking, and the link it carries belongs to that booking alone. Followers are not asked, and nor is anyone who simply opened the page.
Free counts
RSVPs included
A registration is recorded as a booking with a zero total, so a free event that takes RSVPs collects cards exactly the way a paid one does. You do not have to sell a ticket to ask the question.
Per booking
One card, not six
Somebody who booked six seats is asked once. Passes and subscriptions are skipped, since they are not tied to a single date, and so are test and blank addresses.
The card is printed off the end of the occurrence, not off its start, and the end is worked out in your schedule's own timezone. Before that moment the link simply does not open.
How long to wait
six choices, 24 hours by default
1h2h6h12h24h48h
Hours after the occurrence ends. The setting is a plain dropdown with these six values on it, so an afternoon workshop can ask straight away while a late show waits until people are awake.
How long it keeps asking
30 days, then it stops
Day one is the day the event ended. The solid cell is the request going out on the default delay. Dashed cells are past the thirty-day cut-off, where no new request is created: an event you forgot to enable feedback on last spring will not suddenly email three hundred people. A card already sent stays open, so a late reply still counts.
Checked hourly
Pro
The queue runs once an hour, which is why the Feedback tab labels its send times as approximate. If you want them gone now, there is a send-now button.
Draft shuts the card
Free
While an event sits in draft its card will not open, even for somebody holding the link, and nothing typed into it can be submitted. It is the card that checks and not the queue, so drafting an event after tickets sold is not a way to recall a request already on its way. Draft is on every plan.
Per event, if you want
Pro
Each event can follow the schedule default, force feedback on, or force it off. Handy for the one night you would rather not ask about.
The per-event override
03
What lands
One email. Two questions.
The request is short on purpose, and so is the card behind it. A rating you cannot skip, a comment you can, and a submit button that stays dead until the rating is marked.
The request
sent from your address
Subject
How was your experience?
Hello Dana,
We would love to hear your thoughts on the event you attended.
Thursday Jazz Session
Thu 18 Jun, 8:00 PM
Submit Feedback
If that event also collects photos, video or comments from attendees, the same email carries a second link inviting them to add theirs. And if they have allowed web push on your schedule, a notification goes out alongside it.
The card
your logo, colour and font
How was your experience?
Five stars on the real form, one to five in the database. The card at the top of this page is our drawing of the same value.
Rating *
Comment (optional)
Share your thoughts about the event...
0 / 2000
Submit stays disabled until a rating is marked, so a card cannot come back empty. Open the link again afterwards and you get a thank-you page rather than a second blank card.
04
Yours, or pinned up
Read them yourself, or pin them up.
One switch, off by default. Leave it off and the cards are private working notes. Turn it on and they become the reviews that help the next person decide whether to come.
Show publicly: off
Default
Nobody else reads them
Cards land on the Feedback tab, in the CSV export, on the webhook and in the API. The event page shows nothing at all, so a rough night stays between you and the person who had it.
You see the attendee's full name and email, because you already do on the booking.
An average across every card you hold, and a response rate, sit above the table.
This is where most schedules stay, and it is the honest default: feedback you can act on does not have to be feedback everyone can read.
Show publicly: on
Pro
Attendee reviews on the event page
Attendee Reviews
4.463 reviews
Dana2 days ago
The 8pm start worked much better.
Marcus2 days ago
Sound was spot on. Doors a bit earlier?
Tom1 week ago
Could not hear the announcements at the back.
An average, a count, and the twenty most recent cards, worked out for that event and, on a recurring one, for that date. Each card shows the attendee's first name and nothing more, and cancelled or deleted bookings drop out of the list.
Attendees are told before they write: the card carries a notice saying their words may appear on the event page and their first name will be shown.
Being straight about moderation
There is no per-card approval queue for feedback and no way to hide one card while publishing the rest. Publishing is a single switch on the schedule, which is precisely why it starts off. If per-item moderation is what you need, fan photos, videos and comments do have an approval queue.
How fan content is moderated
05
The returned cards
Every card in one drawer.
The Feedback tab of your Sales page counts what is queued, what has gone out, what has come back and what share of the asking worked.
Pending
12
queued, not sent yet
Sent
41
awaiting a reply
Responded
63
average 4.4 out of 5
Response rate
61%
63 of 104 asked
Returned feedback cards, with the attendee, event, date, rating, comment and the day it was submitted
Attendee
Event
Date
Rating
Comment
Submitted
Dana R.
Thursday Jazz Session
18 Jun
The 8pm start worked much better.
19 Jun
Marcus O.
Thursday Jazz Session
18 Jun
Sound was spot on. Doors a bit earlier?
19 Jun
Priya S.
Saturday Matinee
20 Jun
No comment left
21 Jun
Tom B.
Saturday Matinee
20 Jun
Could not hear the announcements at the back.
21 Jun
Lena K.
Thursday Jazz Session
25 Jun
Bar queue moved fast this week.
26 Jun
Owen H.
Open Studio
27 Jun
Loved the walkthrough at the start.
28 Jun
Sortable by attendee, event, date, rating and submission date. Comments are shortened in the table and printed in full in the export. A card with no comment is still a card: the rating is the required half.
Resend one
A request that landed in a spam folder can be sent again from the row it sits on, for that one attendee.
Send the ready ones now
Everything past its delay but still waiting on the hourly queue can be pushed out immediately from the actions menu.
Or cancel the lot
Changed your mind about a whole batch? Cancel every pending request in one go before any of it leaves.
06
When one comes back
A card should not sit there waiting to be noticed.
A push, straight away
Pro
If web push is switched on for your schedule and you have allowed notifications on a device, a new card arrives as a notification the moment it is submitted. That channel does not wait on email being configured.
An email, if you asked for one
Pro
Switch on the New feedback notification and you get the event, the attendee, the rating and the comment by email. On the hosted platform this waits until the schedule has its own email settings, the same requirement as the request. Enterprise schedules can have several admins subscribed.
A webhook, into your own stack
Pro
Subscribe to feedback.submitted and every card is posted to your endpoint as it lands, carrying the event, the date, the attendee's name and email, the rating and the comment.
Or read it back on demand
Pro
GET /api/feedback returns the cards for schedules your API key administers, filtered by event, subdomain, date, a minimum rating or a date range. Handy for putting the ratings on a site of your own.
Before any of it goes near a real attendee, send yourself a test card from the schedule's Feedback settings.
Where the settings live
07
The small print
The whole card, terms and all.
Printed on the back, where the small print belongs. Nothing here should surprise you after you have asked three hundred people how it went.
Comment card / reverseTerms
Rating
Required, a whole number from 1 to 5
Comment
Optional, up to 2,000 characters
Cards per booking
One, enforced by the database
Editing a card
Not possible once it is submitted
Who is asked
Everyone who holds a paid booking, RSVP registrations included
Request delay
1, 2, 6, 12, 24 or 48 hours after that occurrence ends
Default delay
24 hours
Queue
Checked hourly, so the times shown are approximate
Requests stop
30 days after the occurrence ended
Draft events
The card will not open while an event is in draft
Passes and subscriptions
Skipped, because they are not tied to one date
Test and blank addresses
Skipped
Public display
Off by default; an average plus the latest 20 when on
Per event
Schedule default, on, or off
Getting it out
CSV export, feedback.submitted webhook, REST API
Plan
Pro, included on Enterprise and in selfhosted installations
On the hosted platform, feedback emails need the schedule's own email settings saved first, because the request is sent from your address rather than ours. Selfhosted installations have the Pro feature set, so feedback is available there as soon as a real mailer is configured.
Everything people ask before they start asking their attendees.
01How does post-event feedback work?
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.
02Who can leave feedback?
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.
03When does the request go out?
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.
04Is feedback shown publicly?
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.
05Can I moderate or delete a card?
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.
06How many cards does one booking get?
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.
07Do I need the Pro plan?
Yes. Post-event feedback is a Pro feature at $9 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.
08Can I get the feedback out of Event Schedule?
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.
Comment cardBlank
Event
12345
Your event, your logo, your colour. The words are theirs.
Free to start
Stop guessing how it went. Ask the room.
Claim your schedule and publish your events for free, forever. Post-event feedback is on the Pro plan at $9 a month, with zero platform fees on anything you sell.
A comment card per ticket.
A day after the event ends, everyone who booked gets a card: a rating from one to five, and a comment if they have one. Nobody else can fill it in, and nobody can fill it in twice.
Thursday Jazz Session
Thu 18 Jun, 8:00 PM
How was your experience?
Anything else?
Great night. Sound was spot on. Could the doors open a little earlier next time?
One card per booking. Addressed to the name on it, posted after the event, and returnable once. Not left out on a table.
Who gets one
Not the room. The booking.
A card is addressed to a booking, which is why the answers are worth reading. There is no open review box on the event page for people who were never there.
The address
The name on it
The request goes to the email address on a confirmed booking, and the link it carries belongs to that booking alone. Followers are not asked, and nor is anyone who simply opened the page.
Free counts
RSVPs included
A registration is recorded as a booking with a zero total, so a free event that takes RSVPs collects cards exactly the way a paid one does. You do not have to sell a ticket to ask the question.
Per booking
One card, not six
Somebody who booked six seats is asked once. Passes and subscriptions are skipped, since they are not tied to a single date, and so are test and blank addresses.
Post-event feedback is on the Pro plan. See what that costs
When it goes out
Nothing is asked while the event is still on.
The card is printed off the end of the occurrence, not off its start, and the end is worked out in your schedule's own timezone. Before that moment the link simply does not open.
How long to wait
six choices, 24 hours by defaultHours after the occurrence ends. The setting is a plain dropdown with these six values on it, so an afternoon workshop can ask straight away while a late show waits until people are awake.
How long it keeps asking
30 days, then it stopsDay one is the day the event ended. The solid cell is the request going out on the default delay. Dashed cells are past the thirty-day cut-off, where no new request is created: an event you forgot to enable feedback on last spring will not suddenly email three hundred people. A card already sent stays open, so a late reply still counts.
Checked hourly
ProThe queue runs once an hour, which is why the Feedback tab labels its send times as approximate. If you want them gone now, there is a send-now button.
Draft shuts the card
FreeWhile an event sits in draft its card will not open, even for somebody holding the link, and nothing typed into it can be submitted. It is the card that checks and not the queue, so drafting an event after tickets sold is not a way to recall a request already on its way. Draft is on every plan.
Per event, if you want
ProEach event can follow the schedule default, force feedback on, or force it off. Handy for the one night you would rather not ask about. The per-event override
What lands
One email. Two questions.
The request is short on purpose, and so is the card behind it. A rating you cannot skip, a comment you can, and a submit button that stays dead until the rating is marked.
The request
sent from your addressSubject
How was your experience?
Hello Dana,
We would love to hear your thoughts on the event you attended.
Thursday Jazz Session
Thu 18 Jun, 8:00 PM
If that event also collects photos, video or comments from attendees, the same email carries a second link inviting them to add theirs. And if they have allowed web push on your schedule, a notification goes out alongside it.
The card
your logo, colour and fontHow was your experience?
Five stars on the real form, one to five in the database. The card at the top of this page is our drawing of the same value.
Rating *
Comment (optional)
Share your thoughts about the event...
0 / 2000
Submit stays disabled until a rating is marked, so a card cannot come back empty. Open the link again afterwards and you get a thank-you page rather than a second blank card.
Yours, or pinned up
Read them yourself, or pin them up.
One switch, off by default. Leave it off and the cards are private working notes. Turn it on and they become the reviews that help the next person decide whether to come.
Show publicly: off
DefaultNobody else reads them
Cards land on the Feedback tab, in the CSV export, on the webhook and in the API. The event page shows nothing at all, so a rough night stays between you and the person who had it.
This is where most schedules stay, and it is the honest default: feedback you can act on does not have to be feedback everyone can read.
Show publicly: on
ProAttendee reviews on the event page
Attendee Reviews
The 8pm start worked much better.
Sound was spot on. Doors a bit earlier?
Could not hear the announcements at the back.
An average, a count, and the twenty most recent cards, worked out for that event and, on a recurring one, for that date. Each card shows the attendee's first name and nothing more, and cancelled or deleted bookings drop out of the list.
Attendees are told before they write: the card carries a notice saying their words may appear on the event page and their first name will be shown.
Being straight about moderation
There is no per-card approval queue for feedback and no way to hide one card while publishing the rest. Publishing is a single switch on the schedule, which is precisely why it starts off. If per-item moderation is what you need, fan photos, videos and comments do have an approval queue. How fan content is moderated
The returned cards
Every card in one drawer.
The Feedback tab of your Sales page counts what is queued, what has gone out, what has come back and what share of the asking worked.
Pending
12
queued, not sent yet
Sent
41
awaiting a reply
Responded
63
average 4.4 out of 5
Response rate
61%
63 of 104 asked
Sortable by attendee, event, date, rating and submission date. Comments are shortened in the table and printed in full in the export. A card with no comment is still a card: the rating is the required half.
Resend one
A request that landed in a spam folder can be sent again from the row it sits on, for that one attendee.
Send the ready ones now
Everything past its delay but still waiting on the hourly queue can be pushed out immediately from the actions menu.
Or cancel the lot
Changed your mind about a whole batch? Cancel every pending request in one go before any of it leaves.
When one comes back
A card should not sit there waiting to be noticed.
A push, straight away
ProIf web push is switched on for your schedule and you have allowed notifications on a device, a new card arrives as a notification the moment it is submitted. That channel does not wait on email being configured.
An email, if you asked for one
ProSwitch on the New feedback notification and you get the event, the attendee, the rating and the comment by email. On the hosted platform this waits until the schedule has its own email settings, the same requirement as the request. Enterprise schedules can have several admins subscribed.
A webhook, into your own stack
ProSubscribe to feedback.submitted and every card is posted to your endpoint as it lands, carrying the event, the date, the attendee's name and email, the rating and the comment.
Or read it back on demand
ProGET /api/feedback returns the cards for schedules your API key administers, filtered by event, subdomain, date, a minimum rating or a date range. Handy for putting the ratings on a site of your own.
Before any of it goes near a real attendee, send yourself a test card from the schedule's Feedback settings. Where the settings live
The small print
The whole card, terms and all.
Printed on the back, where the small print belongs. Nothing here should surprise you after you have asked three hundred people how it went.
On the hosted platform, feedback emails need the schedule's own email settings saved first, because the request is sent from your address rather than ours. Selfhosted installations have the Pro feature set, so feedback is available there as soon as a real mailer is configured.
Related features
Keep reading
Free forever. Upgrade when you're ready.
Zero platform fees on ticket sales. You only pay Stripe's processing fee.
See all plansFrequently asked questions
Everything people ask before they start asking their attendees.
01 How does post-event feedback work?
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.
02 Who can leave feedback?
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.
03 When does the request go out?
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.
04 Is feedback shown publicly?
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.
05 Can I moderate or delete a card?
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.
06 How many cards does one booking get?
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.
07 Do I need the Pro plan?
Yes. Post-event feedback is a Pro feature at $9 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.
08 Can I get the feedback out of Event Schedule?
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.
Your event, your logo, your colour. The words are theirs.
Free to start
Stop guessing how it went. Ask the room.
Claim your schedule and publish your events for free, forever. Post-event feedback is on the Pro plan at $9 a month, with zero platform fees on anything you sell.
No credit card required