A post-webinar feedback survey that tells you what to change
A webinar rating says how the hour felt. What the next webinar needs is narrower: did the session deliver what the invitation promised, what did attendees come for instead if it did not, and what would bring them back.
What should teams running webinars ask first?
| Ask | Why it matters |
|---|---|
| Did the session cover what the invitation promised? | A mismatch between the title and the content is a common problem, and an easy one to fix in the copy. |
| If it did not, what were you hoping to see instead? | The expectation is the topic of a webinar people already want. |
| Was the level right: too basic, about right, or too advanced? | It tells you whether to split the audience or change the speaker’s pitch. |
| Which part was most useful to you? | The part people name is the part to keep, and often the clip to share afterward. |
| Did you stay to the end? If not, when did you leave? | Where people drop off is where the session lost them. |
| What should the next one cover? | Attendees who say what they want next are the first invitations to send. |
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 |
|---|---|
| “It was good.” | What is one thing from it you expect to use, or pass on to someone else? |
| “Too much product.” | Was it the amount of demo, or that the demo came before the part you came for? |
| “More examples.” | Examples from which kind of company or role, so they look like yours? |
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?
An attendee who asks a buying question in the chat, or whose answer says they are evaluating a product like yours, should hear from a person, not a survey. The survey finds them. For everyone else it is the feedback, and it arrives while the session 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 built for 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 your own series, and add the level and the most-useful-part questions.
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.