Growth idea action plan
Public comment update emails every voter
Use a public admin comment to update everyone who voted on a request instead of leaving the post silent between status changes.
Why this can grow a startup
Most request boards break the loop in the quiet middle. The team has not changed the status yet, but it has learned something useful and never tells the people waiting. Canny treats a public admin comment as a distribution event: the post author and all voters get the update by email. That turns one comment into lightweight lifecycle messaging and keeps the request thread alive without forcing the team to write a separate announcement somewhere else.
Ian's take
From scaling consumer platforms across MENA and Southeast Asia, my default is to distrust growth work that only looks good in a slide. Email still works when it reads like one person noticed one real thing. If the message could be sent to anyone, it usually works on nobody. I would make the first line specific enough that the right reader knows it was meant for them. For retention, I would watch the second and third use, not just the first click. A tactic is real when it changes a habit. For this tactic, I would watch one clear growth signal before putting more time or budget behind it.
Action plan
- Define one narrow startup segment where public comment update emails every voter can create a measurable lift.
- Turn the tactic into one offer, page, campaign, or workflow for the Email and Support channel.
- Use the evidence from help.canny.io to set the first version of the message, format, and audience.
- Launch a small test for 7 to 14 days with one success metric: one measurable growth signal.
- Review the result, keep the winning message, remove weak variants, and turn the learning into a repeatable growth playbook.
Source-backed example
Canny's comments system emails the post author and all voters when an admin leaves a public comment on a post, while direct replies notify only the person being answered.
Source: Canny Help Center (help.canny.io)
GrowthDex source hub: Canny Help Center
Last checked: 2026-05-28
Adjacent tactics in the same lane
If this page is close to your problem, these tactic pages usually belong in the same working set.
- Public ETA on roadmap only when ready same source · 1 shared channel · 2 shared stages
- Status-change-sorted public roadmap same source · 1 shared channel · 2 shared stages
- Feedback capture from any webpage with source URL same source · 2 shared channels
- Custom instructions for feedback auto-replies 3 shared channels · 2 shared stages
Related GrowthDex essays
- The feedback board should keep getting sharper after the vote product feedback, roadmap trust, customer operations
Read GrowthDex essays
The Blog turns real growth tactics into plain-English case studies by niche, channel, and buying situation.
Why this is worth your time
GrowthDex starts with tactics that founders, marketers, and product teams have actually tried. Each essay turns the evidence into a practical move you can test without pretending one case study is a guarantee.
Ian Goh has helped grow consumer platforms across Southeast Asia, India, and MENA. His work includes scaling Tiki to 100M+ users, doubling BIGO's MENA revenue in 7 months, and increasing OYO's direct booking share across 6 Southeast Asian markets.
- Helped scale Tiki to 100M+ users.
- Doubled BIGO's MENA revenue in 7 months.
- Raised OYO's direct booking share by 50% across 6 Southeast Asian markets.
Want help turning this into a growth system?
If you want someone to pressure-test this against your real market, Ian works with founders on growth, market entry, and operator-led distribution.
Work with Ian on growth advisory