Managing Feature Request Expectations: Support AI Prompts

Telling a customer 'no' is the hardest part of support. If you're too blunt, you lose a customer. If you're too vague, they'll just keep asking. This template validates the customer's creativity and explains the 'why' (roadmap priorities), keeping them feeling heard even if the answer is negative.

The Core Blueprint

Software Environment: Outlook (Enterprise AI: Copilot, ChatGPT, Claude, etc.)
Role Focus: Support
Execution Complexity: Standard
Taxonomy Tag: #PRODUCT

PROMPT TEMPLATE

"Compose a polite rejection for [FEATURE]. Acknowledge the value of the idea, explain why it doesn't fit the current roadmap, and thank them for the feedback."

3.2k RUNS

Strategic Use Cases

This correspondence constraint acts as a direct communication architect. It forces the language model to maintain professional warmth while driving action for Support scenarios:

Explaining why a requested custom integration is not on the current product roadmap.

Politely declining niche feature requests that would bloat the core product offering.

Execution Workflow

Streamline your inbox architecture with this execution flow:

1
Ensure you have internal documentation on the current roadmap vision.
2
Open your customer support ticketing tool.
3
Run the rejection template, ensuring the tone remains appreciative and transparent.

Advanced Optimization

Ensure your correspondence drives immediate resolution by editing the prompt's behavioral tags:

Validation-Before-Rejection
...Start by saying: 'This is a creative approach to X, and I see why it would be helpful'.
Roadmap-Alignment Framing
...Explain your roadmap focus (e.g., 'we are currently prioritizing core-stability over new UI tools').
The 'Added to Wishlist' Closure
...Always state: 'I’ve added this to our product feedback loop,' so they feel their effort wasn't wasted.