{"id":1679,"date":"2022-01-18T16:11:56","date_gmt":"2022-01-18T13:11:56","guid":{"rendered":"https:\/\/www.useresponse.com\/blog\/?p=1679"},"modified":"2022-01-18T16:11:57","modified_gmt":"2022-01-18T13:11:57","slug":"how-to-organize-feedback-community-and-introduce-it-to-your-customers","status":"publish","type":"post","link":"https:\/\/useresponse.com\/blog\/how-to-organize-feedback-community-and-introduce-it-to-your-customers\/","title":{"rendered":"How to Organize Feedback Community and Introduce it To Your Customers"},"content":{"rendered":"\n

Using UseResponse<\/a> Feedback tool your feedback won\u2019t be scattered around emails, messengers, live chat conversations, Slack, spreadsheets, and other places, but it will all be organized in a single place. With specialized community feedback software, your feedback boards will be the core source of truth where your product development team will be able to find customer-based insights that will help them build your next best features. It will be the place where your customers can go if they want to share their ideas knowing that their voice will be heard.<\/p>\n\n\n\n

Introducing a Feedback Community can be a rare opportunity to change the habits of your customers, support, and development teams to reform the way of how the feedback is being collected and processed. In this post, you will find some tips on how you can get the feedback system running, introduce it, and help your customers and team understand the benefits of using specialized feedback software.<\/p>\n\n\n\n

Things To Do Before Introducing Your New Feedback Portal to Customers and Team<\/strong><\/h2>\n\n\n\n

Before you introduce the feedback portal or feedback widget to the audience, some preparation work needs to be done.<\/p>\n\n\n\n

Feedback Portal Setup<\/strong><\/h3>\n\n\n\n

While you can collect feedback privately and it will only be visible to you and your team, the most common practice is to organize a Community Feedback Portal. It can be Public <\/strong>(visible to everyone) or Closed <\/strong>(require authentication to see the feedback). You also can make use of single-sign-on (SSO) in this case.<\/p>\n\n\n\n

When creating a Feedback Portal<\/a>, make sure to use a clear name for your feedback board. Speak the customer language and try to be as specific as possible. While \u201cfeedback\u201d has quite a general meaning, you can specify the title of your board to sound like \u201cFeature Requests\u201d or \u201cIdeas Bank\u201d. If you plan to have several boards for different products or areas of your product, state it in the title, eg. \u201cFeature Requests for Admin Area\u201d.<\/p>\n\n\n\n

\"Customer<\/figure>\n\n\n\n

Add a short description to the board to guide your customers and explain what they can do. You can add a short copy like:<\/p>\n\n\n\n

\u201cHere you can share your ideas and feature requests on improving our product, post your questions or issues. You can browse the ideas of other users and vote for them and communicate with our development team.\u201d<\/em><\/p><\/blockquote>\n\n\n\n

You can also create a page with a more detailed description of how you expect customers to use your feedback portal, post rules of conduct, and whatever you find important to tell (like ask them to specify the version of the product they are currently using or post one request per topic, etc.).<\/p>\n\n\n\n

You can modify the design and layout of your Feedback portal completely using the admin area:<\/p>\n\n\n\n

\"Modify<\/figure>\n\n\n\n

<\/p>\n\n\n\n

Categorize<\/strong><\/h3>\n\n\n\n

Depending on the specifics of your company and product you may want to organize the feature requests by different boards or create several categories inside one feedback portal.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Define Statuses<\/strong><\/h3>\n\n\n\n

Statuses are intended to communicate the development process. They are used to let the customers know the status of their request and add it to a separate column in the roadmap. You can use default system statuses or can change them according to your development flows. <\/p>\n\n\n\n

\"Feature<\/figure><\/div>\n\n\n\n

Feedback Form<\/strong><\/h3>\n\n\n\n

Unlike other feedback tools, UseResponse provides you with great flexibility options. You can customize the feedback form to include custom fields, including conditional fields to collect the information you need. <\/p>\n\n\n\n

All these settings will go a long way in adjusting the system according to the needs of your development team and keeping your board organized.<\/p>\n\n\n\n

\"Creating<\/figure>\n\n\n\n

Add Some Content<\/strong><\/h3>\n\n\n\n

We highly recommend adding some topics to get things rolling in your community. Look up your backlog, ask the development team what features are currently in development. With UseResponse you can add topics on behalf of customers, so filling the system with some ideas to start with should be easy.<\/p>\n\n\n\n

By adding some ideas you will give your customers the tone of conversations, show examples of what a good feature request should look like, and encourage them to leave their feedback.<\/p>\n\n\n\n

Introducing New Feedback System<\/strong><\/h2>\n\n\n\n

It is no brainer that a feedback community portal should be easy for customers to find and use whenever they want. Whenever they have an idea or stumble upon something, they should have a quick and easy way to share their voice.  <\/p>\n\n\n\n

Changing the habits and asking your customers for some extra effort may meet resistance at the beginning, so when introducing UseResponse try to explain the benefits of using an organized feedback system.<\/p>\n\n\n\n

For example, you can list the following:<\/p>\n\n\n\n