Custom welcome message with Discobot handoff
Send every newcomer a community-specific welcome note from a real person, then hand them to Discobot for the mechanical tutorial.
Why this can grow a startup
New members often need two different kinds of help on day one. They need emotional orientation about what this community is for, and they need procedural orientation about how to use the software. The Discourse onboarding thread makes that split explicit. A custom private message can reassure the member, point to the right documents, and invite the right first post, while Discobot handles the generic product tutorial. That keeps the welcome flow human without forcing moderators to manually reteach the interface every time.
Source-backed example
In a 2026 Discourse Meta onboarding discussion, admins described pairing a custom welcome message with key pointers, links, and an invitation to the welcome zone while still telling members how to trigger the Discobot tutorial for the platform basics.
Source-reported evidence
Source: Discourse Meta: Onboarding: Discobot, automated messages, other options?
The Discourse thread notes two built-in Discobot onboarding texts plus the option to send custom automated messages from a chosen sender so replies land with a real owner.
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.
Source discovered: May 30, 2026
When to use it
Use this when Community, Lifecycle Messaging, Support is relevant to community onboarding, activation, welcome flow 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 Community and Lifecycle Messaging, using evidence from Discourse Meta: Onboarding: Discobot, automated messages, other options? as context—not as a promised result.
- Record a baseline for: Share of target users completing the product's first-value 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
Connect activation, customer value, retention, and referral into one measurable loop.