Review Feedback Consistently
Depending on the volume of your feedback, set aside time in your day or week to review, comment, label and update suggestions to make your users feel heard. A survey by MarketingLand found that more than half of customers will defect unless their feedback is recognized. Looking at feedback daily keeps you on track and gives users recognition in a timely manner.
Make a plan of who is responsible for reviewing feedback and decide your timeline for reviewing. Hold yourself accountable and know that the better you are at staying on top of it, the easier it is to manage!
Create a saved view for suggestions with no status or no comments to be reminded daily via email to log in to review new suggestions!
Not all feedback is directly captured on your forum. Often your sales and support teams will receive feedback from users over the phone or email. Don’t rely on the users to go to the site to leave this feedback. Capture it for them, but using the Capture Feedback feature in UserVoice.You can enter information that is internal only and also choose to subscribe (or not!) your end user to the feedback for them to get updates.
Updating the statuses of ideas is a key part of keeping users engaged and closing the loop. Users feel heard when there is a response to their feedback. They feel included in your product life cycle and are therefore more likely to continue to provide feedback.
We suggest always updating the status of an idea as you move forward to keep users in the loop and to help boost initial utilization and awareness as new features are released. We also recommend setting a threshold for any ideas with X number of supporters getting some type of status to let users know you are aware of those top pieces of feedback.
Also make sure to let your users know when you are not planning to implement their feedback. Make sure that users are not kept in limbo by declining or rejecting ideas.
Two effective responses are:
- This item is not on the roadmap at this time, but we will let you know if this changes
- We understand the use case, but it is not a product priority at the time. Please take a look at our roadmap, located <here>!