Finding it
Open Settings and choose Request A Feature.Submitting a request
1
Choose Submit A Request
From the feature requests list.
2
Give it a short title
This is what everyone else sees in the list, and what they decide to vote on. “Export leads to CSV” beats “improvement to the leads screen”.
3
Describe what you need
Say what you’re trying to do and why the current app makes it hard. The problem is more useful to us than a proposed solution — there’s often a better fix than the one you’d have asked for.
Voting
Every request shows its upvote count and who submitted it. Tap the upvote to add your vote, and tap it again to take it back if you change your mind. Vote for anything you’d genuinely use. There’s no limit and no cost to you, and an honest vote is what makes the ranking worth reading.Where a request stands
Each request carries a status, so you can see whether anything happened to it:Pending is not a rejection. It’s the default state, and a request can sit there for a long time while still being read. A high vote count on a pending request is exactly the thing that moves it.
What makes a request likely to get built
Describe the situation, not just the feature
Describe the situation, not just the feature
“I need this at trade shows, where I capture forty leads in a day and have no signal” tells us far more than “add bulk edit”. The constraint is usually the part that changes the design.
One request, one idea
One request, one idea
A request bundling five things can’t be voted on coherently — people who want the third item have to vote for the other four. Split them.
Say what you do today instead
Say what you do today instead
The workaround you’ve built tells us how bad the gap really is. If you’re exporting to a spreadsheet every evening, say so.
Small and specific beats big and vague
Small and specific beats big and vague
“Remember my last-used meeting type” is a request we can act on. “Make meetings better” isn’t, however strongly you mean it.
