Skip to the content
searchboar.

Customers and buying decisions

Customer feedback: information customers give about their experience

Customer feedback is information customers provide about their needs, experience or satisfaction, including comments, suggestions, complaints and answers to questions.

Also known as: customer comments · voice-of-customer feedback

At a glance

  • Feedback can be public or private, positive or negative.
  • A comment identifies a perspective; it does not automatically establish prevalence.
  • Collecting feedback only helps when someone evaluates and acts on it.
On this page
A business organizes customer comments into questions and possible improvements.
Feedback becomes useful when comments are interpreted and connected to decisions.

Where does feedback come from?

Customers may offer feedback in a support conversation, a survey, an interview, a return request or a public review. It can be prompted by a question or volunteered without one. The source affects what you learn: people contacting support may have different experiences from those who never needed help.

Zendesk’s overview describes feedback across these forms. A customer review is one public expression of experience; feedback also includes private information that should not be treated as ready-made promotional copy.

Separate the observation from the proposed solution

A customer might say, “Add a telephone booking option.” The underlying problem could be an inaccessible form, uncertainty about availability or a need to ask an unusual question. Investigate that problem before assuming the requested feature is the only solution.

Imagine a small repair business hearing that customers cannot tell whether an estimate includes collection. Several comments point to a missing explanation. The business can clarify the estimate and its service description, then check whether the confusion continues.

How should comments be interpreted?

Group comments by issue while keeping the original context available. Record where the feedback came from and what question, if any, prompted it. Distinguish a reported event from a preference or a suggestion. One serious complaint deserves attention even if it is uncommon.

Do not turn a handful of interviews into a claim about all customers. Purdue’s guidance on primary-data analysis stresses avoiding conclusions that extend beyond the evidence. Counts need a defined base: ten comments mean something different among twelve interviews and thousands of transactions.

Closing the loop

Assign a decision to the issue: investigate further, change an explanation, improve the service or explain why a suggestion will not be adopted. Where appropriate, tell the customer what happened. Asking repeatedly without considering the answers can waste everyone’s time.

The voice of customer can inform article language and topic selection, but do not publish private details or imply every comment represents the entire audience. Good feedback work preserves the customer’s meaning while making a reasoned business decision.

Sources

  1. Zendesk: Customer feedback
  2. Purdue OWL: Analyzing your primary data