When to Use This Message
Send a Feature Request when:
- You've identified a gap or improvement that would make a product more useful.
- You want to formally suggest an idea rather than just mentioning it casually.
- A workaround you're currently using highlights a missing feature.
- You want to explain the use case clearly so the team understands the value.
Message Writing Tips
- Describe the Problem, Not Just the Feature: Explain what you're trying to accomplish — this helps the team evaluate solutions beyond just your specific suggestion.
- Be Specific About the Desired Behavior: Clearly describe what the feature would do and how you'd expect to use it.
- Mention Your Current Workaround: If you're currently solving this another way, describe it — this shows real need, not just a hypothetical idea.
- Note How Many Users This Might Affect: If you believe this would benefit others, not just you, mention it — this can affect prioritization.
Frequently Asked Questions
How do I write a feature request that's likely to be considered?
Focus on the underlying problem and use case rather than just describing a feature — this gives the product team flexibility to find the best solution.
Will I hear back about whether my feature request is implemented?
This varies by company — some provide tracking or status updates, others don't respond individually to every request, especially at scale.
Should I suggest a specific implementation or just the need?
Both are useful — describe the underlying need first, then feel free to suggest how you imagine it working, while staying open to alternatives.