Collecting feature requests from your users is super important when it comes to building software. By continually adding value to your product through understanding the needs of customers, is a great way to ensure customers stay happy and remain customers longer.

Userback provides a fantastic, easy to use multi-purpose widget that will help you collect feature requests from your users and even your internal team. Feature requests will be automatically captured to your Userback account with handy filters that let you manage and prioritize them much faster.

There are 4 main features in Userback to help you with collecting feature requests.

  1. Userback Widget

  2. Filtering feedback with Board View

  3. Sending feature requests to the right place with integrations

  4. Using the JS API to pre-populate user information and add custom data

Userback feature request widget

To setup your feature request widget, you'll need to have a project created to collect your feature requests and simply configure your widget as required.

There are a number of different options available when building your feature request widget and a few decisions you will need to make which include:

  1. Am I collecting feature requests and other types of feedback such as bugs?

  2. What is the best workflow for my users?

  3. What information do I need to collect with each feature request?

The Userback widget settings will allow you to configure your widget that matches the types of ideas and features requests you are collecting, the best workflow for your users and information that you need to collect.

To start with, the Widget lets you collect 3 separate types of feedback (Bug Reports, Feature Requests and General Feedback). Each option can be enabled or disabled independently.

Start by enabling the feedback options applicable to your use case. In this example, only the Feature Request feedback type is enabled.

Considering the workflow for your users, you can set your feature request widget to behave differently. Userback defines each workflow as a destination. There are 3 destinations available including:

  1. When a user clicks the widget button, only show the feedback form, allowing the user to decide if they add a screenshot or video recording.

  2. When a user clicks the widget button, automatically load the screenshot tool, followed by the feedback form.

  3. When a user clicks the widget button, automatically load the video tool, followed by the feedback form.

To change this behavior for 1, 2, or 3, select the destination from the destination drop down based on how you would like the widget button to behave.

If you have more than one feedback type enabled, the destination setting will work in the same way however, the user will need to select the type of feedback they are submitting from the routing screen.

In the example below, Bug Reports and General Feedback are also enabled. Depending on the destination selected for 'Report a Bug', either the Screenshot tool, Video tool or feedback form will be loaded.

The final step to submitting feature requests with Userback is the feedback form itself. Each feedback type has its own form that can be configured. If you have multiple types of feedback selected, ensure that you have the Feature Request form selected when making changes to the form.

When adding fields to the feedback form, you can also update the placeholder text for both the Title field and Comment Field. So for example, in the comment field, you could change the placeholder text to "Help us understand how this idea would benefit your business".

Filtering feature requests with Board View

As feature requests start to come in, your overview page will give you an idea of the separation of feature requests to other feedback.

You can easily access a filtered view of your Feature Requests by clicking the Feature Requests section of the overview page.

In the board view, simply click the 'Type' Filter and select Feature Request. You can easily add or remove other types of feedback to the board by selecting from the 'Type' filter.

Configure your integrations

The final thing to do when managing feature requests with Userback is setup your integrations. You may not be using any 3rd party tools to manage feature requests and that's totally fine, Userback gives you plenty of flexibility when it comes to helping you manage them with your team. There are loads of features to help such as:

  • Adding team members to your account

  • Assigning requests to team members

  • Setting priority

  • Configuring your workflow

If however, you do use a 3rd party tool, great! Userback will allow you to sort incoming feedback such as feature requests and send them to other tools.

In this example, we're connected to ClickUp. In the Automation section, Feature Request is selected when feedback is automatically send to ClickUp.

If you manage multiple types of feedback in your 3rd party tools, you can select them here and send multiple types of feedback to the tool.

Use the JavaScript API

If you're collecting feature requests on a web app, SaaS tool or website that requires the user to log in, chances are, you already know a bunch about the users including their name, email, customer ID etc.

Using the JS API, you can automatically add this information with every Feature Request and the great thing about this is that when the customer is submitting feedback to you, via the Userback widget, they will not need to enter their email, name and other details each time.

When using the JS API, any custom data sent with feedback, will be available in the Custom Data section of the feedback.

Learn more about using the JS API

Did this answer your question?