Feature Request Form

Feature requests arrive as solutions, and building exactly what was asked for is how products get bloated. The help text on the problem field asks explicitly for the situation rather than the feature, because the situation is what you can design against and often has a better answer than the one requested.

Asking how the person handles it today is the highest value question here. An expensive workaround proves the problem is real, and no workaround at all usually means the need is theoretical, and that distinction sorts a backlog faster than any voting system.

The importance scale tops out at I would switch tools for it, which gives you a usable signal about retention risk rather than a general enthusiasm score. Keep the plan field hidden so you can weight requests, and collect the email so you can close the loop when something ships.