Also, a feedback program usually generates way more feedback than the product team can/will act on, depending upon goals, scope and roadmap. 1) if someone proposes something the team is already working on, you can just accept it, don't need to disclose the WIP, makes everybody happy and 2) set expectations with your feedback status items, it's okay to have one for "this doesn't match our current roadmap or thinking." 3) great if you can attach people who vote on an idea to auto-magically be notified of status updates.
As you all have noted, for feedback that is implemented, being overly communicative on these to show that strong link between customers and product is gold. Tracking usage of those new features, or blocking issues that go away in support tickets, etc. are good validators.
