Email
AI Prompt for Feature Request Email
This feature request email prompt reveals your real roadmap. Targeted asks to the right users that guide what to build. Copy the prompt and run it today.
The prompt
Role: You are a product manager who discovers the real roadmap by asking the right users the right questions. You listen more than you pitch. Context: My company is [COMPANY_NAME]. I want input on [FEATURE_OR_AREA], e.g. reporting, integrations. The audience is [USER_SEGMENT], chosen because [WHY_THEM]. The feedback form is at [FEEDBACK_LINK]. I am [SENDER_NAME], [MY_TITLE]. Task: Write a feature request email, 100 to 150 words. Open by saying you are deciding what to build next and their input genuinely counts. Ask 2 specific questions in the email: what is missing in [FEATURE_OR_AREA], and what would make their work 10x easier. Link the form for detailed ideas. Promise to share the resulting roadmap: [ROADMAP_SHARE]. End with thanks for shaping the product. Format: Subject line 'Help us decide what to build'. Then the context, the 2 questions, form link, roadmap promise, sign-off from [SENDER_NAME]. Constraints: 100 to 150 words. Genuine listening tone: no leading questions toward your pet feature. Segment precisely: relevance drives responses. Keep the roadmap promise: publish what you decided and why.
Variables to fill in
Replace each [variable] in the prompt with your own details:
[COMPANY_NAME] [FEATURE_OR_AREA] [USER_SEGMENT] [WHY_THEM] [FEEDBACK_LINK] [SENDER_NAME] [MY_TITLE] [ROADMAP_SHARE]
Example input
COMPANY_NAME: DataBridge; FEATURE_OR_AREA: the new reporting module; USER_SEGMENT: power users; FEEDBACK_LINK: form URL; SENDER_NAME: Sam
How to use this prompt
Ask the users who actually touch the feature. Share the roadmap decision afterward: transparency turns feedback into loyalty.
Tips for the best results
- Ask the users who live in the feature daily.
- Two specific questions beat open-ended 'ideas?'.
- Publish the resulting roadmap: it proves listening.
Frequently asked questions
Who should I ask about features?
Segment by usage: ask power users about depth, new users about clarity. Relevant questions get 3x the response rate of generic ones.
What should I do with negative feedback?
Reply personally within 48 hours, fix what is fixable, and report what changed. Handled well, critics become your most loyal advocates.