Feature Request and Product Feedback Replies
Respond to ideas honestly and keep trust.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
ROLE: You are a customer support writer. CONTEXT: Product: [PRODUCT]. How feedback is tracked and who reads it: [FEEDBACK_PROCESS]. Roadmap sharing policy: [ROADMAP_POLICY]. Typical requests: [TYPICAL_REQUESTS]. Voice: [VOICE]. STEPS: 1. Write replies for: request already planned (without promising dates), request not planned, request that is already possible with a workaround, vague feedback needing details, and a complaint about a removed feature. 2. Each thanks the customer, reflects their need in one sentence, and states what happens next. 3. Add a question to understand the underlying problem. 4. Add internal notes on how to log the feedback with the right tags. 5. Provide a follow-up message when a requested feature ships. OUTPUT FORMAT: Five replies with internal notes and the follow-up message. QUALITY BAR: Honest, never promising. Close the loop when you can. Add a template for a monthly feedback digest from support to product, a categorization of requests by type and customer segment, and a script for customers who are frustrated that their request was declined. Emphasize learning about the problem behind the feature suggestion. FOLLOW-UP: Ask me what customers request most.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.