When a new feature rolls out, there’s no shortage of ways to collect feedback—betas, surveys, interviews, Slack threads, the list goes on. We’ve tested a handful of approaches ourselves and found that different moments call for different tactics.

We don’t run every tactic every time. Instead, we pick what fits the feature and the moment. Here are four ways we’ve gathered feedback:

1. Before release: Scope the MVP with an in-app survey

A lightweight survey inside the product can surface what customers actually want in a first version. We keep it short—2–3 questions—and target users most likely to care, based on plan, role, or related usage.

We’ll often ask things like:

• Which parts of this idea matter most (and why)?
• How would it fit into your workflow?
• What’s needed for v1 vs. what can wait?

This helps separate must-haves from nice-to-haves and gives us real language from real users to guide the MVP.

2. Launch day: A guided tour with a micro-survey at the end

When the feature goes live, we announce it with a short tour that highlights only the essentials someone needs to get initial value. At the last step, we drop in a quick survey while the context is fresh.

Questions we use:

• How valuable will this feature be? (1–5 scale)
• How do you plan to use it? (open text)
• What’s missing? (open text)

Pro Tip: Branch the follow-up. If someone says “not valuable,” ask why. If they rate it highly, ask what use case they’re most excited about. The answers are sharper than a one-size-fits-all textbox. If you haven't done branching in a Flow before, here's a click guide 👇

3. On-demand feedback: Add an on-demand feedback pin

Exploration takes time. Insights (and friction) show up after the tour ends, when people return a few times. To catch that, we place a small “Feedback” Button Pin right on the new UI. Anyone can click it to share thoughts whenever they’re ready.

Pro Tip: Give the pin an expiration date. That way it’s available when useful but doesn’t turn into clutter.

4. Out-of-product nudge: Nudge the quiet but engaged with email

Not everyone leaves feedback in-app. For users who have tried the feature a few times but stayed quiet, we send a short follow-up email with a direct link back to the survey. It’s a gentle reminder that their input shapes what comes next.

This brings in thoughtful responses from people who like to reflect after real use—not just in the moment.

Have you met Captain AI (Beta)? He’s making all that feedback more accessible. Instead of digging through raw responses, we ask him to summarize replies, spot themes, and surface insights in record time.

Example prompt if you’d like to try it:

Summarize the top three themes from survey Flow ‘[Flow Name]’ and highlight any standout quotes.