To say no to a feature request, say it early, in the first sentence, with the real reason and what the person can do instead. Then say it once, on the request itself, where everyone who asked for it will read it. A request left open for a year is also a no, only without the reason. Below: what a good no says, six replies to copy for the usual cases, and how to tell every voter at once instead of answering forty comments one by one.
Why a clear no beats an open request#
An open request reads as a promise. A board full of old requests with dozens of votes and no answer tells your customers that asking doesn't work, and they stop asking.
A no with a reason is useful to the person who asked:
- They stop waiting. They pick a workaround or another tool today, rather than in six months.
- They can argue with the reason. Sometimes they're right, and the reason misread what they need.
- Your team stops answering the same question in support, in sales calls and in the next posts that ask for it.
Most people take a clear no better than silence.
What a good no says#
Four parts, in this order:
- The decision, first. "We've decided not to build this." Not "not at this time", which everyone reads as "soon".
- The reason, in their terms. Not "it's not on the roadmap", which is the decision again, but why: the complexity every user would pay for, a direction the product won't take, a risk you won't run.
- What they can do instead. A workaround, an integration, an export, your API, or another tool that does it well.
- What would change your mind, only if something would. "If more teams ask for this, we'll look again" is honest when you mean it. When nothing would, say nothing: a door left open on purpose is a polite way to keep them waiting.
A short thanks goes first, and that's all the apology a no needs.
Six replies to copy#
Fill in the brackets. Each reply is meant for the request itself, where every voter reads it, rather than for one person's inbox.
It doesn't fit the product#
Thanks for writing this up so clearly. We've decided not to build it: [product] is for [who it's for], and [the feature] would pull it toward [what it would become]. We'd rather tell you now than leave this open for months. If you need it today, [another tool or a workaround] does it well.
Not now, but it may come back#
We agree this is a real problem, and we read every vote on it. It isn't in our plans for [the next few months], because [what comes first, and why]. We're keeping it open, and everyone who voted will hear when that changes.
This one isn't a closed request: leave it open, or move it to Under review, so that it stays a question.
It already exists#
Good news: you can do this today. [The steps, or a link to them.] We're closing this request, and we'll look at why it was hard to find.
It's a duplicate#
This asks for the same thing as [the other request], so we've merged them. Your vote moved there, and you'll hear about it from now on.
A merge is a no to the copy and a yes to the conversation: everything should move to the one request that stays. See duplicate feature requests for what a merge must keep.
Only one customer needs it#
This would solve it for your team, but we haven't heard it from others, and every option we add is one more that everyone has to learn. What we can offer is [your API, a webhook, an export], which lets you build exactly this on your side: [link].
We won't, for security or privacy reasons#
We won't add this: it would mean [storing what we shouldn't, or sharing it with someone who shouldn't see it], and we don't do that for anyone. Here's what we do instead: [the safer way].
This is the one no that needs no "what would change our mind".
Tell every voter at once#
Answering each comment doesn't scale, and a reply that reaches one person leaves everyone else who voted still waiting. Say it once, on the request, and let the people who follow it hear. In Swingback:
- Change the status, with a note. Closed for a no, Under review for a not-now. The note shows on the post, beside the change, for anyone who opens it.
- Everyone who follows the post hears. Writing, voting for or commenting on a post follows it, so its author, its voters and its commenters get a notification that its status changed, in the portal and by email, unless they turned those emails off.
- Pin the longer answer. A team comment, pinned to show first, holds the full reasoning, so the next visitor reads it before voting.
- Keep the post. Deleted, the request comes back next week from someone else. Closed, it stays findable, it shows among similar posts while people type a new one, and it still takes votes: if they keep coming, the no deserves a second look.
- Keep the internal reasons internal. An internal note holds what customers shouldn't read, such as a deal, a competitor or the cost, and never reaches the portal.
Posts in the docs has the statuses, and Notifications who hears what.
When the no happens in your tracker#
Sometimes the decision is made in GitHub or Linear, while planning. With Swingback's sync Beta, the board can follow it: by default, a post closes once its issues are closed as not planned on GitHub, or canceled in Linear, and its followers hear, as with any status change. See an issue moves its posts.
What doesn't travel is the reason. A status the sync sets comes without a note, so add a pinned team comment that says why, or close the post yourself with a note before you close the issue.
If you decide your requests in Linear, collecting feature requests for a Linear team shows how the two stay in step.
The no you didn't say#
A request that waits a year with no answer has been refused already, without a reason and without a way forward. Go through your oldest open requests once a quarter: each gets a yes, a not-now with a reason, or one of the replies above. The board gets shorter, and the requests that remain mean something.
