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.
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-reported evidence
Source: Canny Help Center · Browse Canny Help Center tactics
A public admin comment emails the post author and all voters, while a direct reply only emails the addressed user.
Attributed to the cited source; GrowthDex has not independently verified it. Use this as context, not as a forecast, benchmark, or recommended target.
Evidence scope: claims and metrics are attributed to the linked source; GrowthDex has not independently replicated the reported result. Check the original context and validate fit before applying it. Read the evidence methodology.
Source discovered: May 28, 2026
When to use it
Use this when Email, Support, Product is relevant to close-the-loop, lifecycle, roadmap trust and you can run a bounded test with a free budget.
When not to use it
Do not use it as a substitute for customer evidence, a clear owner, or a measurable stop condition. Local platform rules and market behavior still need checking.
How to do it
- Choose one target segment and define the exact next action this tactic should prompt.
- Adapt the tactic to Email and Support, using evidence from Canny Help Center as context—not as a promised result.
- Record a baseline for: Share of the target cohort repeating the core action within the chosen period. Set a guardrail that would make you pause the test.
- Run a narrow pilot and choose a test window that fits the normal decision or use cycle; do not scale before you have observed the full cycle.
- Compare the signal with its baseline. Scale only if the intended action improves without crossing the guardrail; otherwise revise one variable or stop and record what you learned.
Compare a stack for your situation
Compare source-backed tactics against your product, stage, budget and channel strengths, then choose one experiment to test.
Explore the context
Did you launch this experiment?
Report a launch to help us understand which growth ideas founders put into practice.
Apply this with an operator
Connect activation, customer value, retention, and referral into one measurable loop.
SOURCE HUB
More tactics from Canny Help Center
Explore related GrowthDex examples and evidence connected to Canny Help Center.
Open Canny Help Center source hub