How we handle feature requests
Posted by Renewed Vision Support on October 29, 2013 at 12:58 PM
Updated by Renewed Vision Support on Mar 3, 2017
RenewedVision has advanced software used by thousands of organizations, all around the world. That means we receive a lot of great feedback, suggestions and wishes from our customers of all shapes and sizes.
Unfortunately, this means we need to say 'no' a lot more than we would like. In fact, in many cases we are unable to provide a response or timeframe to each feature request. However, we do read all of the feedback and suggestions sent to us, and prioritize feature request based on a number of factors.
We want to be transparent about the way we handle feature requests, so have outlined how we handle feature requests below.
Feature requests in general
Making a feature request
We regularly review feature requests and suggestions made on the forum. The forum is where suggestions start out, where they gather popularity and evolve as ideas.
Tracking feature requests
What goes in, what stays out
We take into account a number of factors when deciding which feature requests to implement. This is a combination of feedback from our customers, people we consider power-users, our own market research, the availability of our own team and resources, and how the feature fits in with our long-term product plans and strategy.
Special thanks to Kayako for allowing us to borrow, nearly word-for-word, this article. Kayako is the help desk software we use for tickets and our knowledgebase.