Feature Request Response Email Templates (Copy & Paste)

A good feature request reply turns a customer into a collaborator instead of a critic. These templates cover the full lifecycle — acknowledgment, already-on-roadmap, workaround offered, not planned, and shipped notification.

Template 1

Acknowledgment (logged)

Subject

Re: your idea for [feature name]

Body

Hi [First name],

Thanks for suggesting [feature / improvement]. I've logged it with our product team and tagged it with your account so we can follow up if it ships.

Can you share a bit more about your use case? Specifically:
• What workflow would this improve for you?
• How are you handling it today without this feature?

Your detail helps us prioritize. No promises on timing, but feedback like this directly shapes our roadmap.

Best,
[Your name]
[Product] Support

When to use

First reply to any feature request — always acknowledge and ask for use case detail before closing the ticket.

Template 2

Already on the roadmap

Subject

Good news — [feature] is on our roadmap

Body

Hi [First name],

Your request for [feature] aligns with something we're already building. It's on our roadmap for [quarter / timeframe if you can share it].

I can't share exact dates yet, but I've linked your account to this feature request so you'll be notified when it ships.

In the meantime, [workaround if one exists]. Let me know if that helps tide you over.

Best,
[Your name]
[Product] Support

When to use

The requested feature is genuinely planned — be honest about timing and offer a workaround if available.

Template 3

Workaround offered

Subject

Re: [feature request] — a way to do this today

Body

Hi [First name],

We don't have [feature] yet, but here's how customers achieve something similar today:

[Step-by-step workaround — be specific, link to docs if available]

It's not as smooth as a built-in feature, I know. I've still logged your request — if enough customers need this, it moves up the priority list.

Want me to walk you through the workaround on a quick call?

Best,
[Your name]
[Product] Support

When to use

Feature does not exist but a viable workaround does — solve their problem now while capturing the request.

Template 4

Not planned (respectful no)

Subject

Re: your request for [feature]

Body

Hi [First name],

Thanks for the suggestion. I've reviewed [feature request] with our team.

We're not planning to build this because [honest reason — e.g. "it serves a niche use case outside our core focus" or "our architecture doesn't support this approach"]. I know that's not the answer you wanted.

If your need changes or if [related feature we do have] would help instead, I'm happy to revisit. And if this is a dealbreaker for your account, let me know — I want to make sure you're on the right plan or product for your needs.

Best,
[Your name]
[Product] Support

When to use

Feature will not be built — be direct and honest. Customers respect clarity more than vague "we'll consider it" replies.

Template 5

Shipped notification

Subject

[Feature] is live in [Product] — you asked for this

Body

Hi [First name],

Remember when you asked for [feature] back in [month]? It's live now.

[One sentence on what it does]
[Link to docs or how to enable it]

You were one of the customers who pushed for this — thank you for the feedback. Reply if you hit any issues getting started.

Best,
[Your name]
[Product] Support

When to use

You shipped a feature customers requested — proactive outreach builds loyalty and reduces "does it do X?" support volume.

Template 6

Plan limit conversation

Subject

Re: hitting your [limit type] on [Product]

Body

Hi [First name],

I see you've reached your [conversation / seat / storage] limit on the [plan name] plan.

You have two options:
1. Upgrade to [next plan] at [price]/month — includes [limit increase + key benefit]
2. Stay on [current plan] — [explain what happens: e.g. "new conversations pause until next month, existing ones stay open"]

If you're hitting the limit regularly, [next plan] usually makes sense. Want me to switch you over?

Best,
[Your name]
[Product] Support

When to use

Customer hit a plan limit and implicitly needs a feature or capacity on a higher tier — common SaaS upsell moment tied to feature requests.

Get all 6 templates as a doc

Copy everything below into Notion or Google Docs — or enter your email and we'll send a formatted copy. Templates stay visible on this page either way.

Tag and track feedback from your inbox

Feature requests buried in email threads get lost. Userscom uses AI to sort tickets into tabs — route "Feature request" conversations automatically so product feedback never disappears into a general queue.

Try Userscom free

FAQ

Always acknowledge within one reply, log the request with the customer's use case attached, and give an honest status: on roadmap, workaround available, or not planned. Never say "we'll consider it" without meaning it — customers remember and lose trust when nothing happens.

Yes — proactively email customers who requested a feature when it launches. It takes five minutes per customer and generates disproportionate goodwill, case studies, and retention.

Explain why briefly (focus, architecture, niche use case), offer an alternative if one exists, and invite them to tell you if it is a dealbreaker. Customers who feel heard and get an honest answer rarely churn over a single missing feature.

More SaaS support templates

Refund requests

Approve, decline, or offer a downgrade when a customer asks for their money back.

5 templates →

Churn save

Respond when a customer cancels, mentions a competitor, or says they are not getting value.

5 templates →

Failed payment dunning

Recover failed charges with a sequence that sounds human, not like a collections agency.

5 templates →

Angry customer responses

De-escalate frustrated customers without sounding robotic or defensive.

5 templates →

Support cost calculator

Compare Intercom, Zendesk, Crisp & Userscom annual costs.

Free tool →

Feature Request Response Email Templates (Copy & Paste)

Template 1

Acknowledgment (logged)

Subject

Re: your idea for [feature name]

Body

Hi [First name],

Thanks for suggesting [feature / improvement]. I've logged it with our product team and tagged it with your account so we can follow up if it ships.

Can you share a bit more about your use case? Specifically:
• What workflow would this improve for you?
• How are you handling it today without this feature?

Your detail helps us prioritize. No promises on timing, but feedback like this directly shapes our roadmap.

Best,
[Your name]
[Product] Support

When to use

First reply to any feature request — always acknowledge and ask for use case detail before closing the ticket.

Template 2

Already on the roadmap

Subject

Good news — [feature] is on our roadmap

Body

Hi [First name],

Your request for [feature] aligns with something we're already building. It's on our roadmap for [quarter / timeframe if you can share it].

I can't share exact dates yet, but I've linked your account to this feature request so you'll be notified when it ships.

In the meantime, [workaround if one exists]. Let me know if that helps tide you over.

Best,
[Your name]
[Product] Support

When to use

The requested feature is genuinely planned — be honest about timing and offer a workaround if available.

Template 3

Workaround offered

Subject

Re: [feature request] — a way to do this today

Body

Hi [First name],

We don't have [feature] yet, but here's how customers achieve something similar today:

[Step-by-step workaround — be specific, link to docs if available]

It's not as smooth as a built-in feature, I know. I've still logged your request — if enough customers need this, it moves up the priority list.

Want me to walk you through the workaround on a quick call?

Best,
[Your name]
[Product] Support

When to use

Feature does not exist but a viable workaround does — solve their problem now while capturing the request.

Template 4

Not planned (respectful no)

Subject

Re: your request for [feature]

Body

Hi [First name],

Thanks for the suggestion. I've reviewed [feature request] with our team.

We're not planning to build this because [honest reason — e.g. "it serves a niche use case outside our core focus" or "our architecture doesn't support this approach"]. I know that's not the answer you wanted.

If your need changes or if [related feature we do have] would help instead, I'm happy to revisit. And if this is a dealbreaker for your account, let me know — I want to make sure you're on the right plan or product for your needs.

Best,
[Your name]
[Product] Support

When to use

Feature will not be built — be direct and honest. Customers respect clarity more than vague "we'll consider it" replies.

Template 5

Shipped notification

Subject

[Feature] is live in [Product] — you asked for this

Body

Hi [First name],

Remember when you asked for [feature] back in [month]? It's live now.

[One sentence on what it does]
[Link to docs or how to enable it]

You were one of the customers who pushed for this — thank you for the feedback. Reply if you hit any issues getting started.

Best,
[Your name]
[Product] Support

When to use

You shipped a feature customers requested — proactive outreach builds loyalty and reduces "does it do X?" support volume.

Template 6

Plan limit conversation

Subject

Re: hitting your [limit type] on [Product]

Body

Hi [First name],

I see you've reached your [conversation / seat / storage] limit on the [plan name] plan.

You have two options:
1. Upgrade to [next plan] at [price]/month — includes [limit increase + key benefit]
2. Stay on [current plan] — [explain what happens: e.g. "new conversations pause until next month, existing ones stay open"]

If you're hitting the limit regularly, [next plan] usually makes sense. Want me to switch you over?

Best,
[Your name]
[Product] Support

When to use

Customer hit a plan limit and implicitly needs a feature or capacity on a higher tier — common SaaS upsell moment tied to feature requests.

Get all 6 templates as a doc

Copy everything below into Notion or Google Docs — or enter your email and we'll send a formatted copy. Templates stay visible on this page either way.

Tag and track feedback from your inbox

Try Userscom free

FAQ

Yes — proactively email customers who requested a feature when it launches. It takes five minutes per customer and generates disproportionate goodwill, case studies, and retention.

More SaaS support templates

Refund requests

Approve, decline, or offer a downgrade when a customer asks for their money back.

5 templates →

Churn save

Respond when a customer cancels, mentions a competitor, or says they are not getting value.

5 templates →

Failed payment dunning

Recover failed charges with a sequence that sounds human, not like a collections agency.

5 templates →

Angry customer responses

De-escalate frustrated customers without sounding robotic or defensive.

5 templates →

Support cost calculator

Compare Intercom, Zendesk, Crisp & Userscom annual costs.

Free tool →