How to write an effective post and Product Feedback Guidelines

Welcome to the Product Suggestions Topic!

We strongly value your feedback, and would love to hear how you use our product, and how we can make it better.

Here are a few guidelines on how to use the Product Suggestions Community, so that our support team can effectively use and apply your feedback:

Guidelines

Feedback and constructive criticism are welcome. Disparaging, harassing, mean, or snarky remarks about UserIQ, its employees, vendors, partners, or other community members will not be tolerated. We reserve the right to remove comments in order to keep the community a positive experience for everyone.

If it's a bug, create a ticket

This topic is for sharing ideas about the product. If you're reporting an actual bug, that should go into a ticket so that it can get routed to the appropriate engineering team. 

Vote for suggestions you like

Votes do matter! See a post or comment you like or agree with? Please use the up arrow! Feel like making a post that just says "+1"? Please use votes instead. Post a comment to share your detailed use case.

Give details, examples, and tell us about the problem you’re trying to solve

The most helpful Product Feedback posts are the ones that describe the nature and scope of a problem. Try to answer these questions in your post or comment: 

• What is the problem?
• Why is it a problem?
• How do you solve the problem today?
• How would you ideally solve the problem?
• How big is the problem (business impact, frequency of impact, who is impacted)

It's much easier for us to address a suggestion if we clearly understand the context of the issue, the problem, and why it matters to you.

We don’t share timelines

Occasionally, we’ll share very general ideas of what is or isn’t on a roadmap, or roughly when you might expect to see something roll out. However, we do not share specifics, and often can’t tell you exactly what’s on the roadmap. Any timelines we share are not guaranteed and are subject to change without notice. 

There are situations where we aren't ready to share what we're up to or it's not reasonable for us to give specifics. While we are as up front as we can be, our roadmap is full of projects and we generally don’t provide timelines for new features or changes. If we do provide a timeline, know that it is subject to change.