When you open yourself up to customer feedback and feature requests, it’s inevitable that you’ll receive the odd request that you think has no chance of working or being implemented in the future.
The way Receptive manages your feature requests, using voting and prioritization, means that any ideas deemed “good” by your customers will bubble up to the surface, and those deemed “bad” will sink down out of your way.
This means that you don’t need to worry about those requests that you’re unsure of.
That being said, sometimes an idea that you have reservations about may turn out to be something that the majority of your customers want. We would recommend not to judge feature requests too harshly until you’ve seen what other customers and internal team members think of them.
In terms of saying no to those feature requests which simply aren’t in line with your vision or strategy, you can check out our handy guide on how to say no here.