Submitting a feature request

A short guide for customers on how to file a useful feature request on a ProductLift portal.

Before you post

Search first to keep requests about the same need together. If your idea already exists, vote and comment instead of creating a new post.

How to post

  1. Click New post (or the equivalent button on the portal).
  2. Pick the relevant board if there's more than one.
  3. Write a clear title that names the outcome you want. Examples:
    • Good: "Dark mode for the dashboard"
    • Less useful: "It's too bright"
  4. In the description, tell us:
    • What you want.
    • Why you want it. (The use case is what helps the team prioritize.)
    • What you're doing today as a workaround.
  5. Add screenshots or files if they help (drag and drop into the description).
  6. Fill in the category or other fields the form asks for.
  7. Submit.

Give the team enough context

  • Specific use case. "We're a 10-person agency and we need X to do Y" beats "please add X".
  • Frequency. Mention how often this comes up for you.
  • Workaround pain. What does the current workaround cost you in time / money / errors?
  • Customer voice (not just feature voice). The team builds for customer outcomes, not feature lists.

After you submit

  • Updates depend on your notification preferences and the team's sending choices.
  • Other customers can vote and comment on your post, share the link if it'll help build support.
  • An admin may move your post to a different board, edit the title for clarity, or merge it with a duplicate. This isn't a rejection, it's curation.

If your post gets declined

A declined post means the team has decided not to build it. Usually there's an explanation in the comments, read it. If the reasoning doesn't fit your case, leave a comment with the missing context. Declines can be reopened.