# 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.

- Canonical HTML: https://growth.iangoh.com/growth-ideas/custom-welcome-message-with-discobot-handoff/
- Source: [meta.discourse.org](https://meta.discourse.org/t/onboarding-discobot-automated-messages-other-options/394898?tl=en)
- GrowthDex source hub: [Discourse Meta: Onboarding: Discobot, automated messages, other options?](/sources/discourse-meta-onboarding-discobot-automated-messages-other-options-meta/)
- Last checked: 2026-05-30
- Rarity: uncommon
- Budget: free
- Channels: Community, Lifecycle Messaging, Support
- Stages: community onboarding, activation, welcome flow, support deflection


## Why this can grow

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.

## 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. For activation, the useful question is not whether users liked the page. It is whether they got to the first meaningful win faster. 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 custom welcome message with discobot handoff can create a measurable lift.
2. Turn the tactic into one offer, page, campaign, or workflow for the Community and Lifecycle Messaging channel.
3. Use the evidence from meta.discourse.org 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

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.

## Adjacent tactics in the same lane

- [GitHub contributing tab before first PR](/growth-ideas/github-contributing-tab-before-first-pr/) - 2 shared channels, 1 shared stage
- [Prefilled composer links for first-contribution routing](/growth-ideas/prefilled-composer-links-for-first-contribution-routing/) - 2 shared channels, 1 shared stage
- [Category banners from About-topic copy](/growth-ideas/category-banners-from-about-topic-copy/) - 2 shared channels, 1 shared stage
- [Founder 30-second reply SLA for early users](/growth-ideas/founder-30-second-reply-sla-for-early-users/) - 2 shared channels, 1 shared stage

## Read GrowthDex essays

Browse the plain-English essay index at [GrowthDex Blog](/blog/).

## Related GrowthDex essays

- [The community should teach the first contribution before it asks for loyalty](/blog/the-community-should-teach-the-first-contribution-before-it-asks-for-loyalty/) - community-led growth, brand trust, retention

## Advisory

If you want help turning this into a working growth system, Ian Goh offers advisory at https://iangoh.com/advisory.