Customer survey questions for every stage of the journey

Before you write questions, list the moments in your customer journey where opinions form: first visit, purchase, first use, first problem, renewal, cancellation. Each moment gets its own short survey sent right after it happens. A single long yearly survey cannot tell you which moment caused a problem.

Keep each survey short: three to six questions, with one rating and one or two open questions. Send it as close to the moment as possible, while the experience is still fresh.

Use these on your site or right after a first purchase. They show what brought people in and what nearly stopped them.

• How did you first hear about us?
• What problem were you hoping to solve?
• What other options did you consider?
• What almost stopped you from buying today?
• Was any information missing from our site?
• What finally made you decide?

Open version for voice or video: "Tell us what you were looking for when you found us, and what made you choose us in the end."

To ask visitors before they buy, website survey tools show a short survey inline, as a popup or as a side tab on the pages you choose.

Send these a few days after purchase or signup.

• Were you able to get started without help?
• How easy was setup, from 1 to 5?
• What did you expect to happen first that did not?
• Which step took the longest?
• Did you contact support during setup? Why?
• What would have made the first week easier?

Open version: "Walk us through your first time using the product. Where did you feel confident, and where did you have to guess?"

Send these right after a ticket closes or a chat ends.

• Did we solve your problem?
• How satisfied are you with the help you got, from 1 to 5?
• How much effort did it take to get your issue resolved?
• How many times did you have to contact us about this issue?
• Was the person helping you knowledgeable?
• What could we have done better?

Open version: "Tell us how this support conversation went from your side. What helped, and what was frustrating?"

Use these on a regular schedule or after key milestones. The classic CSAT question is a rating with one open follow-up.

• How satisfied are you with [product or service] overall, from 1 to 5?
• What is the main reason for your rating?
• Which part of the product or service works best for you?
• Which part disappoints you most?
• How well does the product meet your needs, from 1 to 5?
• What one improvement would make the biggest difference?

For a full program with scheduling and reporting, see our customer satisfaction survey software page.

• How likely are you to recommend us to a friend or colleague, from 0 to 10?
• What is the main reason for your score?
• How likely are you to renew or buy again?
• What would make you switch to another provider?
• What would you tell someone who asks about us?

The first two form the Net Promoter Score. Our guide to the nps question covers the scale, formula, follow-ups and analysis in detail, and our nps software page shows how to run it.

Ask these at the moment of cancellation or right after. Keep it to a few questions and never make them a condition for cancelling.

• What is the main reason you are cancelling?
• When did you start thinking about leaving?
• What are you switching to, if anything?
• Was there something we could have done to keep you?
• Would you consider coming back if we fixed it?

Open version: "In a minute or so, tell us what led you to cancel. We read every answer."

A typed answer tends to be short and polite. A spoken answer tends to include the situation, the steps and the feeling. To get spoken answers that help, write prompts that sound like a person asking.

• Ask about a recent, specific experience.
• Ask one thing per prompt.
• Suggest a length, such as "a minute or so".
• Keep text available for people who prefer to type.
• Ask for consent before you share any answer outside the team.

With voice feedback and video surveys, each open question accepts text, a voice note recorded in the browser or a video from a phone or laptop, with no app to install.

In business products, the person who buys is often not the person who uses the product every day. Ask both. The buyer cares about outcomes and cost. The daily user cares about speed, clarity and whether the product fits the way the team works.

• What business goal did you buy this product to support?
• How do you measure whether it is working for your team?
• Which teams or roles use the product most?
• Who else in your company should we be hearing from?
• What would need to be true for you to expand use to more teams?
• What would put the renewal at risk?

For daily users, keep the questions practical.

• Which task do you do most often in the product?
• Where do you lose the most time?
• What do you still do outside the product that you wish you could do inside it?
• What would you show a new colleague first?

Open version: "Tell us how your team uses the product in a normal week, and where it fits or does not fit your process."

The channel matters as much as the questions. Send each survey where the customer already is at that moment.

• After a purchase or delivery, send an email invite with the first question visible in the message.
• After a support chat, show the survey in the same window or send it right after the chat closes.
• Inside your product or site, use a side tab or popup on the page where the moment happened.
• At events or in stores, print a QR code on the receipt, table card or badge.

Write a subject line that says what you want and how long it takes, such as "Two quick questions about your order". Name a real team, such as "the support team", and say what you do with the answers. Send one reminder at most, a few days later, and stop there.

• Asking too late. A survey about a support chat sent a week later gets vague answers.
• Asking too often. The same customer should not get several surveys in one week.
• Leading wording. "How much did you enjoy our fast delivery?" assumes the answer.
• Double questions. "Was the product good value and easy to use?" asks two things.
• Rating only. Scores without reasons give you a dashboard but no next step.
• Never replying. Customers who explain a problem and hear nothing stop answering.
• Hiding the length. Tell people up front how long the survey takes.

Start with the ratings for each survey and look at trends by segment: plan, channel, region, product line. Find where scores drop and which moments in the journey they relate to.

Then read the open answers behind the lowest scores. Tag each with themes such as delivery, price, quality, support, setup or missing features. Count themes per segment and note sentiment per answer. Themes that repeat across several moments point to a root cause rather than a one-off issue.

Pull quotes for each theme and share them with the teams who own that part of the journey. Then decide on a few changes, assign owners and measure the same survey again after the change.

Once answers pass a few dozen, survey analysis software saves hours: it transcribes voice and video answers, groups them into themes, marks sentiment per answer and pulls quotes with timestamps.