Skip to main content

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

For app and game developers

How to reply to feature requests from players

Players who send ideas care about your game. Thank them for something specific, tell them where the idea goes, and be honest when it isn't going to happen.

Replace the text in [brackets] before sending.

Templates

Logged for the dev team

Email

Subject: Re: Suggestion for [Game]: [idea]

Hi [Player name],

Thanks for the suggestion! [Idea in their words] would add [the benefit they mentioned or one you can see], and I can tell you've put real hours into the game.

I've added it to the list our designers go through when planning updates, along with your description. I can't promise if or when it will appear, since every idea competes with a lot of others, but it will be read.

Keep an eye on [patch notes / Discord / news channel]; that's where we announce what's coming.

[Agent name]

Not planned

Email

Subject: Re: Suggestion for [Game]: [idea]

Hi [Player name],

Thanks for sending this. I shared it with the team, and I want to be honest rather than leave you waiting: we're not planning to add [idea].

The main reason is [honest reason: it would change the balance of (mode), it doesn't fit the direction of the game, it's not possible on all platforms].

I know that's a letdown. If there's a related problem you're trying to solve, such as [underlying need], tell me more about it; that kind of feedback does shape what we build.

[Agent name]

Chat: quick thanks

Chat

That's a fun idea, thanks for sharing! I've passed it to our design team with your description. We announce upcoming changes in [patch notes / Discord], so keep an eye there.

Tips

  • Repeat the idea back in one line to show it was understood.
  • Point players to the public place where you announce updates, so they don't need to keep asking support.
  • Tag suggestions by theme; the most requested themes are useful input for the next roadmap.
  • Give a reason when you say no; players accept "it would break ranked balance" far better than a flat no.

Avoid

  • "We'll pass it on" with no hint of what happens next.
  • Teasing unannounced features to soften a no.
  • Promising an idea will make it into the next update.

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