# Slack welcome DM with one clear setup action

> Send the installer one concise welcome DM with a single setup action, because Slack warns that broad surprise messages create uninstall risk.

- Canonical HTML: https://growth.iangoh.com/growth-ideas/slack-welcome-dm-with-one-clear-setup-action/
- 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: uncommon
- Budget: free
- Channels: Onboarding, Conversion, Brand Trust
- Stages: slack apps, welcome message, setup, trust


## Why this can grow

A lot of Slack apps confuse presence with progress. They greet everyone, explain everything, and leave the installer with five next steps. Slack's guide is more disciplined. It says the welcome message should be concise, explain what the app does, and make the call to action clear, while also warning teams not to DM the entire workspace because unexpected messages can prompt uninstalls. That gives the team a better rule: help the installer finish the first necessary setup step and earn the right to explain more later.

## 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 slack welcome dm with one clear setup action can create a measurable lift.
2. Turn the tactic into one offer, page, campaign, or workflow for the Onboarding and Conversion 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 DMing only the installing user with a concise welcome message, a clear call to action, and explicit instructions, while avoiding unexpected team-wide DMs.

## Adjacent tactics in the same lane

- [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 onboarding starts at the first invocation context](/growth-ideas/slack-onboarding-starts-at-the-first-invocation-context/) - same source, 1 shared channel, 1 shared stage
- [Slack help path inside Slack before docs detour](/growth-ideas/slack-help-path-inside-slack-before-docs-detour/) - 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.