Feature Request Response
Templates for acknowledging, tracking, and responding to customer feature requests.
Feature Request Received
Hi there,
Thank you for the feature suggestion! I have logged your request for [feature name] and shared it with our product team.
We track all feature requests and use them to prioritize our roadmap. While I cannot guarantee a timeline, your input genuinely helps shape what we build next.
I will make sure you are notified if and when this feature becomes available.
Is there anything else you would like us to consider? We love hearing from our customers.
Best,
{{cursor}}Feature Already Planned
Hi there,
Great news - the feature you requested is already on our roadmap! It is currently [in the planning phase / scheduled for Q[X] / being developed].
While I cannot share an exact release date yet, I can tell you that it is a priority for us. I have added your name to the list of interested customers, and you will be among the first to know when it launches.
In the meantime, here is a workaround that some customers use:
[Workaround description]
Thanks for the feedback - it is great to know we are building what you need.
Best,
{{cursor}}Feature Request Declined
Hi there,
Thank you for taking the time to share your idea for [feature name]. I appreciate the thought behind it.
After discussing with our product team, we have decided not to pursue this particular feature at this time. The main reasons are:
- [Reason 1]
- [Reason 2]
I understand this may be disappointing. Here are some alternatives that might help with your use case:
- [Alternative 1]
- [Alternative 2]
We always revisit our priorities, so please keep the ideas coming. Your feedback is valuable even when we are not able to act on it immediately.
Best,
{{cursor}}Feature Request - Need More Detail
Hi there,
Thank you for your feature suggestion. I would love to learn more about your use case to make sure we capture the full picture.
Could you help me understand:
1. What problem would this feature solve for you?
2. How often do you run into this issue?
3. How are you currently working around it?
4. Would this affect your team or just you individually?
The more context we have, the better we can evaluate and prioritize the request. Your input directly shapes our product decisions.
Best,
{{cursor}}Feature Shipped Notification
Hi there,
Remember when you requested [feature name]? I am excited to let you know that it is now live!
Here is what is new:
- [Feature description]
- [How to access it]
- [Key benefits]
You can start using it right away - no action needed on your end.
We built this because of feedback from customers like you. Thank you for helping us make the product better. We would love to hear what you think once you have tried it.
Best,
{{cursor}}Feature Exists - How To Guide
Hi there,
Good news - the feature you are looking for actually already exists! It might just be in a place you have not discovered yet.
Here is how to use it:
1. [Step 1]
2. [Step 2]
3. [Step 3]
You can also find a detailed walkthrough in our help center: [URL]
If this does not quite cover what you had in mind, please let me know more about your specific use case and I will see if there is another way to accomplish it.
Best,
{{cursor}}Feature Request Upvoted
Hi there,
Thank you for your interest in [feature name]. You are not alone - several other customers have requested this as well, and your vote helps us prioritize.
Current status: [X] customers have requested this feature
Priority: [Under review / On the roadmap / Being evaluated]
We will send you an update when there is movement on this. In the meantime, if you have specific requirements or use cases to share, please do - it helps our product team scope the feature properly.
Best,
{{cursor}}Feature Beta Invitation
Hi there,
Since you expressed interest in [feature name], I would like to invite you to try the beta version before it goes live!
What to expect:
- The feature is functional but may have rough edges
- We would love your feedback on the experience
- Beta access is available starting {{date}}
To opt in:
1. Go to Settings > Beta Features
2. Toggle on [Feature Name]
3. You are all set!
Please share any feedback, bugs, or suggestions by replying to this email. Your input will directly influence the final version.
Best,
{{cursor}}Third-Party Integration Suggestion
Hi there,
Thank you for suggesting an integration with [Tool Name]. We know how important it is for your tools to work together seamlessly.
At this time, we do not have a native integration with [Tool Name], but here are some options:
- Use our API to build a custom connection: [API docs link]
- Connect through Zapier: [Zapier link]
- Use our webhook feature to trigger actions: [Webhook docs]
I have also logged this as an integration request. If more customers ask for it, it will move up our priority list.
Best,
{{cursor}}Feature Feedback Request
Hi there,
We are currently exploring the idea of adding [feature name] to [Product Name] and I would love your input.
A few quick questions:
1. How important is this feature to your workflow? (Critical / Nice to have / Not needed)
2. How would you expect it to work?
3. Are there any tools that do this well today that we should learn from?
Your response does not need to be long - even a one-line answer helps us make better decisions. Thank you for being part of our product development process.
Best,
{{cursor}}When to use this template
- Feature request just landed. Acknowledge it within a day so the customer knows it didn't go into a black hole.
- Feature is on the roadmap but not soon. Be honest about timing without committing to a date you can't keep.
- Customer asks about a feature you've decided not to build. Decline gracefully with the actual reason, even if 'doesn't fit our roadmap' is the truthful answer.
Customize for your workflow
- Always link to your public roadmap or feedback board if you have one. Customers want a place to track, not a one-shot reply.
- If you ship the feature later, the same template can become a 'we built it!' notification. Keep a follow-up snippet keyed to the same request ID.
Common questions
How do I avoid sounding dismissive when declining?
Validate the use case in one sentence (show you understood why they want it) before explaining the decision. Bare 'no' lands worse than acknowledged 'no'.
Should I share the actual roadmap timeline?
If you have a public commitment date, yes. If you're working in quarters or 'when we get to it', be honest about that. Vague 'soon' is worse than honest 'not in 2026'.
Related reading
More Customer Support Templates
Failed Payment Response
Professional responses for handling failed payments, billing issues, and payment retry guidance.
15 snippetsTicket Escalation
Templates for escalating support tickets to senior agents, managers, or engineering teams.
10 snippetsRefund Request
Professional templates for processing, approving, and declining refund requests.
12 snippetsBug Report Response
Templates for acknowledging, investigating, and resolving customer-reported bugs.
8 snippetsOnboarding Welcome
Welcome messages, setup guides, and first-steps templates for new customers.
18 snippetsAccount Cancellation
Retention-focused templates for handling cancellation requests with empathy and alternatives.
14 snippetsService Outage
Communication templates for planned maintenance, unexpected outages, and incident resolution.
9 snippetsFeedback Thank You
Templates for thanking customers who share feedback, reviews, or suggestions.
10 snippetsSatisfaction Survey
Follow-up templates for sending satisfaction surveys and collecting customer ratings.
13 snippetsUse these snippets in TypeFire
Download the template pack, drop the .md files into your TypeFire snippets folder, and start expanding with abbreviations instantly.