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.
Why this can grow a startup
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.
Company 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`.
Source and metric
Source: Slack Developer Docs: Onboarding users to your app · Browse Slack Developer Docs: Onboarding users to your app tactics
Slack calls out help entry points for slash commands, DMs, and `app_mention` events.
When to use it
Use this when Onboarding, Support, Retention is relevant to slack apps, help UX, support deflection and you can run a bounded test with a low 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.
Founder checklist
- Read Slack Developer Docs: Onboarding users to your app and identify what is directly supported.
- Choose one channel context: Onboarding, Support, Retention.
- Define the test around Slack calls out help entry points for slash commands, DMs, and `app_mention` events..
- Set an owner, evidence window, and stop condition before launch.
Explore the context
Apply this with an operator
Choose product surfaces that compound distribution without hiding weak activation or retention.