# Slack onboarding starts at the first invocation context

> Start onboarding from the first Slack surface the user actually touches, and vary the flow for App Home clicks versus slash-command intent instead of making every newcomer take the same route.

- Canonical HTML: https://growth.iangoh.com/growth-ideas/slack-onboarding-starts-at-the-first-invocation-context/
- 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, Product, Activation
- Stages: slack apps, activation, event-driven onboarding, user intent
- Key metric: Slack recommends designing around the key tasks a user should finish in the first 30 seconds.

## Why this can grow

A shared onboarding script usually hides the exact clue the user already gave you. Slack's onboarding guide explicitly says onboarding should start when the first meaningful event happens, such as `app_home_opened` or a slash command, and notes that those users should get different onboarding because the command user has already shown more expertise. That matters because good onboarding is less about introduction and more about preserving momentum. If someone typed a command, they are trying to get work done now. If someone clicked into App Home, they may still need the basic mental model.

## 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 onboarding starts at the first invocation context can create a measurable lift.
2. Turn the tactic into one offer, page, campaign, or workflow for the Onboarding and Product 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's onboarding guide says `app_home_opened` is a good trigger for onboarding, but says a slash-command user should start onboarding then and take a different path because that action shows a different level of expertise.

## Adjacent tactics in the same lane

- [Slack help path inside Slack before docs detour](/growth-ideas/slack-help-path-inside-slack-before-docs-detour/) - same source, 1 shared channel, 2 shared stages
- [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 channel introduction with current config state](/growth-ideas/slack-channel-introduction-with-current-config-state/) - 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 channel, 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.