Feature Request Response Prompt Templates
AI prompt templates for feature request responses. Acknowledge and manage customer product suggestions.
Overview
Feature requests are gifts. Customers are telling you what they need and what would make them happier. Even when you can't build what they ask for, how you respond affects their loyalty. These templates help you acknowledge requests, set realistic expectations, and maintain relationships with customers who want something you might not build.
Best Practices
Respond to every feature request, even if the answer is no. Being ignored feels worse than being declined
Don't promise what you can't deliver. 'We'll consider it' is better than 'we'll add it soon' if you're not sure
Explain your reasoning when you decline. Customers respect honest 'why' explanations
Track requests and follow up when you ship something they asked for. It builds incredible loyalty
Ask clarifying questions. The feature they ask for might not be what they actually need
Prompt Templates
1. Acknowledge Feature Request
Write a response acknowledging a feature request. Requested feature: [WHAT_THEY_WANT] Is it on your roadmap: [YES/NO/MAYBE] Similar existing feature: [IF_ANY] Timeline (if known): [ESTIMATE_OR_NONE] Write a response that: 1. Thanks them for the suggestion 2. Confirms you understand what they're asking for 3. Gives an honest status without overpromising 4. Offers alternatives if any exist Appreciative and honest.
Requested feature: Dark mode for the mobile app Is it on your roadmap: Yes, planned for Q2 Similar existing feature: None Timeline: Q2 this year
Thanks for the dark mode suggestion! You're not the only one asking for this. Good news: it's already on our roadmap for the first half of this year. I don't have an exact release date, but it's actively being worked on. I've added your email to the list of people to notify when it launches. Appreciate you taking the time to write in.
Responding to feature requests that you're planning to build
- •If it's on your roadmap, say so. Customers love knowing they asked for something that's coming
- •Keep a list to notify them when it ships. Following through builds serious loyalty
2. Decline Feature Request
Write a response declining a feature request. Requested feature: [WHAT_THEY_WANT] Why you're not building it: [HONEST_REASON] Alternative or workaround: [IF_ANY] Door open for future: [YES/NO] Write a response that: 1. Thanks them for the idea 2. Explains why you're not building it (briefly) 3. Offers an alternative if one exists 4. Doesn't sound dismissive Honest but respectful.
Requested feature: Integration with obscure CRM that 2 customers use Why you're not building it: Low demand, would require significant maintenance Alternative or workaround: Zapier integration works with that CRM Door open for future: If demand increases
Thanks for the integration suggestion. I looked into it, and right now we don't have plans to build a native integration with that CRM. Here's the honest reason: building and maintaining integrations takes ongoing work, and we haven't seen much demand for this particular one. We have to prioritize integrations that help the most users. That said, our Zapier integration works with that CRM. It's not as smooth as a native integration, but it can handle most of the common workflows. Here's a guide on setting it up: [link] If we see more demand for this in the future, we'll reconsider. I've logged your request so it counts toward that.
When you need to decline a feature request
- •Explain the 'why' briefly. Customers respect honest reasoning even when disappointed
- •Always offer an alternative or workaround if one exists
3. Feature Request Clarification
Write a response asking for more details about a feature request. What they asked for: [VAGUE_REQUEST] What you need to understand: [SPECIFIC_QUESTIONS] Possible interpretations: [DIFFERENT_THINGS_THEY_MIGHT_MEAN] Write a response that: 1. Thanks them for the idea 2. Shows you're taking it seriously 3. Asks specific questions to understand the real need 4. Explains why understanding their use case helps Curious, not interrogating.
What they asked for: 'Better reporting' What you need to understand: What reports, what format, what data Possible interpretations: More report types, different visualizations, export options, scheduled reports
Thanks for the feedback on reporting. I'd love to understand more about what would make reports better for you. A few questions: - Are you looking for different types of reports than we currently offer? - Is it about how the data is displayed (charts vs tables, etc.)? - Do you need better export options (PDF, CSV, scheduled emails)? - Or something else entirely? Understanding your specific workflow helps us build something that actually solves the problem. If you can share an example of what you're trying to accomplish, that's even better.
When a feature request is too vague to act on
- •Give multiple choice options. They're easier to answer than open-ended questions
- •Ask about their goal, not just the feature. Sometimes there's a better solution
4. Feature Shipped Notification
Write a notification to someone whose feature request was built. Original request: [WHAT_THEY_ASKED_FOR] What you built: [WHAT_YOU_SHIPPED] How to access it: [WHERE_TO_FIND_IT] Any differences from their request: [IF_DIFFERENT] Write a message that: 1. Reminds them they requested this 2. Announces it's live 3. Shows them how to use it 4. Thanks them for the input Excited but not over-the-top.
Original request: Keyboard shortcuts for common actions What you built: Full keyboard shortcut system with customizable bindings How to access it: Settings > Keyboard Shortcuts, or press ? anywhere in the app Any differences from their request: We added customization they didn't ask for
Remember when you asked for keyboard shortcuts? They're live now. Press ? anywhere in the app to see all available shortcuts. We also added the ability to customize them if you want different bindings, which you can do in Settings > Keyboard Shortcuts. Thanks for suggesting this. You weren't the only one who wanted it, but you were one of the first to ask. Hope it makes things faster for you. Let me know if anything doesn't work the way you expected.
Following up with customers when you ship something they requested
- •These follow-ups create superfans. Don't skip them
- •If what you built is different from what they asked, explain why
Common Mistakes to Avoid
Ignoring feature requests or sending only automated replies. Customers who suggest features are engaged and worth responding to personally
Saying 'we'll look into it' for everything. If something is never going to happen, it's better to say so
Not tracking who requested what. Following up when you ship something is one of the highest-ROI support activities
Frequently Asked Questions
Feature requests are gifts. Customers are telling you what they need and what would make them happier. Even when you can't build what they ask for, how you respond affects their loyalty. These templates help you acknowledge requests, set realistic expectations, and maintain relationships with customers who want something you might not build.
Related Templates
Support Ticket Response Prompt Templates
AI prompt templates for support ticket responses. Handle customer inquiries efficiently and professionally.
FAQ Response Prompt Templates
AI prompt templates for FAQ responses. Create comprehensive answers to frequently asked questions.
Chatbot Script Prompt Templates
AI prompt templates for chatbot scripts. Design conversational flows for automated customer support.
Have your own prompt to optimize?