Most customer feedback surveys are forms with a score bolted on — answered by the delighted, the furious, and almost nobody in between. Here are the questions worth asking (CSAT, NPS, CES, and the follow-ups), when to send each, and the response-bias math that decides whether the numbers mean anything.
By the Wavefield Research team · Published Aug 10, 2026
The difference between a customer satisfaction survey you can act on and one that decorates a dashboard is not the questions — everyone asks roughly the same five. It is whether the answers survive scrutiny: who was invited, who actually responded, how big the bases are, and whether a quarter-over-quarter move is real or noise.
That is study design, and customer research gets to skip the hardest part of it: the population is your own customer list, so there is no panel to buy and no screener to write. What remains is the discipline — clean wording, sensible timing, and honest reporting of what a 28% response rate does and does not tell you.
How satisfied were you with your support experience today?
The classic CSAT item: fully labeled five-point satisfaction scale, one specific experience, asked while the memory is fresh. Reported as the top-two-box share.
A working feedback survey is one headline score, one why, and a little context — five minutes at most. These six cover the standard repertoire; no survey should carry all of them at once.
How satisfied were you with your support experience today? (Very dissatisfied – Very satisfied)
The workhorse of transactional feedback: one experience, one fully labeled five-point scale, asked within a day of the interaction. Report the top-two-box percentage with its base size, not a bare average — a 4.2 hides whether you have delighted customers or the absence of angry ones.
How likely are you to recommend us to a friend or colleague? (0–10)
The relationship-level question: promoters (9–10) minus detractors (0–6). Useful as a trended headline number across quarterly waves; nearly useless as a one-off, because a single NPS reading has no context and wide error margins on small bases. Always pair it with the follow-up asking why.
The company made it easy to resolve my issue. (Strongly disagree – Strongly agree)
Effort predicts churn after service interactions better than delight does: people leave over friction more often than they leave over mediocrity. Ask it right after support resolutions, onboarding, or returns — the moments where effort actually varies.
You rated us 6 out of 10 — what would make it a 9 or 10?
The highest-value question in any feedback survey, because it attaches an explanation to a number you already have. One open-end after the headline score, optional to answer, and coded into themes afterward — this is where the fixable problems actually surface.
Which plan are you currently on? / How long have you been a customer?
Scores only become decisions when you can split them: new vs. tenured customers, plan tier, support channel. Two or three closed questions — or better, fields you already hold and can attach to the invitation without asking at all — turn one topline into a diagnosis.
Which of these would improve the product most for you? (Select up to two)
A feedback survey can carry one forward-looking question, and forcing a choice beats a rating grid where everything scores important. Cap selections to force trade-offs, randomize option order, and resist adding more than one — this is a feedback survey, not a roadmap workshop.
The wording rules behind these — balanced scales, labeled points, one thing per question — are covered with examples in survey question types.
Transactional surveys (CSAT, CES) trigger on events and measure a memory before it fades: the support ticket that closed an hour ago, the delivery that arrived yesterday. Send within 24 hours, keep it under two minutes, and suppress repeat invitations so a heavy support user is not surveyed weekly.
Relationship surveys — NPS and the classic quarterly customer satisfaction survey — run on a calendar and measure the accumulated relationship rather than any single interaction. They can afford five minutes, a few priority questions, and honest demographic splits. Their value is the trend: wave two means little until wave three draws the line.
Delivery is its own decision — email invitations with single-use links for accountability, SMS invitations for customers who never open email — and the trade-offs are covered in survey data collection methods. Whatever the channel, one rule holds: every invitation spends a little of the customer's patience, so treat contact frequency as a budget.
Feedback data has a special failure mode: it is usually collected from whoever volunteers, then reported without base sizes to people making real decisions. The four patterns below account for most of the damage:
Feedback surveys are answered by the delighted and the furious; the quiet middle — where churn actually brews — stays silent. A 30% response rate means your score describes a self-selected third. The counters: keep it short, invite systematically rather than via an in-app banner volunteers click, and read scores next to response rates, never alone.
The fastest way to kill future response rates is surveying customers and visibly changing nothing. Every wave should end with an internal owner for each theme, and — for named accounts — closing the loop with the detractors who flagged fixable problems. If nothing changed after the last survey, fix that before fielding the next one.
“How much did you enjoy our award-winning support?” measures compliance, not satisfaction. Neutral framing, balanced scales with a real midpoint, and no brand adjectives inside the question. The wording conventions are the same ones covered in survey question types — feedback surveys just break them more often.
An NPS that moved from 31 to 38 on 42 responses moved by noise. Feedback numbers deserve the same discipline as any survey statistic: report base sizes, compute margins of error, and only celebrate differences that clear them. Score obsession without significance testing is how feedback programs lose executive credibility.
On Wavefield these disciplines are defaults rather than analyst effort: single-use invitation links control who can answer, quotas and quality flags run during fielding, and every report pairs percentages with unweighted bases and computes significance on effective bases. Quarterly waves are first-class too — a tracker duplicates the questionnaire with ids preserved, so trends compare like with like. The full analysis workflow is in how to analyze survey results.
A structured questionnaire sent to your own customers to measure their experience — satisfaction with a specific interaction (CSAT), overall relationship strength and likelihood to recommend (NPS), or the effort a task required (CES) — usually paired with an open-ended question explaining the score. It differs from general market research in that the population is your customer base, which means you control the sample frame and can attach account data instead of asking for it.
A defensible short version: one headline score matched to the survey's purpose (CSAT for a transaction, NPS for the relationship, CES after service), one open-ended follow-up asking why, and two or three segmentation questions — plan, tenure, channel — ideally attached from your records rather than asked. Five minutes is the ceiling; every added question measurably costs completes.
They measure different things at different moments. CSAT measures satisfaction with a specific recent experience, asked immediately after it. NPS measures the overall relationship via likelihood to recommend on a 0–10 scale, asked periodically — quarterly is typical. CES measures how easy a task was, asked after service interactions, and is the strongest churn predictor of the three for support-driven businesses. Mature programs use CSAT or CES transactionally and NPS as the trended relationship headline.
Two clocks, not one. Transactional surveys (CSAT, CES) trigger on events — a support ticket closing, an onboarding finishing — with a suppression rule so no customer is asked more than once every few weeks. Relationship surveys (NPS) run on a calendar, typically quarterly or twice a year, to the whole base or a rotating sample. The binding constraint is fatigue: response rates fall with every contact, so budget invitations like spend.
Related: survey question types · data collection methods · sample size calculator · how to analyze survey results
Upload a brief and the agent builds the questionnaire — clean scales, single-use invites, significance-tested reports. Free to build, from $99 to field — repeat tracker waves are $99 flat.
Start a project