A conference feedback survey for next year’s program
Conference feedback is easy to collect and hard to use. A rating per session tells you which talks were liked, not why, and nothing about the hallway, the venue or the people attendees came to meet. Asking about each part of the event separately gives the program, operations and sales teams something to act on.
What should conference organizers ask first?
| Ask | Why it matters |
|---|---|
| How was the conference overall? | One rating to compare years and sort the responses. |
| Which session was the most useful to you, and why? | The reason tells the program team what to book again. |
| Was any session not what its description promised? | A mismatch is fixable in the description, the speaker brief or the level. |
| Did you meet the people you came to meet? | For many attendees, networking is the reason they bought a ticket. |
| How were the venue, food and schedule? | Operations feedback belongs with the operations team, separate from the content. |
| Would you come back next year, and what would make that more likely? | The answer that decides next year’s early-bird list. |
If an answer would not change what you do next, leave the question out. Each extra question is one more reason for someone to stop before they finish.
Which answers come back too vague to use, and what do you ask next?
The answers that cause a phone call are rarely missing. They are present and too loose to act on. A narrower follow-up, asked straight away while the person is still there, usually settles them. Offering likely answers shows the person the level of detail you need.
| What comes back | The follow-up that settles it |
|---|---|
| “Great event!” | What was the one session or conversation that made it worth the trip? |
| “Some talks were too basic.” | Which ones, and what level would have been right for you? |
| “Networking was hard.” | Was it finding the right people, having time between sessions, or the space itself? |
Follow up once per gap, then move on. If an answer is still unclear after one follow-up, flag it for whoever picks the request up rather than pressing.
When is a call or a visit still the right move?
A sponsor, a speaker or an attendee with a complaint about conduct needs a direct conversation, not a survey. For everyone else, the survey is the conversation, and it reaches people while the event is still fresh.
How do you set this up from the Post-webinar feedback template?
Acquainto has a Post-webinar feedback template to start from. After you sign up, open Browse templates, pick Post-webinar feedback, and it lands in the editor as a draft you can change before anything is published.
This template is close to the job. It asks for an overall rating, whether the content matched expectations, which topics to cover next (product deep-dives, case studies, industry trends or Q&A sessions) and any other feedback, and branches on a mismatch: an attendee who says no is asked what they were hoping to see instead. Replace the topic list with next year’s tracks, and add the most-useful-session, networking, logistics and come-back questions. Send it within two days of the event.
To see it from the other side, answer a demo built from the questions on this page. It is a demo: your answers come to Acquainto, not to a business, so leave out real names and contact details.
Acquainto runs it as a short written conversation instead of a form. It:
- asks a follow-up when an answer is incomplete, and asks for clarification when one is vague;
- uses a structured choice where precision matters and open conversation where detail matters;
- shows the person every answer before it is sent, so they correct their own mistakes;
- hands back one clean value per question, delivered to your own systems by webhook.
The person answering needs no account, and nothing has to be scheduled. Start free trial, see how it works, or compare plans.