Pick three sources and no more
Start with the places feedback already arrives. Three is enough:
- A check-in call or message at day 30 and day 90 after the sale.
- A one-question survey after a key moment, such as finishing set-up or closing a support ticket.
- Your support inbox or ticket tool, read for patterns rather than single complaints.
Add more later. A loop with three sources you actually read beats a dashboard of eight you ignore.
Ask one question at a time
Long surveys get abandoned and tell you little. Ask one open question and one number. Good open questions are "What nearly stopped you from getting value from this?" and "What would you miss most if we disappeared tomorrow?".
For the number, a score from 1 to 10 on "How easy was this?" works after a specific event. Build the survey in Typeform or Tally and keep it under a minute. If you want to use scores to drive action, read Increase NPS through targeted actions.
Put everything in one place
Feedback scattered across email, chat and your memory cannot be counted. Pick one home and log every item there. A custom object or notes in HubSpot, a table in Airtable or a page in Notion all work.
Each entry needs five fields: the customer, the date, the source, what they said in their own words, and a theme tag. Do not rewrite their words. The raw sentence is the useful part.
Tag by theme, and keep the list short
Create no more than eight themes, such as set-up, pricing, missing feature, bug, support speed and reporting. Add a ninth called "other" and review it once a month for new themes.
Tags turn opinions into counts. One customer asking for a report is an anecdote. Seven asking for it in six weeks is a decision to make.
Review once a week for 30 minutes
Put a recurring slot in your calendar. Read the new entries, count the tags and pick the top theme. Then give each theme a decision:
- Fix it: someone owns it and has a date.
- Answer it: it is a misunderstanding, so change the documentation or onboarding.
- Park it: write down why, and the number of requests that would change your mind.
Log the decision, not just the discussion. When someone asks why a feature is missing, you can point to the entry.
Close the loop within 14 days
This is the step most teams skip. Every customer who gave feedback gets a reply, even if the answer is no. Use a short template:
"You told us [what they said]. Here is what we did: [fix, answer or reason]. If this still does not work for you, reply and tell me."
Send it by hand when the feedback came from an important account. For the rest, a flow in Zapier can draft the message when you mark an entry as done, and you read it before it goes out.
Connect feedback to health
Feedback is one input to your view of an account, not the whole picture. Customers who are unhappy often say nothing, which is why Listen to behaviour before you listen to surveys matters as much as this chapter. Put a negative feedback entry on the account record, and let it feed the score described in How to monitor customer health.
Common mistakes
- Collecting feedback and never replying, which teaches customers to stop talking.
- Asking only happy customers, because they are easier to reach.
- Treating the loudest customer as the biggest theme.
- Keeping feedback in one person's inbox.
- Running a survey every month with the same questions and no change in between.
- Promising a fix without an owner or a date.
How you know it works
- Every customer who gives feedback hears back within 14 days.
- You can name the top three themes from the last quarter with counts.
- At least one visible change each month traces back to a logged entry.
- Fewer customers say the same thing twice.
- You hear about problems from the loop before you hear about them in a cancellation.
