The sibling of the bug-fix notice, following the same house rules: only the requester hears about it, the platform sends it, and the message plus its delivery outcome are stored. The email carries an 'Open it in the app' button that resolves to an explicit link, else the page the request was filed from, else the app root.
Also called: feature request follow up · did they build it · roadmap update · you asked we built
- 1The ship protocol marks the feature shipped and then calls the notify route with the feature code
- 2The route renders and sends the email through the platform sender and records the outcome
- 3The deep link resolves: explicit link → the page the request was filed from → the app root
- 4The route is fail-closed: with no shared token configured it returns 503 rather than running open
By the time a requested feature is built, the person who asked has usually forgotten the details, so 'your feature shipped' reads as noise and the work gets paid for twice — once to build it, and again as a support call three months later from the man who asked for it. The email now quotes the original request back, explains how the shipped version works, says where it lives, and carries a button that opens it on the right screen. Only the requester hears about it, and staff are not emailed about their own work.
- Requests vanish into a backlog with no feedback loop
- Shipped features go unused because the person who wanted them is not told
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 →