Say No, Keep the Fan.

The template

Hi [Name],

Thanks so much for suggesting [Feature Name]! I really appreciate you taking the time to help us improve.

While we aren't planning to build this specific feature right now, I can definitely see how it would help with [User's Goal].

I've added your vote to our internal tracker so the product team knows there is interest. If we do prioritize it in the future, I'll be sure to reach out.

In the meantime, a possible workaround might be [Workaround].

Thanks again for being a power user!

Best,
[Your Name]

Why it works

• Appreciation First — Validate the effort they took to suggest it. Ideas are gifts.
• Soft "No" — Uses "not right now" instead of "never," keeping the door open and reducing rejection sting.
• The "Tracker" Trust — Mentioning an internal tracker shows you have a process and aren't just ignoring them.

Frequently asked questions

How do I say no to a feature request without losing the customer?

Confirm you understood the request in their own words, explain the reasoning honestly rather than saying it is not on the roadmap, and offer the nearest thing that exists today. Customers accept a no far better than they accept being ignored. What loses them is a vague maybe that never turns into anything.

Should I tell customers a feature will never be built?

Say so when it is genuinely true, because a false maybe costs you more trust later than an honest no does now. If the decision is simply not made yet, say that instead and be specific about what would change it, such as how many other customers ask for the same thing.

How can I track feature requests I have declined?

Log each one against the customer record so you can see how often it comes up and who asked. Wallu tags requests automatically as they arrive across chat, email and social, so a request that gets declined five times a month becomes visible as a pattern instead of disappearing into individual inboxes.