Guide
How to write a good feature request
Five things that turn a good idea into something we can act on. It takes two minutes and gets your request prioritized faster.
- 1
Start with the problem, not the button
Tell us what you're trying to get done and where it falls apart. A request that names the outcome gives us room to find the best fix, which is often simpler than the one you had in mind.
"After a demo I want to leave the customer something they can forward internally. Right now I screenshot each page, which takes 20 minutes and looks rough."
- 2
Say who it affects and how often
Is this every rep on every call, or one team once a quarter? Frequency and reach are most of what decides priority, so give us your honest read.
"All 14 of our field reps hit this after roughly half their meetings."
- 3
Describe the workaround you use today
What you do instead tells us how painful the gap really is and sometimes points at a quick win.
"We export to PowerPoint, then print that to PDF, then re-upload it to our CRM."
- 4
Tell us what success looks like
One sentence on how you'd know it was solved. Skip the implementation details unless they matter to you.
"A Share as PDF option on the presentation that includes every page and the current branding."
- 5
Add a screenshot or a short video
A picture of where you got stuck saves a round of questions. Videos under a minute are perfect.
Attach the screen where you expected the option to be.
What happens next
Every request gets a status. Under Review means we've seen it. Planned and In Progress mean it's on the roadmap. Shipped means it's live. Declined means we won't build it and we'll say why. Duplicates get merged so votes add up in one place.
Write Your Request