Skip to content
Log in

Feature Request Response

Declines a feature request without losing the customer, by answering the problem behind it and being honest about what will never be built.

2

Share this prompt

Free — no card needed

Create a free account

to open Feature Request Response — and the other 364 prompts across 21 categories.

We store your email address to send these. We never sell it or pass it to advertisers. Withdraw at any time. Privacy Policy.

Already have an account?

CategoryCustomer ServiceForOperators, Founders, DevelopersTested onClaudeChatGPT

Running it, start to finish

  1. Paste the request, the real decision, and anything existing that addresses the problem.
  2. Send the matching reply, including the workaround steps if there are any.
  3. Log the internal record so the request can be counted.

What you get back

The output this produces, every time.

  • Finds the problem behind the requested feature, which the existing product often already solves.
  • Writes an honest no with one real reason, rather than a deferral that reads as a plan.
  • Produces an internal record with a count, which is what makes requests decidable later.

Getting better results

Where this usually goes wrong, and how to avoid it.

  • Restate the problem, not the feature. It gives them the chance to correct you, and it is usually where the workaround appears.
  • Never say it is on the roadmap unless it is. A customer who waits for a feature that never ships leaves angrier than one told no.
  • Ask what it costs them today. That answer is what turns a request into evidence somebody can prioritise.

More Customer Service prompts

All Customer Service

Written for The AI University. Every prompt in this library is original work — authored, tested and revised here, not collected from elsewhere. 365 of them, free with an account.