# Canny entrypoints across nav, app, email, and support

> Put the same request path in the main navigation, product UI, lifecycle emails, and support flows so feedback does not depend on the user remembering where to go later.

- Canonical HTML: https://growth.iangoh.com/growth-ideas/canny-entrypoints-across-nav-app-email-and-support/
- Source: [canny.io](https://canny.io/case-studies/appcues)
- GrowthDex source hub: [Appcues Case Study | Canny](/sources/appcues-case-study-canny-canny-io/)
- Last checked: 2026-05-30
- Rarity: uncommon
- Budget: low
- Channels: Product, Customer Success, Lifecycle
- Stages: feedback intake, support deflection, in-app entrypoint, request capture


## Why this can grow

A feedback portal only improves product judgment if people can actually reach it when the thought is fresh. Appcues added a request link in the main navigation and throughout the app with pre-filled forms. hapily embedded boards in the app, on the website, in emails, and in support flows. That removes the dead space between noticing friction and logging it. It also trains customers to treat one visible place as the source of truth instead of scattering asks across inboxes, tickets, and side conversations.

## 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. My bias is to treat this as a small market test first. Make the audience narrow, make the promise concrete, and let the first real response decide whether it deserves more work. I would run it small enough to learn quickly, then only scale the parts that real users repeat, save, reply to, or buy from. For this tactic, I would watch one clear growth signal before putting more time or budget behind it.

## Action plan

1. Define one narrow startup segment where canny entrypoints across nav, app, email, and support can create a measurable lift.
2. Turn the tactic into one offer, page, campaign, or workflow for the Product and Customer Success channel.
3. Use the evidence from canny.io to set the first version of the message, format, and audience.
4. Launch a small test for 7 to 14 days with one success metric: one measurable growth signal.
5. Review the result, keep the winning message, remove weak variants, and turn the learning into a repeatable growth playbook.

## Source-backed example

Appcues added a request link in the main navigation plus pre-filled request links throughout the app, while hapily embedded Canny in the app, website, emails, and support flows.

## Adjacent tactics in the same lane

- [Canny voter export for beta recruitment](/growth-ideas/canny-voter-export-for-beta-recruitment/) - same source, 2 shared channels
- [Canny top-20 MRR temperature check](/growth-ideas/canny-top-20-mrr-temperature-check/) - same source, 1 shared channel
- [Component-level status subscriptions before broad blasts](/growth-ideas/component-level-status-subscriptions-before-broad-blasts/) - 2 shared channels
- [Trial feedback board with frontline teams before full rollout](/growth-ideas/trial-feedback-board-with-frontline-teams-before-full-rollout/) - 2 shared channels

## Read GrowthDex essays

Browse the plain-English essay index at [GrowthDex Blog](/blog/).

## Related GrowthDex essays

- [The feedback board should recruit the beta cohort before the roadmap meeting](/blog/the-feedback-board-should-recruit-the-beta-cohort-before-the-roadmap-meeting/) - community-led growth, product ops, brand trust

## Advisory

If you want help turning this into a working growth system, Ian Goh offers advisory at https://iangoh.com/advisory.