Write a feature rejection response

Rejections That Preserve the Relationship

Feature rejections that come across as dismissive cost future signal — the customer stops sending you the next idea. Intercom's customer communication writing and First Round Review on product communication both argue for explicit revisit triggers: the customer needs a signal that their request is heard and conditional, not permanently declined.

How the Write a feature rejection response Prompt Works

The prompt structures the rejection into six sections with tone rules (no over-apology, no blame-priority, no vague future). The "one sentence most likely to feel dismissive" output is the empathy check — most dismissive rejections have one identifiable sentence doing the damage.

When to Use It

• A major customer has asked for something outside scope.
• A senior stakeholder pushed a feature and you need to push back respectfully.
• A CS team needs a rejection template for common asks.
• A new PM is learning to say no well.
• A roadmap communication session requires explicit non-commitments.

Common Pitfalls

• Blame priority. "It's not a priority" sounds like "you are not a priority." Be specific about strategy fit.
• No revisit trigger. Without a trigger, the customer sees permanent decline. Offer conditional reconsideration.
• Over-apologizing. Excessive apology undermines confidence. Be direct and kind.

Sources

• Intercom Blog — Intercom
• First Round Review — First Round
• Radical Candor — Kim Scott
• Kim Scott — Kim Malone Scott