How to Respond to Feature Requests: Real Replies to Copy
Shayan, Founder19 min read

Every feature request gets one of six answers: we're building it, not right now, tell us more, no, it already exists, or it just shipped. A good reply tells the customer which of the six it is, gives the real reason in a sentence or two, and explains what happens next.
That sounds easy until you're the one staring at an inbox full of polite requests from paying customers whose ideas aren't on this quarter's plan. Nobody wants to tell a loyal user that their workflow isn't a priority. So support and product teams reach for a cushion like "We'll pass this onto our team for future consideration."
Customers know that sentence means their message is going into a drawer. One Hacker News commenter described the standard reply they get whenever they ask a vendor for something outside the norm:
hey, great that you'd be interested in this feature! It's not something we are planning to build! why not add it to our suggestions board though - the more people who vote on it the more chance we might consider this in the future!
Then they added what every customer thinks when they read it: "of course nothing on the suggestions board is ever implemented." What they actually wanted to hear was much simpler:
sorry, your use case is an edge case and not something we support; you could try doing X or Y but what you're attempting is outside our typical use and not on our roadmap.
To see what works better than polite brush-offs, I went through real staff replies on the public boards and community forums of ClickUp, Ahrefs, Retool, Glide, Descript, Supabase, Vercel, and Zapier, along with the customer comments underneath them. If you're still setting up how you collect and triage ideas, start with our feature requests guide or compare the best feature request tools. Below are the replies that held up, the ones that backfired, and a plain template you can copy for each situation.
1. We're building it
When a customer asks for something you're actually planning to build, the trap is getting excited and promising a release date before the work is scoped. Then a migration takes twice as long as expected, and a happy thread turns into customers asking every two weeks why the feature still isn't live.
When the feature is genuinely on the schedule and simple to state, a short confirmation is enough. After a user on Glide's forum asked for screen deep linking, Glide CEO David Siegel replied: "Yes! Deep linking is planned." On n8n's forum, founder Jan Oberhauser explained why user and privilege management was taking time before giving a rough window:
Yes, but adding User Management is sadly not a feature we are able to push out in a few hours and also nothing you want to get wrong. For that reason did we not get to it yet. It is however something we want to get out in the next few months.
When a feature is close to shipping, describing what it will actually do helps more than a calendar date. On ClickUp's mobile board, where offline support had 4,430 votes, a staff member posted in October 2026:
Offline task editing is almost done! You'll be able to make changes with no connection and they'll sync once you're back online. No firm date yet, but it's close.
And if the rollout comes with a catch, name the catch up front so nobody feels misled on launch day. When Tanner Pierce on Retool's product team confirmed public app links in September 2026, he shared the target quarter and immediately set expectations about which plan would get it first:
To set expectations, we're currently planning to make Public Apps available to Enterprise customers first, before considering expansion to other plans. In the meantime, if you need to share an app outside your organization, you can add people as External Users.
Most teams avoid giving a date unless the code is almost out the door, and when they do share a timeline, it's a quarter or version number rather than a day. Confirm what you're building, mention any caveats early, and tell them how they'll hear when it ships.
Yes, we're building this. [One sentence on what it will do.]
I don't have a firm date to share yet, but when it's ready I'll
post an update here and you'll get an email. Until then, you can
[workaround, if one exists].2. Not right now
"Not right now" is the most common answer on any product board, because good ideas always outnumber the engineers available to build them. The trap is flipping a status badge to Not on the roadmap or pasting a cheerful thank-you paragraph without saying what your team is working on instead. Customers read a bare status label as "we don't care, and we're never doing this."
Look at what happened on ClickUp's board in December 2025 when a staff member moved a 636-vote request for subtask permissions to "not on the roadmap" with a generic template:
While this isn't something we're planning to add to our roadmap right now, we truly appreciate your input. Please keep sharing your thoughts and suggestions with us!
Nine days later, a second ClickUp staff member had to step into the thread to calm voters down and explain what the status change actually meant:
Just to clarify, the new status only means it's not on our immediate roadmap right now, not that we'll never do it. At the moment we're heads down on other core quality work, but we will still look at what it would take to tackle this.
When a popular request gets that same status with no staff comment at all, the thread turns sour fast. ClickUp's request for Ctrl + Z undo has 9,018 votes and sits at "not on the roadmap" with no recent staff explanation in view. Customers in the comments wrote: "to not even be on the roadmap with 9,000+ upvotes (!!) is very uh... surprising lol" and "8 years and 9k+ upvotes. Undo is a core basic functionality, how is it not considered for the roadmap at all?"
Contrast that with how Tess on Retool's team handled a request for developer dark mode in January 2023. She told the thread why it wasn't making the cut that quarter by naming what was ahead of it:
Currently, this is not something we've been able to fit into our roadmap for this quarter, but it's definitely on our radar. For reference, a lot of our resources for the next quarter will be dedicated to some larger planned projects (for example, revamping the table).
Ten months later, when a user checked back in on the thread, she replied honestly again:
Unfortunately, we had several large scale projects that were prioritized over this feature this year. That said, we are still tracking feedback and requests for this feature ... Really wish I had better news
Naming the competing priority turns a frustrating brush-off into a trade-off another builder can understand.
We aren't able to fit this onto the roadmap this quarter because
our team is focused on [what you're building instead, in one line].
I've linked your note to [the request on the board], so you'll get
an email if the status changes.If someone bumps the thread six months later and your priorities still haven't shifted, don't dodge them:
Thanks for checking in. We prioritized [the other projects] over
this during the past few months, so we still haven't started work
here. We're keeping the request open and will post here when we're
able to pick it up.3. Tell us more
A lot of feature requests look unusable at first glance only because they're missing one sentence of context. Jitbit's Max Al Farakh wrote that in his experience "50% of all feature request can be solved using existing features," and Carolyn Kopprasch, chief happiness officer at Buffer, recommends asking customers what they're ultimately trying to achieve: "We can learn a lot from those kinds of conversations, if they're willing to indulge us."
When you want to understand the problem behind an ask, keep the question narrow. On Ahrefs's board, Tim Soulo replied to a Rank Tracker request with two quick questions: "what is the use case for that? And where do you want to see this data in the interface?"
When a thread is long and messy, reading the problem back to the user works better than asking an open-ended question. On a 2,792-vote ClickUp thread about formula fields in dashboards, a staff member summarized the complaints into three points, covering slow formula fields, no calculations on aggregated fields, and supporting all formula fields everywhere, and asked: "Is that an ok summarization?" And when a user asked for a way to mute chat channels, another ClickUp staff member linked the existing notification settings and asked a question that helps fix the UI:
Was there anything you could share on why you thought this functionality didn't exist? Was it hard to find?
The trap with discovery questions is asking them when you already know the answer is no. On ClickUp's board in early December 2025, a staff member replied to a 587-vote request about inviting guests to a whole Space by asking which part of the flow felt like "the biggest time sink: hunting down each folder in the list, reconfiguring permissions every time, or something else?" Twenty-six days later, the request was moved to "not on the roadmap" with a pasted template. Another thread on subtask templates asked users for their use cases and shared a Calendly booking link in July 2025, only to tell them a month later that the feature was already possible and move the post to "not on the roadmap."
Only ask a customer to do homework when their answer can still change what you build.
Quick question so I make sure we solve the right problem: what are
you trying to get done when you run into this, and how are you
working around it today? A sentence or a screenshot is plenty.4. No
Roughly half of the declines on public feedback boards give no reason at all. Support and community teams default to "We'll pass this onto our team for consideration" because saying no feels confrontational.
In reality, leaving a customer hanging on a feature you know you'll never build wastes their time. As Basecamp's Chase Clemons wrote on the company blog:
If we're not going to do it, we tell the customer so. This sets expectations up front and lets the customer know if they need to explore an integration, use a workaround, or consider switching to a different product.
Raycast's Thomas Paul Mann described their approach the same way:
If we receive a suggestion that we won't build, we let them know. We want to set the right expectations. If they share our opinion and adopt the tool, that's great. If they stop using the tool, that's fine as well.
A good no doesn't need to be an essay. It just needs the real constraint, whether that's architecture, licensing, a third-party dependency, or product focus, plus a workaround if you have one.
When users asked Supabase to host TimescaleDB in February 2021, kiwicopple on Supabase's team gave the exact reason in three sentences:
I reached out to the founders of TimescaleDb. Unfortunately their license won't allow it because we're a hosted platform. I understand their stance - they have their own hosted platform.
When Descript closed a request to keep original files off the cloud in December 2025, staff member Gabe Michalski wrote: "We've since moved to full cloud-based file storage so this is not something that will be considered any time soon."
When the blocker is outside your control, pointing to third-party tools takes the sting out of the rejection. Andy Claremont on Glide's community team explained why they weren't bringing back push notifications:
Unfortunately the push notification issues with PWAs in iOS are a blocker. They're caused by dependencies beyond our control. That's why we kept the feature in beta but ultimately deprecated it.
Right under that explanation, he listed three ways users could still send notifications through Twilio, Microsoft Teams or Slack, or Pushover. A Basecamp customer, quoted in a Help Scout article by former Basecamp support member Emily Triplett Lentz, described what a reply like that feels like from the customer's side:
She gave me an answer that I really didn't want to hear, but gave me a work-around that was elegant enough that I forgot to be sad I didn't get what I asked for.
We won't be building this. [One or two sentences giving the real
product, technical, or business reason.]
If you need to handle this today, you can [workaround, integration,
or alternative tool]. If our plans change down the road, we'll
update [the request on the board].5. It already exists, or someone already asked
Customers don't memorize your help center or read every thread on your board before they write in. Often the thing they're asking for is sitting two menus deep, or another customer asked for the exact same thing last month.
When the feature already exists, skip the lecture and tell them where to click in one line. ClickUp closed a 56-vote request to sort notifications from oldest to newest with a single sentence: "You can change today's Inbox to be sorted by oldest first or newest first!" When users asked Descript to stop adding itself to macOS login items, Gabe Michalski linked the help article and put the answer right in the comment so nobody had to go hunting:
TLDR: It's not in launch items specifically - it's a setting in Descript menu tray / screen recorder button.
If the capability exists on a higher tier, state that plainly without turning it into a sales pitch, the way Ahrefs's Andrey Kirillov did on a request to export more than 100,000 keywords: "It is possible to export more than 150K keywords with an Enterprise plan" followed by a link to the pricing page.
When the feature doesn't exist yet, but someone else already asked for it, tell the customer what merging their post actually does for them. A ClickUp staff member merged a mobile task-view request with: "We are working on this right now actually as part of another request. I will merge these so you can keep up to date with task view changes." On Zapier's community forum, a moderator explained the benefit of the merge in plain English:
I have added your vote for it so you'll get an email the second it becomes available. No ETA on if/when you can expect to see this implemented but we'll be sure to come back to this thread with any updates in the meantime.
When the feature already exists:
Good news, you can already do this in [Product]: [where to find the
setting in one line, plus a link to the docs]. If that doesn't quite
cover what you're trying to do, let me know what's missing.When someone else already asked for it:
Someone else asked for this on our board here: [link]. I've merged
your request into that thread so your vote counts toward it and
you'll automatically get an email when its status changes.6. It shipped
The "we built it" reply is the most enjoyable message you'll ever send to a customer, and it's also the easiest one to forget. By the time a feature makes it through QA and ships, the team is already thinking about the next sprint, and the feedback thread from two years ago is the last thing on anyone's mind.
On Ahrefs's board in April 2020, Tim Soulo closed an 82-vote internal-links request with a candid admission: "Oops. Forgot to update you guys. We have released two reports..." Another Ahrefs request was marked complete with: "This feature to add keywords to Rank Tracker from Keywords Explorer has been added some time ago."
When you catch the thread on release day, the message doesn't need fanfare. It just needs to say what shipped, where to find it, and any caveat the user might run into. Ahrefs's Andrey Kirillov closed a 66-vote request in one sentence: "Export to Google Sheets is now available in all Keywords Explorer and Site Explorer reports!" When Ahrefs shipped its URL Rating history chart, staff member Fedor Fokin added the one detail power users would immediately ask about:
UR history chart has been added to Overview 2.0 🎉 Note that this UR is based on a new algorithm different from the old Site Explorer, and its history starts in August 2022.
Replying directly to the people who described their workflows in the thread makes an even stronger impression. On ClickUp's 4,066-vote Google Calendar sync thread, calendar team lead Ricardo Clerigo replied to individual commenters by name:
Hey Alejandro ... you can now see all your GCal events in ClickUp and find those empty time blocks to schedule tasks into. Your workflow should work end-to-end now.
Airtable's team did the same when they shipped email confirmations for help-center feedback:
Thanks @kuovonne , and great idea! This is now implemented; we'll send over an email confirmation when comments are added to the feedback, and an email address is provided.
You asked for [feature name], and it's now live. You can [what it
does, in one sentence] under [where to find it in the app]. [One
caveat or link to the release notes, if needed.] Thanks for pushing
us to build it.When a yes turns into a not right now
Plans change. A feature you genuinely intended to build in Q2 gets bumped by an infrastructure rewrite, or an integration turns out to be ten times harder than the prototype looked.
The worst thing you can do when a planned feature stalls is quietly flip the status badge back to Open or Future and hope nobody notices. Customers watching a popular thread notice every status change. ClickUp had a QuickBooks integration marked Planned since December 2019 with 1,319 votes. In August 2025, a staff member moved it back to Future with a stiff two-liner:
We've updated the status of this request to reflect the current progress. There is no current estimate, but examples are always welcome to help clear up what we would need to build once we are ready to pick this up.
Compare that with how Ahrefs's Fedor Fokin handled moving a 71-vote request for Ahrefs Rank history from In Progress back to Open in May 2023. He gave the specific product reason:
We can add Ahrefs Rank over time as well as Domain Rating history to Overview 2.0, but since these metrics are very similar, we plan to add only DR for now. So if you are interested in both, please let us know in the comments.
And if someone on your team changes a status by mistake, own it right away. When ClickUp's Google Calendar sync thread got flipped to the wrong status in February 2026, Ricardo Clerigo opened his update with:
First - excuse us 🙈 for the incorrect change of status that recently happened to this task. I can assure you we are very much actively working on this.
When you have to walk back an earlier yes, say what changed and what the status means now:
We originally planned to ship this in [quarter/window], but we've
had to pause work on it because [the real reason, in one sentence].
I'm moving this request back to [status] so the board reflects where
things actually stand, and I'll post here when we pick it back up.Why changing a status without a comment backfires
Nearly half of the status changes on public feedback boards go out with no staff comment attached. Someone on the product team does a Friday afternoon backlog sweep, moves twenty cards to Closed or Not on the roadmap, and shuts their laptop.
Status badges work well for routine forward progress. Buffer tells users on its roadmap that "We'll notify you when a feature goes from being 'Planned' to 'In Progress' to 'Complete'." Zapier tells voters that "your vote ensures you're emailed if that changes," and Dropbox prompts users to "Follow ideas to get updates when statuses change." Even when a feature takes a long time, voters appreciate seeing the badge move forward: on tl;dv's board, a customer named Natascha celebrated in January 2025 when a 98-vote Make.com integration moved to Planned, calling it the highlight of her day, and came back a year later in January 2026 when it moved to In Progress to joke, "every year again 'highlight of the day'!"
When a request stalls, moves backward, or closes without being built, a status change with no comment beside it feels like a door slammed in the customer's face. Even an automated housekeeping rule needs a human explanation, like the note a Zapier staff member left after an active request thread auto-closed: "topics auto close after a certain time frame and truly isn't done out of ill intent."
The status change sends the update for you.
On a UserJot board, changing a request's status emails everyone who posted, voted, or commented, and commenting as a teammate emails the person who asked. Free to start.
Keeping replies connected to the board
The reason support teams fall back on vague brush-offs is that the chat inbox and the feedback tracker usually don't talk to each other. The person answering support tickets has no easy way to check if an idea is already on the board, attach the customer's email to it, and make sure they hear back six months later.
We built UserJot so the reply in chat and the request on the board stay linked. Inside the in-app widget, your feedback board sits alongside live chat when you turn on Conversations, which is currently in beta and free on every plan. When a customer asks for a feature in chat, our support agent Juno searches your public feedback board, shows them the matching request, and once they confirm, adds their vote or files a new request on their behalf. If a request comes in by email instead, an admin can post it on behalf of the customer in a couple of clicks.
That makes your human reply much simpler. Whether the answer is "we're building it" or "not right now," you can leave a two-sentence explanation on the request and link the customer straight to it. A new comment from your team emails the person who posted the request, while internal comments stay private to your teammates. Whenever you move the status to Planned, In Progress, Completed, or Closed, UserJot automatically emails everyone who posted, voted, or commented. Marking a request Planned or In Progress also puts it onto your public roadmap without a second step, and when you mark it Completed, you can link the finished request right under your changelog post.
What to cut from your replies
Before you hit send on a feature request reply, read it back and cut the filler that makes customers tune out.
Cut "we'll send your feature request to the development team" if nothing happens after you say it. As a merchant on Shopify's community forum complained in January 2025, users get tired of hearing "we'll send your feature request to development Team," a team "who will never get back to you or you never hear from anyone in shopify." Either link the customer to the request on your board so they get status emails, or tell them right there in the thread that you aren't building it.
Cut "it's on our radar" and "stay tuned" unless you name what is ahead of the request or where they should tune in. Cut the three-sentence thank-you paragraph in front of a one-line rejection. A direct "Thanks for asking about this. We aren't planning to build it because..." respects the reader's time much more than a sandwich of compliments. As that same Hacker News commenter put it:
As a customer I'm much more likely to cancel a service if I get Vague! Happy! Pointless! customer service interactions rather than honest responses.
Save your apologies for when you miss a deadline or flip a status by mistake, not for having a product strategy. And if you want to build a shared library of support replies that still sound like a person wrote them, see the examples in our guide to canned responses.
Frequently asked questions
How do you respond to a feature request?
Start by stating which of the six answers applies: you're building it, not right now, you need more detail, you won't build it, it already exists, or it just shipped. Follow that with a one-sentence reason and tell the customer what happens next, such as linking the board thread where status updates will be posted. Most effective replies from teams like ClickUp, Ahrefs, and Supabase fit in three sentences.
How do you respond to a customer about a feature request you will not build?
Say no plainly, share the real technical or product constraint in a sentence, and offer a workaround, integration, or alternative tool if one exists. When Supabase declined a request to host TimescaleDB, the team explained that TimescaleDB's license didn't allow other hosted platforms to run it. Customers handle a direct no well when they understand the reason behind it.
Should you give an ETA on a feature request?
Only give a timeline when the work is scoped and you're confident in the window, and even then, prefer a quarter or version number over a calendar date. When a feature is close but not locked in, a reply like ClickUp's "Offline task editing is almost done! ... No firm date yet, but it's close" builds excitement without setting a deadline you might miss.
What do you say when the feature already exists?
Tell the customer where to find the setting in one sentence, include a direct link to the help article, and ask what's missing if that doesn't solve their problem. When users asked Descript how to stop the app from opening at startup, a staff member linked the docs and gave the exact menu path right in the reply.
How do you respond to a duplicate feature request?
Merge the new post into the existing request and tell the customer that their vote was carried over so they'll automatically get an email when the status changes. Zapier's community team uses a clean version of this: "I have added your vote for it so you'll get an email the second it becomes available."
How do you tell a customer their feature request shipped?
Name the request they asked for, explain what shipped and where to find it in the app, and send the update to everyone who posted, voted, or commented. On ClickUp's Google Calendar sync thread, the calendar team lead replied directly to commenters to explain how their specific scheduling workflow now worked end to end.
Should you reply to every feature request?
Every request on a board should get an accurate status, and any request you decline, stall, or have questions about should get a short written note explaining why. Some teams like Raycast read and answer every message individually, while others like Basecamp and Todoist read everything but only reply when they have a follow-up question or a clear decision. What frustrates users isn't a stated policy, it's a popular request sitting silent or moving to "not on the roadmap" without a word of explanation.
What should a feature request reply never say?
Avoid saying "we'll pass this onto our team for consideration" with no way for the customer to track the idea, or "it's on our radar" without naming what you're prioritizing ahead of it. Skip the three-sentence thank-you paragraph before a rejection, and never promise a release date just to end an uncomfortable conversation.


