# Slack help path inside Slack before docs detour

> Keep the first help path inside Slack with a help action, DM fallback, or `@mention` response before you send the user to external docs.

- Canonical HTML: https://growth.iangoh.com/growth-ideas/slack-help-path-inside-slack-before-docs-detour/
- Source: [docs.slack.dev](https://docs.slack.dev/app-management/onboarding-users-to-your-app)
- GrowthDex source hub: [Slack Developer Docs: Onboarding users to your app](/sources/slack-developer-docs-onboarding-users-to-your-app-docs-slack-dev/)
- Last checked: 2026-06-09T01:09:48.000Z
- Rarity: rare
- Budget: low
- Channels: Onboarding, Support, Retention
- Stages: slack apps, help UX, support deflection, activation


## Why this can grow

People ask for help at the point of confusion, not at the point where the docs IA makes sense. Slack's guide says command-heavy apps should offer a help action like `/myapp help`, conversational apps should answer in the app DM when the user asks for help or says something unclear, and `@mentions` are another good time to surface help fast. That is useful growth discipline because it keeps the user in the workflow they were already trying to complete. A docs link can still exist, but it should not be the first thing standing between confusion and progress.

## 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. For activation, the useful question is not whether users liked the page. It is whether they got to the first meaningful win faster. 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 slack help path inside slack before docs detour can create a measurable lift.
2. Turn the tactic into one offer, page, campaign, or workflow for the Onboarding and Support channel.
3. Use the evidence from docs.slack.dev 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

Slack recommends a help action for slash-command apps, DM-based assistance for conversational apps, and a helpful response when the app is `@mentioned`.

## Adjacent tactics in the same lane

- [Slack onboarding starts at the first invocation context](/growth-ideas/slack-onboarding-starts-at-the-first-invocation-context/) - same source, 1 shared channel, 2 shared stages
- [Slack channel introduction with current config state](/growth-ideas/slack-channel-introduction-with-current-config-state/) - same source, 2 shared channels, 1 shared stage
- [Slack welcome DM with one clear setup action](/growth-ideas/slack-welcome-dm-with-one-clear-setup-action/) - same source, 1 shared channel, 1 shared stage
- [Slack app suggestions from shared domain links](/growth-ideas/slack-app-suggestions-from-shared-domain-links/) - same source, 1 shared stage

## Read GrowthDex essays

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

## Related GrowthDex essays

- [The Slack app should start helping before the docs tab opens](/blog/the-slack-app-should-start-helping-before-the-docs-tab-opens/) - onboarding, product-led growth, brand trust

## Advisory

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