Customer feedback questions that get real answers

Why do feedback forms collect answers you cannot use?

You send a feedback form, a handful of customers answer, and you are left with an average and a few vague comments. Usually the form asked about everything at once, the rating had no reason attached, and nobody can tell which part of the experience the answer was about. Sometimes it is worse, and some of the answers were never given at all, because the form filled them in itself.

Better feedback starts with picking one moment, such as a delivery, a support chat or a cancellation, and asking only about that. If what you need is a score you can track, our guide to the customer satisfaction survey covers CSAT and NPS and how to work them out. This page is about the questions themselves and the answer formats that carry them.

Which customer feedback questions should you ask?

Pick the moment first and then two or three questions for it. The rating tells you how it went, an open question tells you why, and one question about choosing or leaving tells you what you would not have guessed. Ask soon after the moment, while the customer still remembers it.

The two competitor lists we read on 3 November 2026 overlap with these. Fillout's “6 Questions You Should Start Asking in Your Customer Feedback Form” starts with the visitor's goal and whether they found what they wanted, and Loox's product survey list from 2022 asks about satisfaction, use, ease and value for money. Both are good sources of questions. Neither says how many to ask at once, and that is where most forms go wrong. Five questions that each get an answer are worth more than twelve that get skipped.

How do you word a question so the answer is honest?

Ask about one thing per question. “Was our team fast and friendly?” has no right answer for a customer whose reply was fast and rude, so split it in two. Leave your opinion out of the wording, too: “How much did you enjoy your order?” assumes they did, while “How was your order?” lets them say it was bad.

Make the scale easy to read the same way every time. Label both ends of a rating, such as 1 for very poor and 5 for excellent, and keep higher as better across the whole form. Give choice questions a way out, “Not sure” or “Other”, so nobody picks a wrong answer just to get past it.

Put the rating first and the open question right after it, phrased around the answer they just gave: “What is the one thing we should change?” works better than an empty “Comments” box, because it asks for one specific thing. Keep that question optional. A customer who only wants to leave a rating should still be able to send it.

Which answer formats send answers nobody gave?

We asked one rating question in six different formats, plus one open question, and pressed send without touching any of them, in Chromium, Firefox and WebKit. Then we answered all seven and sent again. Every answered format arrived correctly. The untouched ones did not all arrive as “no answer”.

The last two rows are the problem. A slider always has a value, so a customer who never touched it still sends the middle of the scale, and your average drifts towards 3. A dropdown without a blank first option sends whatever is listed first, which here was the best possible score. Both look exactly like real answers when you read them later. Use radio buttons or stars for ratings, as our HTML radio button test explains, and give every dropdown a blank first option with required if the answer matters; the HTML dropdown menu article shows the markup.

Should a feedback form ask for the customer's email?

Ask for it only when the customer agrees to be contacted, and after the questions rather than before. With the questions first, customers can tell you what went wrong before they decide whether they want a reply. A short “May we contact you about your feedback?” with name and email fields that appear after a yes keeps the form short and leaves the choice with them.

Check what that kind of form actually sends. In our own customer feedback template, the name and email fields are hidden with CSS until the customer picks Yes. We tested the case where someone picks Yes, types their name and email, then changes their mind and picks No. The fields disappeared from the screen, but in 3 of 3 browsers the name and email were still sent, and they were in the notification email next to “may_contact: no”. A field hidden with CSS keeps its value and is sent like any other. The fix is to switch the hidden fields off, because disabled fields are left out of the request, as our HTML fieldset test showed. With the script below added, the withdrawn name and email were not sent.

<script>
  // Hidden follow-up fields still send what was typed into them.
  // Switch them off while they are hidden, so a withdrawn email never leaves the page.
  const contact = document.querySelector('[name="may_contact"]');
  const followUps = document.querySelectorAll('[data-show-if="may_contact"] input');
  function syncFollowUps() {
    followUps.forEach((input) => { input.disabled = contact.value !== "yes"; });
  }
  contact.addEventListener("change", syncFollowUps);
  syncFollowUps();
</script>

Does Formgong do anything special with feedback answers?

For the questions, no, and we would rather say so. Good feedback questions work the same in any tool, and both Fillout's and Loox's lists are worth reading. Fillout's guide shows its builder's conditional logic choosing the follow-up question. Formgong's customer feedback template is plain HTML that sits on your own page and needs no script for its one follow-up, the feedback form generator writes a form for your own questions, and every submission is emailed to you with each answer on its own line. That same script-free condition is what let the withdrawn email through in the test above, so add the fix if you use the contact question. For a longer survey with several choice questions, the customer survey template is a starting point.

Which question gave you the most useful answers?

If one question has told you more about your customers than any other, or one format gave you answers you could not trust, write to support@formgong.com. We will test the format the same way and add good questions to the table.