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.
Why this can grow a startup
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.
Source guidance
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.
Source-reported evidence
Source: Slack Developer Docs: Onboarding users to your app · Browse Slack Developer Docs: Onboarding users to your app tactics
Slack says only the installing user should receive the welcome DM, not the whole team.
Attributed to the cited source; GrowthDex has not independently verified it. Use this as context, not as a forecast, benchmark, or recommended target.
Evidence scope: claims and metrics are attributed to the linked source; GrowthDex has not independently replicated the reported result. Check the original context and validate fit before applying it. Read the evidence methodology.
When to use it
Use this when Onboarding, Conversion, Brand Trust is relevant to slack apps, welcome message, setup and you can run a bounded test with a free 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.
How to do it
- Choose one target segment and define the exact next action this tactic should prompt.
- Adapt the tactic to Onboarding and Conversion, using evidence from Slack Developer Docs: Onboarding users to your app as context—not as a promised result.
- Record a baseline for: Target users who complete the tactic’s intended next action. Set a guardrail that would make you pause the test.
- Run a narrow pilot and choose a test window that fits the normal decision or use cycle; do not scale before you have observed the full cycle.
- Compare the signal with its baseline. Scale only if the intended action improves without crossing the guardrail; otherwise revise one variable or stop and record what you learned.
Compare a stack for your situation
Compare source-backed tactics against your product, stage, budget and channel strengths, then choose one experiment to test.
Explore the context
Did you launch this experiment?
Report a launch to help us understand which growth ideas founders put into practice.
Apply this with an operator
Choose product surfaces that compound distribution without hiding weak activation or retention.
SOURCE HUB
More tactics from Slack Developer Docs: Onboarding users to your app
Explore related GrowthDex examples and evidence connected to Slack Developer Docs: Onboarding users to your app.
Open Slack Developer Docs: Onboarding users to your app source hub