Most teams start by emailing a long survey to every customer once a year. A few people answer, the answers are general ("good service", "a bit expensive"), and nobody can tell which part of the product or which page they are about.
Each method on this page reaches different customers at a different moment. Pick two or three that cover the moments you care about, keep every question short, and decide in advance what you will do with the answers.
The short answer
Use a few methods together, each at the moment it fits. Ask one or two short questions where the experience happens: on the page, in the app, or right after a purchase or a support chat. Run a relationship survey such as NPS a few times a year for the bigger picture, and read what customers already tell you in support tickets and reviews. Then fix what comes up most and tell customers what changed.
The 8 ways to collect customer feedback
Some methods ask customers a question. Others listen to what they already say or watch what they do. You need both: the questions tell you why, the rest tells you where to look.
| Method | Best moment | What you learn | Effort for the customer |
|---|---|---|---|
| On-site surveys and feedback widgets | While they are on the page | What they think of that page, in their words | One tap, plus an optional comment |
| In-app surveys | Right after they use a feature or finish a task | How easy or useful that feature was | One tap |
| Email and SMS surveys | After a purchase, a delivery or a closed ticket, or on a calendar | Satisfaction with one interaction, or loyalty overall (NPS) | Open the message, follow a link, answer a form |
| Customer interviews and usability tests | Before a big decision, or with customers who just left | The reasons behind behaviour, in depth | 15 to 60 minutes |
| Support tickets and chat logs | Every day, without asking | Recurring problems and confusing steps | None: they already wrote to you |
| Reviews and social media | Whenever customers post | What they tell other people about you | None for you to add |
| Feedback boards and feature requests | Whenever customers have an idea | What they want you to build next | Sign in and post or vote |
| Analytics and behaviour data | All the time, without asking | Where customers drop off, not why | None |
Short surveys on the page or in the app usually get more answers than an email survey, because they ask while the experience is fresh and answering takes a second. Interviews get the deepest answers from the fewest people. Support tickets, reviews and analytics cost the customer nothing, so use them to decide what to ask about.
Choose the right survey question: NPS, CSAT or CES
Three standard questions cover most customer surveys. Each one measures something different, so pick the one that matches what you want to learn:
| Metric | The question | Scale | Use it for |
|---|---|---|---|
| NPS (Net Promoter Score) | How likely are you to recommend us to a friend or colleague? | 0 to 10 | Loyalty to the company as a whole, a few times a year |
| CSAT (customer satisfaction) | How satisfied were you with your order? | 1 to 5 | One interaction: a purchase, a delivery, a support chat |
| CES (customer effort score) | How easy was it to set up your account? | 1 to 7 | One task: setup, checkout, cancelling, finding an answer |
Follow each one with an optional "What is the main reason for your score?" The number tells you how many customers feel that way. The comment tells you what to fix.
Tip: Ask one of the three per moment. Three rating scales in a row read like a form, and people stop answering.
Ask at the moment the experience happens
Customers remember an experience best while they are still in it. A question about checkout works on the order confirmation page. A week later in an inbox, the answer is vaguer, and fewer people give it.
- After a purchase, ask a CSAT question on the order confirmation page, or email one within a day of delivery
- When a support ticket closes, ask how satisfied the customer was with the help
- At the end of onboarding or the first use of a feature, ask a CES question on that screen
- At the end of each help article, ask "Did this page answer your question?"
- On pricing and sign-up pages, ask "Is anything stopping you from signing up today?"
- For the relationship as a whole, run NPS by email or on the site on a fixed schedule, such as once a quarter
The first five are transactional: they ask about one moment, and each answer is tied to it. The last one is a relationship survey. Run it on a schedule, so you can compare one quarter with the next.
Keep every question short and easy to answer
Each extra question loses some of the people who would have answered the first one. Start with a question that takes one tap, ask one thing at a time, and use the words your customers use.
| Instead of | Ask |
|---|---|
| How satisfied were you with the speed, friendliness and quality of our support? | How satisfied were you with this support chat? |
| How much did you love our new dashboard? | How useful is the new dashboard? |
| Do you have any feedback? | What almost stopped you from ordering today? |
| Please rate your overall experience with our onboarding process. | How easy was it to set up your account? |
Incentives such as a discount code bring in more answers, but they also bring in people who answer only for the reward. If you offer one, give it to everyone who answers. Never make it depend on a positive answer. That skews every result, and most review sites ban it for public reviews.
Tip: Three questions at most on a page or in an app, with the free-text question last and optional.
Collect feedback without collecting personal data
Most feedback doesn't need to know who gave it. To learn whether checkout is easy or a help article is clear, you need many honest answers, not names. People also say more when they know nobody can trace the answer back to them.
Only ask for an email address when you plan to reply. Otherwise, leave the contact fields out and say next to the question that answers are anonymous. Under GDPR, a tool that sets cookies or stores identifiers in the browser needs consent first, so a cookie-free survey also spares your visitors a banner.
Close the loop: act on feedback and tell customers
Feedback only helps once someone acts on it. Give it a routine:
-
Put it in one place
Survey answers, support tags and review notes in one list or board, not five inboxes.
-
Group it by theme
Billing, delivery, setup, a specific page. Count how often each theme comes up.
-
Pick the theme that costs you the most
The one with the most complaints, or the one that stops people from buying. Fix that first.
-
Check that the fix worked
Compare the answers before and after the change, on the same page and question.
-
Tell customers what changed
A line in your changelog or newsletter, or a reply to the customers who raised it. Customers who see the last round led to something tend to answer the next one.
Example
Example: a small online shop finds out why buyers hesitate
Say you run an online shop that sells coffee beans by subscription. You have an NPS email that goes out twice a year, and the comments say things like "great coffee" and "shipping could be better". You can't tell which part of shipping.
You add three short questions on the site. On the order confirmation page: "How easy was it to place your order?" (1 to 7) and an optional "What almost stopped you?". On every help article: "Did this page answer your question?". On the subscription page: "Is anything stopping you from subscribing today?"
After a month, the confirmation page comments keep naming one thing: buyers can't see the delivery date before they pay. The help article on pausing a subscription gets more "No" answers than any other, and its comments ask how to skip a single delivery. The subscription page comments ask the same question.
You show the delivery date at checkout and add a "skip one delivery" section to the help article and the subscription page. A month later, you compare the answers on the same pages. The twice-yearly NPS email stays, now for the questions about the shop as a whole.
Creative ways to collect customer feedback
Once the basics are in place, a few less common methods fill the gaps:
- Ask on your 404 and empty search results pages: "What were you looking for?" turns a dead end into a list of missing content
- Put a one-question survey on the cancellation or downgrade page, and keep it optional
- Add a feedback tab to your help centre so customers can flag a wrong answer without opening a ticket
- Ask your support and sales teams for the three questions they heard most this month
- Invite customers who left in the last quarter to a 15-minute call, and ask what they use now
- Read your competitors' reviews: their customers' complaints show what yours expect you to get right
Where Asklet fits
Asklet covers the first two methods: short surveys on your website and inside your web app. You paste one snippet, and path patterns such as /help/** or /checkout/thank-you give each part of the site its own questions. Questions can be Yes / No, a 1 to 5 rating, a custom range such as 1 to 7 for CES, an NPS scale, a choice list or free text, and the results come back for each page.
Customers answer without an account or an email address, and the widget sets no cookies, so it needs no consent banner. Emails and phone numbers typed into comments are removed before they are saved. It does not send email surveys, record sessions or collect public reviews, so keep your email tool and help desk for those.
You can start on the Free plan: one website, 10 live pages and 100 responses a month, with no card needed.
Your next steps
-
List the moments that matter
Checkout, setup, a support chat, a help article. Pick the two where you know least about how customers feel.
-
Write one question for each
CSAT after an interaction, CES after a task, then an optional "What is the main reason for your score?"
-
Ask on the page where it happens
Put the question on the confirmation page, the help article or the app screen, not in an email a week later.
-
Read your support tickets and reviews
Tag a month of them by theme to see which problems come up without anyone asking.
-
Review the answers once a month and tell customers
Fix the most common theme first, compare before and after, and share what changed.
Try these steps on your own site. Asklet adds the questions to every page with one snippet. Free plan, no card needed. Compare the plans.
Start freeCommon questions
What are 5 methods of obtaining feedback from customers?
Surveys (by email, on your site or in your app), customer interviews, support tickets and chat logs, reviews and social media, and feedback widgets on your website. Most teams combine a short survey at key moments with a regular look at support tickets and reviews.
What is the best channel to collect customer feedback?
The one that reaches customers at the moment you want to learn about. For a page, a feature or a checkout, ask on the page or in the app. For the relationship as a whole, or for customers who no longer visit, use email.
How often should you ask customers for feedback?
Ask transactional questions every time the moment happens, such as after each order or support chat, but show each customer the same survey only once. Run relationship surveys such as NPS on a fixed schedule, often quarterly or twice a year.
Should you offer an incentive for customer feedback?
Only if answers are too few to act on. An incentive raises the number of answers but can lower their quality. Give it to everyone who answers, never only to people who answer positively.
Can you collect customer feedback without cookies?
Yes. A survey only needs the answer, not the person. Asklet, for example, sets no cookies, stores no IP addresses and needs no sign-in, so the widget needs no consent banner.
Related
More from the blog
- Privacy and law EU cookie consent changes: where the Digital Omnibus stands in October 2026 9 min read
- Privacy and law Session replay and pixel lawsuits: what website owners should know 9 min read
- Privacy and law How to make a feedback widget accessible, and what the European Accessibility Act asks 9 min read