Customer Feedback Survey: The Complete Guide (Templates, Examples, Software)

A customer feedback survey is the cheapest way to find out why people churn, what they wish you'd build, and whether your product is actually solving the problem you think it is. It's also the easiest thing to get wrong. Most surveys go out to thousands of customers, get a 3% response rate, produce a pile of data nobody acts on, and quietly stop happening six months later.

This guide is the opposite. It covers what a customer feedback survey actually is, when to send one, what to ask, the templates that consistently get 25%+ response rates, and the software worth paying for. Everything here works at the scale a solo founder or small SaaS team operates at — no enterprise survey tooling required.

#What Is a Customer Feedback Survey?

A customer feedback survey is a structured way to ask paying users about their experience with your product. It can be one question or twenty. It can go out via email, in-app widget, post-purchase popup, or a link in a chat reply. The format matters less than the discipline behind it: ask a clear question, at the right moment, to the right person, and actually read the answers.

Most teams confuse "survey" with "survey tool." They sign up for Typeform or SurveyMonkey, build a 12-question form, send it to their whole customer list, and then act surprised when 4% of people respond. The survey tool is the easy part. The hard part — and the part that decides whether your survey produces anything useful — is the design choices behind it.

The four major categories of customer feedback survey are:

• Customer satisfaction (CSAT) — sent immediately after a specific event (purchase, support ticket close, feature use). Measures how satisfied a customer was with one thing.
• Net Promoter Score (NPS) — sent quarterly or semi-annually. Asks "how likely are you to recommend us?" on a 0–10 scale. Tracks loyalty over time.
• Customer Effort Score (CES) — sent after a specific interaction. Asks "how easy was it to get your issue resolved?" on a 1–7 scale. Identifies friction.
• Product feedback — open-ended. Asks what users want built, what's broken, what they're confused about. Drives the roadmap.

Each one answers a different question. Most teams pick one or two and stick with them. Running all four at the same time will overwhelm both your customers and your team — and you'll learn less, not more.

#When to Send a Customer Feedback Survey

Timing is the single biggest lever in survey response rates. Ask the right question at the wrong moment and you'll get silence. Ask the right question at the exact right moment and you'll get a paragraph back.

Within an hour of a support ticket closing. The customer just spent time explaining a problem and watching you solve it. They have a strong, fresh impression. A CSAT or CES question sent inside the same hour captures that impression before it fades. Wait 24 hours and most of the signal disappears.

Day 7–14 after signup. This is the onboarding window. Too early and they haven't formed an opinion. Too late and the initial impression has faded and they've moved on. Days 7–14 hit the sweet spot — they remember signing up, they've actually used the product, and they have a real reaction worth capturing.

Immediately after a key feature gets used for the first time. If a customer just exported their first report or invited their first teammate, that's the moment to ask "did that work the way you expected?" The answer tells you whether your most important workflows are clear or confusing.

At cancellation. The exit survey is the most valuable feedback you'll ever collect, and almost nobody does it well. When someone cancels, you have one shot to learn why. Even if you can't win them back, the answer shapes your roadmap.

Quarterly NPS for active users. Once a quarter, ask paying customers a single NPS question. Tracking the score over time tells you whether your product is getting better or worse — independent of what you think about it.

What you should not do: send the same survey to your entire list every month. It trains people to ignore your surveys. The teams that get the highest response rates send fewer, smaller, more targeted surveys.

#How to Design a Customer Feedback Survey That Gets Answered

The single biggest predictor of a good response rate is the number of questions. One question gets 25–40% response. Three questions get 10–15%. Ten questions get 3–5%. Twenty questions get whatever you'd get from an unsolicited cold email.

Follow these rules:

• One question only, whenever possible. A second question costs you 30% of your responses. A third costs another 30%.
• Make the first question a closed scale (1–5, 1–10, or yes/no), then offer an optional open-ended follow-up. People click numbers easily. They write paragraphs only when they care.
• Plain text, not branded HTML. A plain-text email from a real human feels like a personal note. A branded email with header images, footers, and CTA buttons feels like a blast. Plain text gets 2–3x the response rate.
• Send from a real person. [email protected] outperforms [email protected] by a wide margin. Use the founder's name if you're solo.
• Acknowledge that one sentence is enough. Adding "even a quick one-liner helps" removes the psychological barrier of "I don't have time to write an essay."
• Don't promise prizes or discounts in exchange for survey responses. It biases the answers and attracts deal hunters. Trust the relationship.

The best feedback emails read like a personal message that happens to include a single question. They do not read like a corporate survey form.

#Customer Feedback Survey Templates

Each template below is short, specific, and gets a 20%+ response rate in practice. Copy and adjust for your context.

#Template 1: Post-onboarding (send day 7)

 1Subject: Quick question about your first week
 2
 3Hi {{ first_name }},
 4
 5You've been using [Product] for about a week now. Wanted to check in with one
 6question, no survey link:
 7
 8What's one thing about [Product] that hasn't clicked yet?
 9
10Even a quick reply helps — we read everything.
11
12— [Founder name]

#Template 2: After a support conversation closes

 1Subject: Was that helpful?
 2
 3Hi {{ first_name }},
 4
 5Thanks for writing in earlier about {{ issue_summary }}. Quick one:
 6
 7On a scale of 1–5, how would you rate the help you got? (1 = bad, 5 = great)
 8
 9If you have a sentence on why — even better. No pressure.
10
11— [Support agent name]

#Template 3: Quarterly NPS

 1Subject: How likely are you to recommend [Product]?
 2
 3Hi {{ first_name }},
 4
 5We send this question once a quarter. It's the most important one we ask.
 6
 7On a scale of 0–10, how likely are you to recommend [Product] to a colleague?
 8
 9(If you have 30 seconds to tell us why your score is what it is, that's the
10most useful thing you can do for us this week.)
11
12— [Founder name]

#Template 4: Feature use feedback

 1Subject: How's the {{ feature_name }} working?
 2
 3Hi {{ first_name }},
 4
 5I saw you tried out {{ feature_name }} for the first time yesterday. Just want
 6to ask one thing:
 7
 8Did it do what you expected?
 9
10If yes, no need to reply. If no, hit reply with what happened — I'll get it
11fixed.
12
13— [Founder name]

#Template 5: Exit survey (sent at cancellation)

 1Subject: One question before you go
 2
 3Hi {{ first_name }},
 4
 5Sorry to see you cancel. We don't do "win-back" emails — you've made your
 6decision and we respect it.
 7
 8But before you go, would you tell us in one sentence what made you cancel? It
 9shapes what we build next, and we'd really value the answer.
10
11— [Founder name]

These five templates cover the five highest-leverage feedback moments in a SaaS lifecycle. If you run nothing else, run these.

#Customer Feedback Survey Software

The right software depends on what you're actually trying to do. Most teams over-buy here — they grab Qualtrics or SurveyMonkey when a plain-text email from their own domain would outperform either tool.

For most early-stage SaaS — under $20K MRR, under 1,000 paying customers — plain-text email from your own domain plus a CSAT widget in your support tool beats every paid survey platform. You'll get higher response rates, no learning curve, and zero monthly bill. Upgrade to a dedicated tool when survey volume actually justifies it.

Looking for a feedback loop, not just a survey tool? ShipTell ships customer feedback collection (CSAT after every support reply, feature voting on a public board, and automatic notifications when you ship what someone asked for) as part of a $19/mo platform. Start a 7-day free trial.

#Customer Feedback Survey Examples (What Good Looks Like)

The hardest part of running a feedback survey isn't the tool — it's the question. Here are three examples of good survey questions, alongside the bad versions teams usually run by default.

Bad: "How are we doing?" Good: "What's one thing about [Product] that's been confusing this week?"

The first is so vague it can't be answered. The second points the customer at something specific and signals you actually want the honest answer.

Bad: "Please rate your overall experience on a 10-point scale based on the following criteria: ease of use, value for money, customer service, feature breadth, reliability, design quality..." Good: "On a scale of 1–5, how easy was it to get your issue resolved today?"

The first is a survey designed to make the team feel comprehensive. Nobody fills it out. The second answers a specific question that you can actually act on.

Bad: "We'd love to hear your thoughts on our recent product changes! Please take this 10-minute survey to help us understand what we should build next." Good: "We're deciding what to build in the next quarter. What's one thing you wish [Product] did that it doesn't yet?"

The first is bureaucratic. The second invites a real opinion.

#How to Close the Loop on Customer Feedback

Collecting feedback is the easy half. Acting on it — and telling the customer that you acted on it — is the half almost every team skips. Here's the brutal math: a customer who suggested a feature six months ago, and got radio silence in return, is far more likely to churn than a customer who never suggested anything in the first place. Asking and then ignoring is worse than not asking.

The closed-loop process looks like this:

1. Capture every request with the contact info attached. Not in a Notion doc detached from the customer. In a system that knows which customer asked for what.
2. Surface duplicates. When customer #14 asks for the same thing customer #1 asked for, group them — that's how you know it's worth building.
3. Update the original requester when you actually ship. This is the step almost everyone skips. It's also the one that builds the most loyalty.

Most feedback management systems handle step one. Almost none handle step three automatically. ShipTell's feature request board does — when you publish a changelog entry that maps to an open feature request, every voter gets an email automatically. The loop closes itself.

#What to Avoid

A few practices look reasonable but consistently hurt response rates and data quality:

Don't promise rewards. "Take our 5-minute survey for a chance to win a $50 gift card" attracts deal hunters and biases the data. The customers whose opinions you actually want will not be motivated by $50.

Don't run the same survey monthly to your entire list. People get fatigued. They stop opening anything that looks like a survey from you. Vary the trigger and vary the question.

Don't aggregate feedback into a quarterly report you read once and forget. Feedback only matters if it shapes a decision within 30 days. If your survey results sit in a dashboard nobody opens, you're collecting data, not running a feedback loop.

Don't ask leading questions. "How much did you love the new dashboard?" gets you positive answers because you primed for them. "What's one thing about the new dashboard that didn't work for you?" gets you actionable answers.

Don't survey churned users with the same email blast as active users. They've left. Send them an exit survey, not your quarterly NPS — and respect that they may not respond at all.

#Bottom Line

A customer feedback survey works when it asks one specific question, at the right moment, from a real person, and the team actually reads and acts on the answers. Almost every other pattern produces low response rates and a dataset nobody uses.

For solo founders and small SaaS teams: skip the survey software for now. Run plain-text emails from your own domain at the five trigger moments above. Run CSAT inside your support tool. Run quarterly NPS on a 30-question-free format. Read the answers. Act within 30 days. That's the entire system.

If you want feedback collection that wires into your support inbox, your roadmap, and your changelog automatically — so the request a customer made in March turns into an email notification the day you ship in May — give ShipTell a try free for 7 days.