How to decline a feature request without leaving customers guessing

Ask about the problem, explain your decision and offer a useful alternative when you can. Here is a practical process for handling requests you cannot take on.

A customer asks for a small addition. You want to help, but your team already has work planned and the request would add more to build, test and maintain.

It is reasonable to decline it. The important part is giving the customer a clear answer and taking the problem behind the request seriously.

Understand the problem first

Before deciding, ask what the customer is trying to do and how they handle it now. A request for a particular feature may point to a problem you can solve another way.

Useful questions include:

  • "What problem is this solving for you?"
  • "How are you working around it currently?"
  • "Would [alternative] achieve the same thing?"

Check whether other customers have raised the issue. Keep related requests together so you can review demand without relying on who last emailed you. Our guide to moving feedback into development covers that process.

Give a direct answer

Thank the customer for explaining the request. Then say whether it is planned, deferred or something you have decided not to build.

Give a short reason they can understand. You might be focused on another product area, avoiding complexity for other users or unable to justify the maintenance involved. Avoid vague promises that suggest work has been agreed when it hasn't.

For example:

"We've looked at this carefully. It's not something we're prioritising right now — we're focused on [X], which will have a bigger impact for most of our users."

Make sure the explanation is true for the request you're answering. You can find more on setting expectations in common feedback mistakes.

Offer an alternative if there is one

An existing feature, integration or workaround may help. Explain its limits as well as what it can do, and don't present a cumbersome workaround as a full solution.

If you don't have an alternative, say so. A clear answer is more useful than asking a customer to try something that won't meet their needs.

A reply you can adapt

Hi [Name], thanks for explaining what you need.

We're not planning to build [request] at the moment because [reason]. I've recorded the problem so we can include it in future reviews.

In the meantime, [alternative] may help with [specific task]. It won't cover [limitation], but I can help you set it up if useful.

Thanks, [Name]

Remove any sentence that doesn't apply. Only promise to record, review or follow up on a request if your team has a way to do that.

Distinguish a deferral from a final decision

Some requests don't fit the product. Others need to wait for capacity, more evidence or a dependency.

Record the difference in your feedback system. For deferred requests, note what would cause you to review the decision and set a sensible review date. If the feature later goes ahead, tell the people who asked for it.

Keep the process consistent as requests grow

A shared feedback record helps your team see related requests and previous decisions. It also prevents two colleagues from giving the same customer conflicting answers.

FeedbackNexus lets you collect requests, review demand and keep customers informed about status changes. You can read more about measuring the cost of feedback management and prioritisation frameworks if you're setting up your process.

Start a free trial to try it with your own feedback.