Feature Request

Join 6000+ product leaders
Sign up for our newsletter & get the best product tips straight to your inbox

How do you write a feature request?


What is a feature request?

A feature request is a comment, message, or ask from a user to implement a specific feature into your product. Feature requests can be used to decide how to iterate on an existing product.

Alongside finding a channel for reaching out to the developer, users must be descriptive about a feature request in these ways:

  • State clearly what the feature is

  • Describe how it might work

  • Explain what problem the feature would solve

  • Describe a scenario that shows the proposed feature at work

Download Now: Get our 5-minute guide on Why Insights Are Essential and How to Source Them

How do you raise a feature request?

For requests to be raised, your team needs a system in place for making these suggestions in a way that everyone on your team can quickly see. For instance, GitHub makes it easy to request features that your entire team of collaborators can see. 

How do you ask a customer for a feature request?

There are several ways to ask your customers for feature requests. First, you must have some form of open communication between you and your customers. Even if it's an automated chatbot, having a Contact Us page where users can submit requests is key. 

Second, look through user reviews. Here customers will leave direct ("Please add form optimization") or even indirect ("It takes too long to fill out forms") requests for new features. 

How do you prioritize client feature requests?

The methodology for prioritizing feature requests will vary by your team's approach and requirements. Generally, though, a hierarchy might look like this:

  1. Major bug and security fixes

  2. Minor bug and security fixes

  3. Small features and touch-ups that can be implemented in the short-term

  4. Major features and redesigns that can be implemented over the long-term

Feature request examples and templates

Feature request templates are a great way to structure the feedback your team receives from users. Without one, you'll find it difficult to collect and structure feedback from customer support and product review channels. Most feature request collection apps provide templates for structuring the feedback you receive. 

If you're looking for inspiration for writing effective internal feature requests, you can skim through this page.

How to respond to a feature request 

Responding to a feature request is known as "closing the loop". When closing the loop, it's important to acknowledge the feedback, let the user know if/how their feedback is being addressed ("We already have a plan to implement this in the next update!"), and then end the conversation. 

Reach out to airfocus for tools to help you organize, structure, and refine your feature management process.

Get our Customer Feedback eBook

A comprehensive look into all the core topics of customer feedback: what is it, how to collect it, what types of feedback we have and many tips and common mistakes you should avoid when you want to work with customer feedback effectively.

Get the eBook

General FAQ

What to expect once you've opened an issue?
Once you've opened an issue, you can expect a response from a team manager and a follow-up on when/how the issue will be addressed.
What types of feature requests are there?
The different types of feature requests are bugs, improvement suggestions, and new feature requests.

Building better products
starts here

Join thousands of product managers and makers who already enjoy our newsletter. Get free tips and resources delivered directly to your inbox.
Top rated
on major review platforms
airfocus is where teams build great products. Welcome home 💙
All rights reserved.