Skip to main content

Private beta — 15% off for early teams · Join the beta

For software and SaaS teams

Feature request reply templates

Feature requests deserve a real answer, not a black hole. Tell people what will happen with their idea, even when the answer is no, and write back if it ships.

Replace the text in [brackets] before sending.

Templates

Logged for the roadmap

Email

Subject: Re: Idea for [Product]: [feature]

Hi [Customer name],

Thanks for taking the time to write this up. Being able to [feature, in their words] would clearly save you [the benefit they described].

I've added your request to our product board along with your use case. We look at these when planning, and the number of customers asking for something does move it up the list.

I can't give you a date, but I've linked your account to the request, so you'll hear from me directly if we build it.

[Agent name]

Not planned (an honest no)

Email

Subject: Re: Idea for [Product]: [feature]

Hi [Customer name],

Thanks for the suggestion. I talked it over with our product team, and I'd rather give you a clear answer than a vague "maybe": we're not planning to build [feature].

The short reason is [honest reason: it conflicts with how X works, it serves a small group of users, we're focusing on Y this year].

If what you're really after is [underlying goal], here's how other customers handle it today: [workaround, integration or API].

I know that's not the answer you hoped for. If your needs change or you have a different angle on this, I'm always happy to hear it.

[Agent name]

It shipped

Email

Subject: You asked for [feature], and it's here

Hi [Customer name],

Back in [month], you asked us for [feature]. It's live in [Product] as of today.

Here's how to try it: [one or two lines, or a link to the docs].

Your request was one of the ones that made the case for building it, so thank you. If it doesn't quite fit how you'd use it, I'd love to hear why.

[Agent name]

Tips

  • Ask what problem the feature would solve; the underlying need is often solvable today.
  • Record the request with the customer's account and use case, not just the feature name.
  • Say no when the answer is no; an honest no keeps trust better than a polite "we'll consider it" that never ends.
  • Keep a list of who asked for each feature so the launch email writes itself.

Avoid

  • "Great idea, we'll pass it on to the team" with no further follow-up.
  • Hinting at a release date the product team hasn't committed to.
  • Treating every request as a yes to avoid an awkward conversation.

Receive your first support ticket today.

Connect email or install the widget, invite your team, and start replying from one focused inbox.

  • 21-day free trial
  • Developer-friendly setup
  • Export your data anytime