Custom saved responses Setup

When you update a feature's status (to Planned, Released, etc), by default you have several pre-populated options to explain the transition.

See additional response ideas below

You can also create your own custom saved responses. There are two ways to do this:

1. Under your account settings

2. When updating the status of a feature

1. Create / edit custom saved replies in your account settings

Click the icon in the top right hand corner and select "Settings".


Select "Custom responses" from the list on the right-hand side. Then click "Manage custom responses":


Click "Create", select the status for the new custom saved reply and hit "Save":


To edit any saved response, just click "Edit" next to the saved response:


And update your response:


2. Create a new custom saved reply when updating the status of a feature

When changing the status of a feature, just check the box "Save response for future use" and the response will be added to your custom saved reply list:


Pre-populated Responses

We have pre-populated responses in place if you don't want to create your own. You can access these using the "Saved response" drop-down menu when you change the status of a feature.

The pre-populated responses are listed below.

Awaiting Feedback:

"We're gathering feedback from customers, so that we can gauge demand for this feature. Make sure to click "Want" on this feature if you need it."


"Coming soon! this is a high priority for the team here!"
"This is on our roadmap now, we can't give a definite date for release, but it's coming."


"We are building this as we speak."
"We've started on this feature, we'll let you know when it's released."
"Our development team are hard at work on this feature right now, check back soon for an update."


"Released now. Thanks for all your interest in this feature, your feedback helps us to build a better product."
"This has been built, and should be available in our next release, which is scheduled for [DATE OF RELEASE]."


"We appreciate every suggestion. Right now this doesn't fit with our strategy but it may do in the future."
"Out of scope, we just don't think that this is somewhere that we're taking our product."
"We don't think there's enough demand from our customers, and we've got to focus on where we can help the most customers."
"Duplicate, I'm declining this as we've got this covered in another feature request: [LINK TO REQUEST]." 

More response ideas

Awaiting feedback:

"Thanks for this suggestion! We regularly review all suggestions received and work on the ones which our users find most valuable. If we release any features you have personally requested or voted on, we will e-mail you to let you know when it has been released. Thank you very much!"
"Thanks, this is a great idea! We'll leave this in Awaiting Feedback while we see what other customers think. If this turns out to have high demand, we'll investigate further."


"This work hasn't been scheduled yet, but it's on our project list for next year."


"Our development team is hard at work on this feature right now. You can check back soon for an update!"


"I think we're going to stick with the current status stages for the foreseeable. I can see a potential customization of the stages, but if we do that it would probably be best to have them completely configurable. We have to balance that against it being simple to explain and manage our product, too."
"Good news! You can already do this. Just go to... We'll close this one off, if you have any questions, reply to this message."
"What we suggest is.... As there would be a large amount of coding work to accomplish something with a simple workaround we're going to turn this one down. If you have any questions, reply to this message."
"Thank you for your feedback. As explained in the comments, I will close this suggestion because what you want is already possible."


See how we say no to requests at Receptive.


Any questions? Email or use the form here


Have more questions? Submit a request


Please sign in to leave a comment.