How to collect customer feedback: five channels compared

To collect customer feedback, use more than one channel and give each a single job. Send a short survey straight after a purchase or visit to learn what just happened. Run a Net Promoter survey on a fixed schedule to track the relationship. Interview a few customers when you need to know why. Invite every customer to leave a public review, with no reward attached. And treat support tickets and complaints as feedback that customers have already sent. Then read all five in one place, because the same problem showing up in two channels is the one to fix first.

The mistake most businesses make is not choosing the wrong channel. It is using one channel for every question. A satisfaction survey cannot tell you why customers leave. A review site cannot tell you what a quiet majority thinks. The table at the end of this article compares the five channels by when to use each and the kind of response to expect.

The survey used as the example is the six question customer feedback survey: a conversational form that opens by promising six quick questions in about ninety seconds and keeps a counter on every screen.

Post purchase survey: ask about the last thing that happened

This is the channel to start with. It goes out right after a visit, an order, a delivery or an appointment, so the customer remembers the details and you know exactly what they are rating.

Keep it about that one event. The example opens with “How satisfied were you with your visit today?” on a five point scale from very satisfied to very dissatisfied. It follows with the recommend question, then a required “What is the main reason for your score?”, then two optional questions: a checklist of what went well (the staff, the speed, the quality, the value, the atmosphere, or nothing in particular) and “What is the one thing we could do better?” The last question asks for an email only if the customer wants a reply.

Three design choices do most of the work. The time is stated up front, so nobody starts a survey they will abandon. The score is always followed by a reason, so the number arrives with something to act on. And only three of the six questions are required, so a customer in a hurry still submits a complete response.

Qualtrics lists the delivery channels for this kind of survey: email, which customers are used to and trust when it comes from a familiar address about a purchase they remember, and SMS, which reaches people who do not use much else but suits only a small amount of feedback at a time. For a shop or a cafe, a QR code on the receipt or the table does the same job.

NPS: ask about the relationship on a schedule

The Net Promoter question, “How likely are you to recommend us to a friend or colleague?”, measures the relationship rather than the last visit. Bain’s explanation of the score is simple: answers on a zero to ten scale, the percentage of promoters who score 9 or 10, minus the percentage of detractors who score 0 to 6. Bain also suggests tracking it for each business, product, store or team, and for customer segments.

Its value comes from repetition, so it belongs on a fixed schedule rather than after every transaction. The example survey carries the question because a single visit survey is a convenient place to collect it, but the score is best read across a quarter, not visit by visit. The dedicated NPS survey example strips it back to four questions: the score, the reason, permission to reply and an email for those who say yes. Timing, wording and segment reporting are covered in depth in NPS survey best practices, and the difference between a relationship score and a satisfaction score is on the NPS versus CSAT page.

Interviews: ask why, with five customers

Surveys tell you what. Interviews tell you why. Nielsen Norman Group describes a user interview as a method where the interviewer asks questions, listens, and follows up to learn more about people’s experiences, needs and values. It also notes that interviews are attitudinal: you hear what people report about their behaviour and feelings, not what you would see if you watched them.

Use interviews when something moves and nobody knows why: a drop in satisfaction, a run of cancellations, a price change that did not land. Pick customers from both ends of the survey results. Ask about the last time they bought, what almost stopped them and what they compared you with, and let the follow up questions do the rest.

Keep the notes in the same place as the survey responses. An interview theme that matches a cluster of survey comments is evidence. One that matches nothing may be one person’s view.

Reviews: invite everyone, reward no one

Public reviews are feedback that future customers read, which makes them marketing as much as research. They also skew towards strong opinions, so they are a poor measure of what an average customer thinks.

The rules here are strict. Google’s Maps content policy does not allow businesses to offer incentives such as payment, discounts or free goods in exchange for posting any review, or for revising or removing a negative one. The FTC’s endorsement guidance says a business cannot condition a discount on a review being positive, while inviting all customers to post honest reviews is fine.

So ask every customer, not just the happy ones, and never attach a reward. The simplest invitation is a link on the thank-you screen of your private survey, shown to everyone, with no hint about what to write.

Support tickets: the feedback you already have

Complaints, support emails, returns and cancellation reasons are feedback that customers took the trouble to send without being asked. They are also the channel most likely to come from customers who are about to leave.

The job is recording, not collecting. Give every complaint the same few fields: date, channel, what the problem was in one line, and whether it was resolved. A shared inbox tag, a spreadsheet or a short internal form works. Once a month, compare the top complaints with the “one thing we could do better” answers from the survey. Where they match, you have your next fix. For a software product, a complaint is often a bug, and the bug report question bank lists the steps, expected result and environment questions that let a developer reproduce it.

If the business runs training, events or classes, the same principle applies to the evaluation at the end: the course evaluation form example splits teaching, materials and outcomes into separate rating grids so one weak area does not drag down the others, and the event feedback form goes out the morning after while the details are still fresh.

Common mistakes

Asking everything in one survey. A twenty question survey after a coffee gets abandoned by exactly the people with the most useful complaints.

A score without a reason. Always follow a rating with a why, even if the why is optional.

Rewarding reviews. It breaks platform policy and makes the reviews worthless as a signal.

Only asking happy customers. Choosing who gets asked is the fastest way to a flattering and useless result.

Collecting and never replying. If the survey offers a reply, keep the promise. The example’s thank-you screen says follow ups come within two working days, and that is the standard it will be judged against.

Keeping each channel in its own silo. The overlap between channels is where the signal is.

Build it

The rating matrix page shows the field that asks several statements on one scale, which suits a survey that rates staff, speed and value separately; a matrix can take one answer per row or several per row. The example survey is a conversational form, one question per screen with a counter, and the same survey can be built as a classic form on one page if it will be filled in on a counter tablet.

Responses export as a CSV with one column per question, the submission time in the first column and choice answers as their labels, so a quarter of satisfaction ratings can be counted in a spreadsheet without cleaning. A matrix answer is exported in a single column as statement and answer pairs. To see responses as they arrive, the email alerts add-on sends each submission to one address, which suits whoever handles replies. The steps for viewing and exporting responses are in the guide to managing your responses.