Answer once. Everyone reads it.
Your users are already writing this down somewhere. Better it is a page you control, where the answer is public and the count is honest.
What claiming gets you
An official presence
A verified badge, your team name and a clear distinction between company responses and the independent public record.
One reply, read by everybody
Answer on the request itself instead of the same email forty times.
Statuses that mean something
Suggested, under review, planned, in progress, shipped. Everyone who voted is told when one moves.
Honest counts
Merge the duplicates and the number on the board becomes a number you can plan against.
A decline that lands well
A reason on the record beats silence, and it stops the same request coming back every quarter.
Plain analytics
Followers, requests, votes over time, and which requests are growing fastest.
How verification works
Pick your board
Find it in the list, or add your app if it is not there yet.
Prove the domain
Add a TXT record at your domain, or use a work email address at it. The DNS route survives people leaving.
You are in
The badge goes on the board, the dashboard opens, and you can reply.
What an answer looks like
A response sits above the community comments, signed with a name and a role, and the timeline underneath says where the request actually stands.
See a request with a response