The second fork of the help dialog. A feature request is stored in the feature ledger with its own code, a title derived from your words, the canonical module, the screenshots you attached and the page it came from — the same queue surface the platform team works from.
Also called: feature request · suggest an improvement · idea box · wish list
- 1Same capture, same attachments, same annotation tools as a bug report
- 2The confirmation reads 'Request received — It's in the queue — you'll see it when it ships'
- 3A back link in the form lets you switch: 'Actually, I have a feature idea' / 'Actually, something's broken'
Feature requests filed from inside the app were accepted on screen and then quietly thrown away — the builder got a confirmation, the idea reached nobody, and it only came to light when someone asked why a suggestion they had made twice was never mentioned again. Ideas raised from the widget now land in the same ledger the team works from, with the same screenshots and the same record of which screen prompted them. The screen that made someone want the feature is usually the most useful part of the request.
- Ideas lost between a phone call and a to-do list
- Feature requests arriving without any context about the screen they're about
See it on your own jobs
Twenty minutes, your numbers, no slide deck. We’ll build one of your real buildings in front of you and send you the estimate link at the end — yours to keep either way.
or keep browsing features →