Customer feedback form template
Feedback forms lose responses to length. A five-field feedback form gets a fraction of the completions a two-field one does, because most people giving feedback are doing it as a favor, not a task they're invested in. This template is one rating question and one open comment, which is close to the minimum that's still useful.
Copy-paste HTML
<form action="https://send.webforms.to/wft_your_key" method="POST">
<fieldset>
<legend>How would you rate your experience?</legend>
<label><input type="radio" name="rating" value="1" required> 1</label>
<label><input type="radio" name="rating" value="2"> 2</label>
<label><input type="radio" name="rating" value="3"> 3</label>
<label><input type="radio" name="rating" value="4"> 4</label>
<label><input type="radio" name="rating" value="5"> 5</label>
</fieldset>
<label for="comment">What could we do better? (optional)</label>
<textarea id="comment" name="comment"></textarea>
<label for="email">Email (optional, if you'd like a reply) (optional)</label>
<input type="email" id="email" name="email">
<button type="submit">Submit</button>
</form>Replace https://send.webforms.to/wft_your_key with your own endpoint from the WebForms dashboard.
Why these fields
- Email is optional and explicitly framed as "if you'd like a reply," not left unexplained. An unexplained email field on a feedback form reads as data collection and measurably suppresses completion; explaining why you're asking recovers most of that.
- The open comment is framed as "what could we do better," not "any comments" - a specific prompt gets specific, actionable answers, where an open-ended one tends to get either nothing or vague praise.
Where to send it
Get your endpoint
Free for 300 submissions a month. No card required.
Start freeCustomer feedback form FAQ
1-5 gets more completions for a general feedback form because it's a faster decision to make. Save 1-10 (classic NPS) for when you specifically need to benchmark against the NPS methodology, since the extra granularity mostly matters for that comparison, not for reading individual responses.
Routing rules on paid plans can send low ratings (say, 1-2) to a Slack channel or webhook immediately, while higher ratings just get logged - so a bad experience gets seen fast without every rating needing the same urgency.