msg2ai.
Guide · uses the Chief Experience Officer skill

How to run a post-event NPS survey and report with Claude

The post-event report is what makes next year's event better — if it gets written. The Attendee Experience skill drafts the survey, plans how it reaches attendees while the experience is fresh, and turns the results and the team debrief into a structured report.

What you'll need

Step by step

  1. Load the Attendee Experience skill. Paste the conference-attendee-experience SKILL.md into a Claude.ai Project, or install all eight skills for Claude Code. Install steps →
  2. Draft the survey. Ask for the post-event survey: the NPS question, the top 3 open-ended questions and session ratings.
  3. Send it while it's fresh. With AI Ambassador, the survey goes out via WhatsApp/SMS within 2 hours of event close.
  4. Capture the debrief. Run the post-event debrief — what worked, what didn't, sponsor feedback, attendee complaints, team retrospective. ActionNotes captures it; with Zoom connected, the skill records the debrief and extracts action items from the transcript.
  5. Generate the report. Claude produces a structured post-event report covering NPS score, top themes, key wins and recommended changes for next year.
  6. Optional: file it for next year. With Google Drive connected, the report, NPS data and debrief notes are stored at 08-attendees/post-event/. With Obsidian connected, a Post-Event Retrospective note links to each skill's retrospective.
Example promptDraft the post-event NPS survey and the post-event report for our committee.

Good to know

From the skill's SKILL.md

The exact instructions the Chief Experience Officer skill gives Claude for this workflow.

Post-Event NPS & Recap Generator (powered by ActionNotes)

Close the loop and build next year's case.

What it covers
  • Draft the post-event survey: NPS question, top 3 open-ended questions, session ratings
  • AI Ambassador sends the survey via WhatsApp/SMS within 2 hours of event close — while the experience is fresh
  • ActionNotes captures the post-event debrief meeting: what worked, what didn't, sponsor feedback, attendee complaints, team retrospective
  • Output: a structured post-event report covering NPS score, top themes, key wins, and recommended changes for next year
  • When Zoom is connected, record the post-event debrief and extract action items from the transcript
  • When Google Drive is connected, store the post-event report, NPS data, and debrief notes at 08-attendees/post-event/
  • When Obsidian is connected, maintain a Post-Event Retrospective note linked to individual skill retrospectives — build institutional knowledge across events
How to build a conference sponsorship prospectus with ClaudeRead the guide →How to write a conference Call for Speakers with ClaudeRead the guide →How to review and rank conference speaker submissions with ClaudeRead the guide →How to build a conference planning timeline with ClaudeRead the guide →

Try it with the Chief Experience Officer skill

Free and MIT licensed. Paste it into Claude.ai in five minutes, or install all eight for Claude Code with one command.