Customer feedback form templates
A customer feedback form asks someone who has already bought, visited or used something how it went, in a shape that produces one number you can track and one comment you can act on. This collection gathers formformform templates built for that task, from a six-question satisfaction survey to post-visit forms for restaurants, shops and hotels, a support-interaction form and three digital-experience surveys — each pinned to a different moment of measurement.
formformform's surveys and feedback category holds 24 templates, running from a three-question newsletter signup to a fourteen-question post-event survey. Customer feedback is one task inside that range: ask someone who has already bought, visited, contacted or used something how it went, in a way that produces both a number you can track across months and a sentence somebody can act on this week. What that something is decides most of the questions, which is why this collection reaches well outside surveys-forms — a support contact is rated in customer-support-forms, a shop visit in retail-forms, a stay in travel-forms, a meal in food-forms, a prototype session in design-forms and a broken page in technology-forms. Employee feedback is deliberately not here: it has its own collection, because a staff survey answers to anonymity and cadence questions a customer survey never has to.
The real axis between these templates is what each one attaches the rating to. The three relationship surveys attach it to nothing at all — customer-feedback-form, customer-satisfaction-survey and nps-survey-form ask no date, no location and no order number, which is what makes them safe to send on a schedule. Everything else is anchored to an event, and the anchor is the giveaway: Date of Interaction and Contact Channel on the support form, Meal Period and Party Size on the restaurant form, Store Location Visited on the retail one, Check-In Date and Check-Out Date on the hotel one, Product or Prototype Name / Version on the UX form, Page URL Where You Noticed the Issue on the website form. The second axis is the scale itself. formformform has no rating or scale field type, so every rating on this page is just a field with its points written out as options — a radio in every case but one — and the wording is not shared between forms. "1 – Very poor" through "5 – Excellent" runs across every row of the usability survey and across three of the five product ratings, while the UX form matches that wording on its Overall Experience row alone and gives its other three ratings scales worded to their own dimension: Very difficult to Very easy, Very unclear to Very clear, Could not complete to Very easy. The restaurant and hotel forms use a four-point Excellent / Good / Fair / Poor for their quality ratings, then switch to a four-point Definitely to Definitely not for the closing would-you-return and would-you-recommend questions; the support form uses that same four-point scale for Agent Knowledge, Agent Friendliness and Resolution Speed but a five-point Very Satisfied to Very Dissatisfied for its Overall Satisfaction; the store form runs five points of Excellent, Good, Average, Below average, Poor. The same thing happens at eleven points on the NPS question: nps-survey-form lists 0 – Not at all likely through 10 – Extremely likely as radio buttons, customer-satisfaction-survey lists the same eleven points in a dropdown. Nothing renders as stars or a slider, and the option labels are plain text you can rewrite.
None of these templates ships with conditional logic, and on a feedback form that is the constraint you will feel first. The follow-up you actually want — "what could we improve?" shown only to someone who answered Dissatisfied, the Agent Name question shown only when the channel was Phone or Live Chat, the Room Number field asked only of a guest who reports something wrong with the room — has to be added in the editor after you clone the template. formformform's template generator writes every field flat and always visible; the product's editor does support branching one field on an earlier answer. It is a couple of minutes per rule, not a missing feature, but it is worth doing before you send: a form that asks every respondent every follow-up question is how you end up with a healthy average score and an empty comment box.
11 templates, and when to use each
Every one is free to open, edit and publish. The line under each name is what separates it from the others here.
- Customer Feedback Form
Start here when you have no particular transaction to attach the answers to — its recommend question is the only one on this page worded as a five-point Very Likely to Very Unlikely radio, and it is not even required; the only rating it does require is a single Overall Satisfaction, and there is no date, order, location or product field anywhere in its seven questions.
Understand what customers love — and what needs fixing.
7 questionsSurveys & Feedback Forms - Customer Satisfaction Survey
Use it when you want a trackable NPS number without asking anything else — at six questions it is the shortest member, the only one that presents the 0–10 recommend scale as a dropdown instead of eleven radio buttons, and the only one that pairs that score with a separate satisfaction question running Very Satisfied to Very Dissatisfied.
Measure loyalty with a simple NPS and satisfaction survey.
6 questionsSurveys & Feedback Forms - Net Promoter Score Survey
Use this NPS instead when one score across the whole company hides the problem — it is the only member with a Which of our products or services did you use? question, complete with an "I'm not yet a customer" option, so the score can be broken down by product line rather than reported as a single average.
Measure customer loyalty with a simple 0–10 NPS question.
7 questionsSurveys & Feedback Forms - Product Feedback Survey
Reach for it when how long someone has owned the thing changes what their rating means — it is the only member that asks a usage-tenure question, running from Less than 1 month to More than 1 year, and it asks it immediately before the five ratings so every score arrives with a tenure attached. It is also the only one that asks whether the buyer would purchase the product again, and the only one that rates Meets your expectations on a scale from "1 – Falls far short" to "5 – Far exceeds expectations".
Gather structured ratings on usability, quality, value, and design.
13 questionsSurveys & Feedback Forms - Customer Service Interaction Feedback
Send this after a support contact rather than after a purchase — it is the only member that records a Date of Interaction, a Contact Channel spanning phone, email, live chat, in-person and social media, and an Agent Name (if known) nobody has to fill in, and the only one where Was your issue resolved? is asked separately from how satisfied the customer felt.
Measure support team performance with structured post-interaction feedback.
12 questionsCustomer Support Forms - Website Usability Survey
Use it on a live site where the respondent is ordinary traffic rather than a recruited tester — it is the only member that asks how the visitor arrived, rates Page loading speed and Mobile experience as their own dimensions, and carries an explicit "N/A – I visited on desktop" option so desktop visitors do not guess at a mobile score.
Collect visitor ratings on navigation, design, content, and speed.
12 questionsSurveys & Feedback Forms - UX/UI Feedback Form
Use it for a moderated session on something that is not shipped yet — it is the only member that records which build was tested, via Product or Prototype Name / Version and a Device Used for Testing dropdown, asks whether this is the tester's first exposure, and makes Points of Confusion or Frustration a required answer.
Gather structured usability feedback from testers during product design reviews.
12 questionsDesign Forms - Website Feedback Form
Put this behind a permanent "report a problem" link — it is the only member with no rating scale at all, collecting instead the Page URL Where You Noticed the Issue, the Browser and Device, a feedback type that includes Accessibility Issue, and whether the problem stopped the visitor completing what they came to do.
Collect bug reports, suggestions, and content errors directly from site visitors.
8 questionsIT & Technology Forms - Restaurant Feedback Form
Use it when the same room performs differently at different times — at fourteen questions it is the longest member here, the only one that pins the visit to a Meal Period and a Party Size, and it rates Food Quality, Service, Ambiance, Value for Money and Cleanliness on one shared four-point Excellent to Poor scale so a bad Tuesday lunch does not disappear into a monthly average.
Collect guest ratings for food, service, ambiance, and value after each visit.
14 questionsFood & Restaurant Forms - In-Store Experience Feedback Form
Use it across more than one branch — it is the only member that asks which Store Location Visited, which is what lets one five-point Excellent, Good, Average, Below average, Poor scale run identically across Staff Friendliness, Store Cleanliness, Product Selection, Checkout Speed and Overall Experience and still be compared between shops, and it marks both name and email optional in the label itself.
Capture in-store customer feedback across cleanliness, staff, selection, and checkout speed.
13 questionsRetail Forms - Hotel Guest Feedback Form
Use it when the thing being rated is a stay rather than a moment — it is the only member that takes a Check-In Date, a Check-Out Date and a Room Number, so a comment about Cleanliness or Amenities & Facilities can be traced back to a specific reservation and a specific room.
Collect structured post-stay ratings and comments from hotel guests.
12 questionsTravel & Hospitality Forms
What these forms ask for
Question labels shared by more than one of the 11 templates above, counted once per template.
- Email Address8 of 11 templates
- What could we improve?4 of 11 templates
- Your Name4 of 11 templates
- Value for Money3 of 11 templates
- Cleanliness2 of 11 templates
- Date of Visit2 of 11 templates
- Ease of navigation2 of 11 templates
- Guest Name2 of 11 templates
- Name2 of 11 templates
- On a scale of 0–10, how likely are you to recommend us to a friend or colleague?2 of 11 templates
- Overall Experience2 of 11 templates
- Overall Satisfaction2 of 11 templates
- Your Name (optional)2 of 11 templates
What these forms are made of
These forms ask between 6 and 14 questions each, and 76 of the 116 questions across the set are required. Field types, counted once per template:
- Email11 of 11 templates
- Long Text11 of 11 templates
- Radio11 of 11 templates
- Short Text11 of 11 templates
- Dropdown6 of 11 templates
- Date4 of 11 templates
How to build a customer feedback form
Decide what one response represents before you write a single question — a whole relationship, or one meal, one support ticket, one stay, one test session — because that alone decides whether you need a date, a location, an order number or nothing identifying at all.
Pick one headline metric and fix its wording permanently: the 0–10 recommend question if you want an industry-comparable NPS, a five-point Overall Satisfaction if you only need your own trend. Rewording it later resets the trend line you were building.
Break the rest into named dimensions instead of one catch-all rating — Food Quality, Service, Ambiance, Value for Money and Cleanliness on the restaurant form; Agent Knowledge, Agent Friendliness and Resolution Speed on the support form — because "it was fine" tells the people who have to fix something precisely nothing.
Set the scale points deliberately, since each one is a radio you are editing by hand: choose four points or five, decide whether a neutral middle is honest or just a place to hide, and add an explicit N/A option for any dimension a respondent might not have used, the way the usability survey does on Mobile experience.
Keep the open questions to two — one for what worked, one for what to change — and put them after the ratings, so the scores are recorded before anyone talks themselves into a longer answer or abandons the form.
Make identity optional unless you genuinely need to follow up, then add branching and a webhook in the editor: reveal the detail questions only to low scorers, and push each submission to wherever complaints are triaged so a one-star rating is not sitting in a dashboard nobody opened.
Who uses these forms
One audience per template, in the order the templates are listed above, taken from what each template names for itself.
Frequently asked questions
Do these templates use star ratings or a 1–5 scale?
Neither, strictly. formformform has no rating or scale field type, so every rating and score question on this page is a Radio field with the points written out as options — the one exception being customer-satisfaction-survey's 0–10 question, which puts the same eleven points in a Dropdown instead. The wording differs from form to form: "1 – Very poor" through "5 – Excellent" covers every row of the usability survey and three of the five product ratings, and the UX form matches it on Overall Experience alone, its other three ratings running Very difficult to Very easy, Very unclear to Very clear and Could not complete to Very easy; the restaurant and hotel forms use a four-point Excellent / Good / Fair / Poor for quality but close on a four-point Definitely to Definitely not; the support form uses that four-point scale for Agent Knowledge, Agent Friendliness and Resolution Speed but a five-point Very Satisfied to Very Dissatisfied for Overall Satisfaction; and the store form runs Excellent down to Poor across five points. That is worth knowing because it is also what makes them easy to change — open the Radio field in the editor and rewrite, add or remove option labels to get a seven-point scale, a differently worded five, or a scale in another language. What you cannot get is a star widget or a slider.
Should a customer feedback form ask for a name and email?
Only if you intend to reply. Several members here answer that in the label rather than in the settings — the support form reads "Your Name (optional)" and "Email Address (optional)", the store form spells the same thing out as "Email Address (optional — for follow-up if needed)", and the usability, NPS and satisfaction surveys simply leave both fields unrequired. The hotel and product forms require both name and email, because a stay or a warranty claim has to be traceable; the restaurant form goes half way, requiring Guest Name but leaving Email Address optional. If you do collect contact details, formformform hosts responses in the EU and supports GDPR obligations, and you can switch on optional end-to-end encryption per form. Do not treat any of that as a SOC 2 or ISO 27001 claim — those belong to the hosting provider, not to us.
What is the difference between the NPS survey and the customer satisfaction survey here?
They ask the same 0–10 recommend question and diverge immediately after. customer-satisfaction-survey is six questions and pairs the score with a separate overall-satisfaction question rated Very Satisfied to Very Dissatisfied, which gives you two numbers about the relationship as a whole. nps-survey-form instead adds "Which of our products or services did you use?" — with options down to "I'm not yet a customer" — plus a free-text product name, so the score can be split by line rather than reported as one company-wide average. If you sell one thing, take the shorter one.
Can I show a follow-up question only to customers who rate us badly?
Yes, but you add it yourself after cloning. No template in formformform's library arrives with conditional logic — the generator writes every field flat — while the editor supports branching a field on an earlier answer. So clone the template, then add a rule that reveals "What could we improve?" only when Overall Satisfaction is Dissatisfied or Very Dissatisfied, and another that shows the Email Address field only once someone has said they want a reply. Same technique for the support form's Agent Name (if known) field, which is only worth asking about a phone or live-chat contact.
Can a customer attach a photo of the problem — a damaged item, a broken page?
Not from the template as generated, but yes in the product. formformform's editor has a File Upload field, capped at 2 MB per file and encrypted on encrypted forms; it is simply not one of the field types the template generator can emit, so nothing on this page arrives with one. Clone the template and drag Upload in from the editor palette. The website feedback form shows the alternative if you would rather not receive files at all: it asks for the Page URL and the Browser and Device as plain text, which is usually enough for a developer to reproduce the fault.
Keep browsing
All Survey & Feedback form templates24 templates
Build yours in a few minutes
Open any template above, change what you need, and publish. Free during early access — no credit card, and no cap on how many responses a form can take.
Start free