What should you do with NPS feedback?
Use NPS feedback to understand the experience behind recommendation ratings, identify issues that need attention and track what your team does next. Read the comment with its rating and relevant context, decide who should review it, and record the response or improvement action.
Not every comment needs a personal call or a process change. Some confirm a useful practice; some raise a question; others describe an unresolved problem. A clear review process helps distinguish them without promising every suggestion will be implemented.
This guide focuses on follow-through. For score calculations and group comparisons, use NPS analysis. For setting up the survey, see how to measure NPS.
Start with a review decision
Read what the person actually said. A low rating can justify a closer look, but it does not identify the remedy. “The instructions were confusing” and “I am waiting for a refund” need different owners and next steps even if both came with the same rating.
Scroll horizontally to see all columns →
| Feedback type | Example | Possible next step |
|---|---|---|
| Specific unresolved issue | I still do not know whether my request was received. | Check the request and provide a clear status where contact is appropriate. |
| Recurring process concern | The upload instructions were hard to follow. | Review several examples and test the instructions. |
| Suggestion | I would like an evening appointment option. | Consider demand and feasibility; explain the decision when appropriate. |
| Positive experience | The adviser explained the next step clearly. | Recognize the useful practice without exposing private details. |
| Unclear account | It was not what I expected. | Clarify when possible; avoid inventing what went wrong. |
A single response can lead to both an individual resolution and a broader improvement. One billing error may reveal a process issue; many reports may still require different individual remedies. Do not classify solely by how many times a theme appears.
Prioritize by need, evidence and responsibility
Consider severity, whether the matter remains unresolved, how many people may be affected and which team can act. A rare serious concern may deserve attention before a frequent minor inconvenience. Follow established procedures for matters requiring specialist handling.
Do not let automated sentiment decide urgency on its own. A calmly written message can describe a significant problem. AI can help organize and flag responses, but the review process needs clear human responsibility and an appropriate route for issues outside routine feedback.
Theme counts are useful for understanding the observed response set. They are not automatically a measure of how common the problem is among all customers. Keep comment coverage and source examples available when prioritizing.
Give each action an owner and a status
An alert is not an action. A forwarded email is not proof that someone accepted responsibility. Use a small set of clear statuses that people can maintain, with a named owner and the next review date.
Scroll horizontally to see all columns →
| Status | Meaning | Evidence to retain |
|---|---|---|
| Needs review | The comment has arrived and has not yet been assessed. | Original response, date and relevant survey context |
| Assigned | An owner has accepted responsibility for the next step. | Owner, action and target review date |
| In progress | The action is underway or information is being checked. | Progress note and any dependency |
| Awaiting reply | The team has asked for information or confirmation. | Contact attempt and next review date |
| Resolved or decision communicated | The agreed action is complete or the decision has been explained. | What happened and how it was communicated |
Separate “no further action appropriate” from “resolved” if those mean different things in your workflow. A suggestion declined after review is not the same as a service problem fixed. Keep the reason so a later reviewer understands the decision.
Respond without turning the conversation into a score request
Where personal contact is appropriate, acknowledge the specific issue, explain what you can check and give a realistic next step. Avoid a generic message that implies the problem is fixed before anyone has investigated it.
Example acknowledgment: “Thank you for explaining the difficulty with your registration. I’m checking whether the document arrived and will update you by Thursday. You do not need to submit it again while we check.”
This is a fictional example; adapt the promise to what the team can deliver. Do not request a higher rating, make support conditional on changing feedback or overwrite the original response after a resolution.
For anonymous feedback, share an appropriate summary of themes and actions. The team can explain that it clarified instructions or changed a process without identifying respondents. If a survey is anonymous, do not imply the team can contact everyone personally.
Turn repeated concerns into a process review
When comments suggest a pattern, examine the underlying work. Who encountered the issue? At what stage? Do service records support the account? Are different problems being placed under one broad theme?
For example, “communication” could mean no confirmation, inconsistent advice or a delayed decision. Those concerns require different tests. Define the issue narrowly enough to assign useful work while preserving the context of the original comments.
Write an improvement record containing the observed concern, evidence, proposed change, owner and measures to review. Keep individual requests linked where appropriate, but do not circulate unnecessary personal details in a shared improvement board.
For larger teams or multiple locations, agree on shared theme definitions and statuses while allowing local detail. The same word can have different meanings across teams. Review examples together before aggregating counts.
A worked follow-through report
Suppose a fictional survey produces 80 comments. Reviewers identify 20 responses requiring an individual action. By the review date, 12 have completed actions, five remain in progress and three await a customer reply.
- Completed actions: 12 of 20, or 60%.
- Still open: eight, with owners and next review dates.
- These are action-status counts, not an NPS score or a measure of customer satisfaction.
Of the 12 completed actions, nine customers reply to a follow-up and seven say their issue is resolved. Report seven of nine respondents confirmed resolution, with three completed-action customers not responding. Do not describe all 12 as customer-confirmed resolutions.
Also inspect how long cases remain open, recurring dependencies and whether the same problem appears again. A fast closure rate can be misleading if staff close records administratively without addressing the issue.
How do you check whether follow-through helped?
Use a measure close to the action: confirmation delivered, request resolved, fewer failed uploads or a clearer next step. Ask about the experience when useful and appropriate. A later recommendation score provides additional context, but it is not the only definition of success.
Matching the same customers across waves can show their observed rating changes. It does not prove the action caused the change. Other experiences, survey timing and selective follow-up response may contribute. Preserve those limits in the report.
A customer may consider an issue resolved while still giving a low recommendation rating because other concerns remain. Treat that as useful feedback rather than a failed attempt to obtain a better score.
What data should stay connected?
Keep the response, question version, rating, relevant service context, reviewed theme and action record connected at the appropriate level. Where personal follow-up is needed, use authorized contact information. Where group-level learning is sufficient, avoid adding identity simply for convenience.
Give each audience the view it needs. The service owner may need an individual request; leadership may need themes, unresolved counts and decisions. Review quotations before sharing them outside the authorized team.
Do not silently change theme definitions between reports. A renamed or split category can alter the apparent trend. Maintain the original classifications or document how earlier responses were recoded.
Evaluate the complete feedback workflow
Sopact’s relevant approach connects collection, analysis and governance so the operational team can manage recurring feedback with its context. Test the workflow rather than relying on a dashboard demonstration: inspect a source comment, review a proposed theme, assign a next step and verify the reporting permissions.
Check which action-tracking features are native and which require integration with your existing service system. A feedback platform does not automatically replace every support process. Confirm how updates return to the shared view and who maintains that connection.
Compare total work across collection, interpretation, routing and reporting. Many survey tools can collect ratings and text; the practical question is how the team keeps the process reliable as sources, periods and responsibilities grow. See feedback-tool requirements for a pilot checklist.
Watch the feedback companion
See Sopact’s discussion of reviewing feedback with its context.
Frequently asked questions
Should every NPS comment receive a personal response?
No. Use personal follow-up where it is appropriate, possible and useful. Shared learning and a summary of actions may be the right response for anonymous feedback or broader suggestions.
Does a resolved action require a higher NPS rating?
No. Resolution should reflect the issue and agreed action. A customer can consider that issue resolved while retaining other concerns about the overall relationship.
Can one comment indicate a wider process problem?
Yes. A single report can justify investigation. Check the evidence and potential reach rather than waiting for an arbitrary number of similar comments.
Can AI decide which comments are urgent?
AI can assist with organizing and flagging feedback, but it should not be the only route for important concerns. Use clear review responsibility and the organization’s established response procedures.
Does responding guarantee better participation next time?
No. Showing that feedback was considered can support a useful relationship, but future participation depends on many factors. Measure it rather than promising a particular uplift.
