Saying No to Feature Requests
Respond to requests with clarity and respect.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
Help me respond to feature requests. The request: [REQUEST]. Who asked: [REQUESTER]. Our current priorities: [PRIORITIES]. Reasons it doesn't fit now: [REASONS]. Draft three responses: to a customer, to a sales colleague, and to an executive. Each should acknowledge the need, explain the decision based on priorities, state what happens next (revisit date, workaround, alternative), and avoid false promises. Include questions to ask to understand the underlying problem. Provide a template for logging requests with fields for problem, frequency, segment, and workaround, and a quarterly review routine. Add a short list of phrases to avoid that sound dismissive, with kinder alternatives, and a decision aid for when a request should be accepted despite the current priorities, such as a security issue or a contractual commitment. Provide a method for tracking how often the same request appears and how to use that count to reconsider the decision with evidence. Also include a one-line internal note I can use to record why the request was declined, with a date to revisit.
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.