Responses + CSV
Read what users told you. Every survey answer and form submission is summarized — averages, NPS, and choice tallies — and you can export the raw responses to CSV anytime.
from 318 responses
Summarized for you
Averages, NPS scores, and choice tallies, automatically.
Every raw response
Browse individual submissions, not just totals.
Export to CSV
Take the raw data anywhere you need it.
Live in three steps.
Collect answers
Run surveys and forms.
Read the summary
See the numbers add up.
Export
Download the raw CSV.
From verbatims to a roadmap argument.
Quarter-end: leadership wants evidence, not vibes. Your in-product surveys have been collecting all quarter — here is how the responses become the argument.
Start with the summaries
Responses shows each survey's shape at a glance: the NPS average and its full 0–10 distribution, choice tallies ranked, rating averages with their spread.
Read the distribution, not the average
A "7.4 average" hiding a promoter/detractor split is a different company than a uniform 7. The bar chart tells you which one you are.
Chase the verbatims
Open-text answers sit next to the user who wrote them — name, email, traits. Twelve detractors mentioning the same export bug is not sentiment; it is a ticket with a customer list attached.
Export for the deck
CSV export hands the raw rows to whoever asks — analysts, finance, the board deck. Answers, users, timestamps, guide of origin: everything the pivot table needs.
What to expect: Feedback becomes citable: "NPS 41, n=312, top detractor theme is export reliability — here are the accounts." That sentence wins roadmap meetings that adjectives lose.
When not to use responses + csv.
No pattern fits every job. Here’s where we’d point you at something else — sometimes ours, sometimes not.
As a support inbox
Responses collect and organize; they do not open tickets or send replies. A detractor mentioning a bug deserves a human follow-up through your support tool — pipe the signal there, do not let it rot in a table.
Live operational dashboards
This is a reading room for feedback, not a streaming metrics wall. For always-on dashboards, export to CSV or stream events through integrations into your BI stack.
Anonymous research panels
Responses shine because they attach to real accounts. If your study requires guaranteed anonymity, run it in a dedicated research tool — identity here is a feature you would be fighting.
How are different question types summarized?
Ratings and NPS show the average plus the full distribution (read the distribution — NPS especially, where 0–6 are detractors and 9–10 promoters). Multiple choice shows a ranked tally. Form steps show collected fields with each full submission in the table.
Can I tell who said what?
Identified users appear with name or email; otherwise their ID; otherwise "anonymous". Identity is what turns a complaint into a follow-up — you know the plan, tenure, and account behind every verbatim.
What does the CSV contain?
The raw response rows — question, answer, user, timestamp, source guide — ready for spreadsheets or your warehouse. Project-wide or per guide, exported whenever you need it.
Responses are empty — what did I miss?
Work backwards: is the survey published, is the SDK detected on the Install page, does the audience/trigger ever match, and has anyone actually finished the survey step? The pipeline fills in the order people answer.
Can responses flow into my other tools automatically?
Two paths: signed webhooks stream events out as they happen — a new survey response can land in Slack or your CRM within seconds — and the warehouse export covers bulk analysis. The CSV button stays the manual fallback for one-off asks.
See it on your own app.
Ship your first guide in minutes. Free to start — no credit card.