The best customer satisfaction survey questions are short, specific, and tied to a single thing you want to learn. A good survey usually runs under ten questions, leads with one clear rating question, and pairs every score with an open field so the number tells you something is wrong and the comment tells you what. Below is a question bank you can pull from, organized by what you are trying to measure, followed by a template you can send this week.

This is written for people who run the survey, not just design it: support leads, onboarding managers, and ops teams who have to act on the answers. Every question here is picked because the response points at something you can actually change.

What questions should be on a customer satisfaction survey?

A customer satisfaction survey should include one primary rating question, one or two targeted follow-ups tied to the interaction you are measuring, and at least one open-ended question. The rating question gives you a trackable score, the follow-ups tell you which part of the experience drove it, and the open field surfaces the reasons you did not think to ask about. Keep the total under ten questions so people finish it.

Do not try to measure everything in one survey. A survey sent after a support ticket should ask about that ticket, not about pricing, the product roadmap, and the sales process. Match the questions to the moment, and send it within a few hours of the interaction while the experience is still fresh.

Customer satisfaction survey questions by type

Most survey questions fall into a few reliable categories. You do not need all of them. Pick the ones tied to the goal of this specific survey.

Overall satisfaction (CSAT)

CSAT questions capture how a customer felt about a specific experience. They work best sent right after an event, while it is fresh.

  • "How satisfied were you with your overall experience?"
  • "How satisfied are you with the product?"
  • "How satisfied were you with the support you received?"
  • "How well did our product meet your needs?"
  • "How satisfied are you with the value you get for the price you pay?"

Use a simple, consistent scale, typically 1 to 5 from "very dissatisfied" to "very satisfied." CSAT is the share of respondents who pick the top two options, so keep the scale the same across surveys or your trend line breaks.

Loyalty (Net Promoter Score)

NPS measures the whole relationship rather than a single event, so send it at checkpoints like renewal, not after one interaction.

  • "How likely are you to recommend us to a friend or colleague, on a scale of 0 to 10?"
  • "What is the main reason for your score?"

The follow-up "why" question is where the value is. A number on its own tells you the temperature; the reason tells you what to fix.

Effort (Customer Effort Score)

Effort questions are often the most actionable in the whole survey, because a high-effort answer points straight at a broken step.

  • "How easy did we make it to resolve your issue?"
  • "How much effort did you personally have to put in to get your problem handled?"

Effort predicts loyalty better than delight does. Customers rarely reward you for a smooth experience, but they leave over a painful one. If you want to run effort as its own metric, our guide to the Customer Effort Score survey and formula covers the exact wording and timing.

Product and feature questions

  • "Which feature do you use most often?"
  • "Which feature, if we removed it tomorrow, would you miss the most?"
  • "What is one feature you wish we had?"
  • "How well does the product fit into the way you already work?"

Support and service questions

  • "Was your issue resolved on the first contact?"
  • "How knowledgeable was the person who helped you?"
  • "How long did it feel like you waited for a response?"
  • "Did you have to explain your issue more than once?"

The "explain more than once" question is worth its weight. Repeated explanation is one of the most common and most fixable causes of a bad support experience, and it usually traces back to how conversations are handed off between people or channels.

Open-ended questions

  • "What is the one thing we could do to improve your experience?"
  • "What almost stopped you from buying or signing up?"
  • "What did you expect that did not happen?"
  • "Is there anything you were hoping to tell us that we did not ask about?"

Every structured score should be paired with at least one open field. The number tells you something moved; the text tells you why. Read these comments and group them into themes rather than skimming for the flattering ones.

How many questions should a customer satisfaction survey have?

Keep a customer satisfaction survey under ten questions, and shorter is usually better. Most transactional surveys work best with one rating question and one open-ended follow-up, which takes under a minute to complete. Longer surveys have lower completion rates, and every extra question you add to satisfy internal curiosity costs you responses from the customers you most want to hear from. Ask only what you will act on.

There is a simple test for each question: if a bad answer would not change anything you do, cut it. A survey is not a research project. It is a decision tool, and every question that does not lead to a decision is just fatigue.

What is a good CSAT score?

A CSAT score between 75% and 85% is generally considered good, though the benchmark varies by industry and by how you word the question. More important than the absolute number is the trend: a CSAT that is climbing tells you your changes are working, and one that is slipping is an early warning worth acting on before it shows up in churn. Compare your score against your own baseline first, and against industry benchmarks second.

Survey design rules that protect your data

The questions only work if the survey around them is built well. A few rules do most of the work.

Avoid leading questions. "How amazing was our service?" invites a polite lie. "How satisfied were you with our service?" invites the truth. Neutral wording is the difference between data you can trust and data that flatters you.

Ask about one thing at a time. "How satisfied were you with the speed and quality of support?" is two questions wearing one coat. If the answer is low, you cannot tell which half is broken. Split it.

Use a consistent scale. Switching between 1 to 5, 1 to 7, and 0 to 10 across surveys makes your numbers impossible to compare over time. Pick a scale per metric and keep it.

Send it at the right moment. A support CSAT belongs right after the ticket closes. An onboarding CSAT belongs at the end of onboarding. A relationship NPS belongs near renewal. Timing decides whether the answer is about the thing you think it is about.

Close the loop. Tell customers what changed because of their feedback. It is the single most reliable way to keep response rates from decaying, because it proves the survey was not a waste of their time.

A short customer satisfaction survey template

Here is a transactional template you can adapt and send after a support interaction or an onboarding milestone. It is deliberately short.

  1. Overall rating (CSAT): "How satisfied were you with your recent experience?" (1 to 5 scale)
  2. Effort (CES): "How easy did we make it to get what you needed?" (very difficult to very easy)
  3. Resolution: "Was your issue fully resolved?" (yes / no / partly)
  4. Open-ended: "What is the one thing we could do better?" (free text)

For a relationship survey sent near renewal, swap question one for the NPS question ("How likely are you to recommend us, 0 to 10?") and keep the open-ended "why" follow-up. That is a complete, usable survey. Everything beyond it is refinement.

What to do with the answers

Collecting the responses is the easy half. The half that changes anything is routing each theme to the team that can fix it. A run of complaints about a confusing invoice belongs with the people who own the billing experience, not buried in a summary deck. Repeated support frustration usually points at how conversations are triaged and handed off, which is easier to see once you are reading the volume through a well-managed shared inbox rather than scattered across mailboxes.

These surveys are also one input into a bigger picture. Individual scores are useful, but they are most valuable inside a wider voice of customer program, which decides where to listen and how feedback becomes action, and alongside the operational numbers in our guide to the customer service metrics and KPIs to track. A survey score tells you how customers feel. The operational metrics underneath it usually tell you why, and often move first.

The point of the survey

A customer satisfaction survey is not a report card. It is a way to find the next thing to fix. Keep it short, ask only what you will act on, pair every score with an open comment, and route what you learn to the people who can change it. That routing is the start of a wider customer feedback loop: the survey collects the signal, and closing the loop is what turns it into a fix the customer actually notices. Do that consistently and the survey stops being a number you present in a meeting and starts being the reason the experience gets better, which is the only outcome that was ever worth measuring. For the wider view of where all of this fits, our foundational piece on why customer experience is won in the back office connects the survey to the operations that actually deliver the experience.

D
Daniel Voss
Support operations writer.