Product Feedback Policy

Our approach to product feedback

Here at Mango, we take product feedback extremely seriously. It's helped make what Mango is today. We've always considered it a crucial part of our journey towards building a better product, and we've used your feedback to identify the most important features, ideas, pain points, and opportunities so that you can get more value from Mango as efficiently as possible.

Our feedback portal to provide an easy way to suggest ideas, track and keep informed of the progress of your ideas, as well as vote on suggestions made by other Mango users. It's a one-stop shop where we communicate what's coming for Mango, and we want all of our users to be a part of it.

What happens to your product feedback

All new requests are set to the "Awaiting Feedback" status so that more people can vote, prioritise and give us information. This allows us to gauge demand, gather use cases, and establish impact and value throughout the user base.

Our Product Teams hold regular feedback meetings to discuss the highest priorities for our customers, team members and prospects, and look at how the requests align with our own strategy. Only the highest priorities will be discussed at each meeting. If an idea hasn't received a lot of support or discussion, it will be left Awaiting Feedback for future consideration. As the team goes through each suggestion, they will update the status of the requests so that you immediately know the outcome. 

If we decide to build a feature or make an improvement, the status will change to "Planned". Anyone who has submitted or voted on a specific request will be notified when the status of the request is updated. Planned ideas will be added to our product roadmap which you can view at any time from your Feedback dashboard.

Our product feedback portal always has the most up-to-date information about our products and what we are building next, but the order of planned features in our roadmap does not necessarily indicate the order in which features will be released and is subject to change at any time.

If you reach out directly to our Support or Customer Success teams for an update, they'll be able to look up your suggestion for you, but they won't have any additional information or provide an estimate for when your request will be reviewed.

FAQs

What do the statuses mean?

What happens if my idea is rejected?

As much as we'd like to build a product that serves all our users, there will be features we won't (or can't) build. While a suggestion might be great, it may not be viable, or it may not align with the internal vision we have for Mango. In these cases, a suggestion will be marked as Declined. We'll provide a clear explanation of why we've chosen to decline a suggestion, which will be public and available to all users.

How long will it be before the product team reviews my idea?

Items will be reviewed by our product specialists on a weekly basis; we take the top requests and update the status where appropriate. Feedback meetings occur at least once per month. Make sure your ideas are clear and concise so others can vote on it & prioritise. Also be sure to prioritise your own requests too - that way, we will know if a particular request is important to you.

How long will it be before you build my idea?

Good software need to be planned well, built well, and thoroughly tested. The time if might take for each individual idea to go from suggestion to released may vary greatly, depending on the scope, complexity, impact and demand.

If a suggestion that has garnered a lot of support, and feedback and aligns with our vision for Mango, it may be selected for development at a Product Team meeting. The time it may take to pass through planning and design, to development, to rigorous testing and ready for release can only be estimated on a case by case basis.

When a request enters Building stage, we'll do our best to communicate in which future quarter the feature may become available.

If a suggestion garners little attention, it is unlikely it will be considered for development, unless it aligns closely with our internal trajectory and vision for Mango.

I asked for X but you built Y

Every suggestion we choose to build has to be considered alongside our internal vision for Mango, and balanced with technology needs, performance, and for use by a broad swathe of users. In planning, we may find that the suggestion was a starting point for us to build something that achieved X but also allowed Y. Ensuring the core pain point that your suggestion solves will help us to ensure that the end product does X even better than you might have imagined.

My request hasn't been reviewed yet and I submitted it 6 months ago. What can I do?

If we haven't reviewed your suggestion yet and it is a high priority for you:

• Make sure it's at the top of your priority list

• Make sure your request is clear. Why do you need this? What is it stopping you from doing? What is the impact of that? Please add these details in a comment on your idea.

Thank you for your feedback, understanding, and support as we work together to improve Mango!