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.
Company 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.
Source and metric
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.
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.
Founder checklist
- Read Slack Developer Docs: Onboarding users to your app and identify what is directly supported.
- Choose one channel context: Onboarding, Conversion, Brand Trust.
- Define the test around Slack says only the installing user should receive the welcome DM, not the whole team..
- 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.