A feedback form builder for answers you can act on

Four parts, in this order. First, one line of context: what the feedback is about and who reads it. Second, the core score, worded exactly the same every time. Third, one open question: what is the main reason for your score? Fourth, optional context such as which product, location or agent, and permission to follow up.

Leave out anything you will not act on. Demographics, marketing opt-ins and testimonial requests each belong in a different form, or at least after the feedback is complete. If you already know who the person is (an order number, a ticket ID), pass it in the link as a hidden field rather than asking for it. Zunoform's hidden fields capture URL parameters into the response, so the form stays short and the answer still arrives tied to the right order.

Illustration: 80 customers answer a CSAT question after support tickets. 52 answer 5, 12 answer 4, 8 answer 3, and 8 answer 1 or 2. CSAT is (52 + 12) / 80 = 80%. The same 80 people also answer a 0 to 10 recommend question: 40 promoters, 24 passives and 16 detractors, so NPS is 50% minus 20%, or 50. Neither number tells you what to fix; the 16 open answers from the detractors do. That is why the open question is the one you should never cut.

Closing the loop means two things: replying to the individual who gave a low score, and telling everyone what changed. The first is service recovery with an expiry date, so it needs routing, not a monthly report. The second is what keeps people answering your next survey.

In Zunoform, the practical setup looks like this. A logic rule shows "What went wrong?" and "May we contact you?" only when the score is low. A tag rule labels those responses, for example "detractor" when the recommend score is 6 or below; tags are computed on the server at submission and appear in the responses view. The response then goes where your team already works: Google Sheets, Zoho CRM, a Zapier catch hook or a webhook on the free plan, or Slack, HubSpot, Notion and Airtable on Pro. Email notifications work on Free through your own SMTP server and on paid plans through Zunoform's mailer.

For the public half, a short note in your next newsletter or changelog is enough: you told us checkout was confusing, so we cut it from four steps to two. Keep a simple log of what feedback led to which change; it is also the best evidence when someone asks whether the survey is worth running.

For employee and internal feedback, usually yes, because people answer more candidly when they cannot be identified. For customer feedback, usually no, because you cannot fix a specific problem for someone you cannot reach. Decide per form, then say which it is at the top.

If you promise anonymity, make it real. Zunoform's anonymous mode stores no IP address, user agent, referrer, location, language or screen size for that form. That still does not protect someone who types their name into an open question, or who is the only person on a three-person team, so avoid questions that identify people by elimination. Our anonymous surveys guide covers this in detail.

Zunoform works well when feedback needs logic, routing and a few integrations without a survey platform's price: rating and star questions, conditional follow-ups, tag rules, anonymous mode, hidden fields and 500 responses a month are all on the free plan, and the NPS question, Slack and HubSpot come with Pro at $14.99 a month.

It is not the right choice if you need unlimited free responses (Google Forms and Tally have no monthly cap), statistical text analysis or dashboards across many surveys (dedicated survey platforms do this better), or automatic survey sends triggered from your help desk; you send the link yourself or through your own tools.