Hi, how can we help you today?

This knowledge base will guide you through all the necessary steps to help shape the future of our product.

Feature Request FAQ

1. How do I know if my idea is a "Feature Request" or a "Bug"?

A Feature Request is a request for new functionality or an improvement to something that is already working as designed. A Bug is when an existing feature is broken, crashing, or not performing the way it was intended.

Note: If you are experiencing a technical error that prevents you from working, please contact our Support Team directly for immediate assistance rather than posting it as an idea.


2. What happens right after I submit an idea?

Every submission goes through a three-step initial review:

  1. Moderation: We check for duplicates and ensure the post is clear.

  2. Categorization: We tag it by product area (e.g., "Mobile App," "API," "Billing").

  3. Community Phase: The idea goes live for other users to see, vote on, and discuss.


3. How do you decide which features to build?

We don’t just look at the number of votes. We use a balanced scoring system to ensure we are building the right things for the right reasons. We look at:

  • Customer Value: How much time or effort will this save you?

  • Reach: How many of our total users will benefit from this?

  • Effort: How long will it take our engineers to build and maintain?

  • Strategic Alignment: Does this help us reach our long-term goals as a company?


4. Why hasn't my high-vote idea been built yet?

We understand it can be frustrating to see a popular idea sitting in "Planned" or "Under Review." Usually, this is due to Technical Dependencies.

For example, we might want to build "Feature X," but we first need to rebuild our database architecture to support it. We aim to keep you updated on these "under the hood" projects through our status updates.


5. Can I edit my request after I’ve posted it?

Yes! If you find a better way to explain your idea or want to add a screenshot, you can edit your post at any time. We actually encourage this—the clearer the request, the easier it is for our team to evaluate.


6. Will I get credit if you build my idea?

Absolutely. When an idea moves to Completed, the original author is highlighted. We often reach out to top contributors for exclusive "First Look" demos and beta testing opportunities as a thank you for helping us grow.


7. What does it mean when an idea is "Closed" or "Declined"?

If we mark an idea as "Not at This Time," it doesn't mean it was a bad idea. It usually means:

  • It conflicts with the core simplicity of our product.

  • The technical cost is too high compared to the benefit.

  • It is a very niche request that only applies to a tiny fraction of users.

We will always leave a comment explaining exactly why we reached that decision.


8. How many votes can I cast?

To ensure the roadmap reflects what users truly need, we sometimes limit the number of Active Votes per user. This encourages you to put your weight behind your "must-have" features rather than "nice-to-haves." Once a feature you voted for is released, you get that vote back!