Every new member gets
a personal welcome in seconds.
A bot watches my community around the clock. The moment someone new joins, it grabs their name and fires a warm, personalized welcome that tells them exactly where to start. Nobody slips through the cracks. Nobody goes cold on day one.
The welcome message that decides if they stay.
Most community owners lose a third of their new members in the first 48 hours. Not because the content is bad. Because nobody said hello. A new member joins, sees a wall of existing conversation, has no idea where to start, and quietly disappears. The fix is a single warm message that arrives the moment they join, greets them by name, tells them exactly what to do first, and makes them feel seen. That message is now automatic, every time, at any hour.
Who it’s for
Anyone running a paid or free community: Telegram groups, course platforms, membership areas, email lists, Discord servers. Especially useful if you run a one-person operation, ship content on a tight schedule, and cannot personally greet every new member within the first hour. If your community adds more than 10 new members a week and you are not greeting each one personally, this is for you.
What goes wrong
Without the bot, new members arrive to silence. The ones who join at 2 AM see nothing for 8 hours. The ones who are shy do not ask where to start and never find it. Early churn is almost always a first-impression problem, not a content problem. A member who goes cold in the first 48 hours almost never comes back, and you paid real money or real effort to acquire them.
How the machine works
A trigger watches the community platform for new member events. The moment one fires, the bot looks up the member’s name, selects the right welcome template for that community, fills in the name, and sends the message within seconds. No human in the loop. No delay. One warm message that feels personal and points them to step one. The bot replaces the 30-minute daily welcome ritual that most community owners skip when they get busy.
What you get back
Around 30 minutes a day back from manual welcoming at scale. Roughly 180 hours a year. A modest but steady lift in 30-day retention, because members who receive a personal welcome in the first hour are far more likely to stay. Compounded over a growing community, that retention lift is worth real money. The first impression every new member gets is warm, personal, and consistent, whether they join at noon or at 3 AM.
A third of new members were going cold before I said hello.
I started noticing the pattern about six months into running a Telegram community. New members would join, I would see the notification, and then life would happen. A meeting, a recording session, a school run. By the time I got back to the app, the new member’s join notification was buried under 40 other messages. When I finally typed “Welcome!” the member had been sitting in the group for six hours staring at a conversation they had not been invited into. Some of them had already left.
The problem was not the community content. The problem was the gap between the moment they joined and the moment they felt seen. That gap was me. I was the bottleneck. When I was at my desk, new members got a fast, warm hello. When I was busy, they got silence. The standard of the first impression depended entirely on where I was on the day they decided to join.
So I built a small bot. The moment a new member joins any of my communities, the trigger fires. The bot grabs their display name, selects the right welcome template for that channel, fills in the name, and sends the message. It takes about three seconds from join event to delivered message. The member gets a warm personal hello that tells them their name was noticed, confirms what community they joined, points them to the one first action they should take, and invites them to ask a question. Everything a good personal welcome does, every single time, without me touching the phone.
The retention number moved. Not dramatically on the first week, but steadily. Members who received the instant welcome were more likely to reply, more likely to post in their first session, and more likely to still be active 30 days later. None of that surprised me in hindsight. It is the same reason a restaurant host matters: the first 30 seconds of a guest’s experience shapes every minute that follows.
Proof point: I document real operations numbers from my own businesses on my YouTube channel, including community retention before and after automations like this one, so the retention figures on this page are checkable against a real operation, not a made-up case study.
Three moves that turn every new join into a member who actually stays
What made this work was treating the welcome message as the most important content in the community, not an afterthought. The bot hangs on three moves: personalize the greeting so it feels like it was sent to them, orient them with one clear first action, and open the door for a reply. Done right, it recovers the roughly 30 percent of new members who would have gone cold from silence. At 100 new members a month that is 30 people kept inside the community, compounding forward every single month.
Personalize the greeting so the member knows they were noticed
The bot opens with the member’s name, not “Hello everyone” or “Welcome to the community.” That single word, their name, is the difference between a message that reads like a bot and a message that reads like a host who saw them walk in. It confirms which community they joined, because people often join several at once and are disoriented. Two sentences, their name, the community name, warm tone. That is the whole personalization layer and it costs nothing extra to run.
Give them one first action, not a list of resources
The single most common mistake in welcome messages is listing ten things the new member can do. A pinned post, a resource library, a getting-started guide, an introduction channel, a rules doc. Ten options is zero options. The bot gives them one: the single best first action for someone who just arrived. For a course community, that is Module 1, Lesson 1. For a Telegram group, that is the pinned post. For a membership, that is the onboarding video. One action, one link, one sentence. A member who completes one action on day one is ten times more likely to complete a second action on day two.
Open the door for a reply so the conversation has somewhere to go
The last line of every welcome message ends with an invitation. Not a demand, not a form, not a survey. A simple sentence that tells the new member it is safe to ask a question or share where they are starting from. That invitation is what turns a one-way announcement into the beginning of a conversation. Members who reply to the welcome message are the ones who become the most engaged long-term. The bot cannot force a reply, but it can make the first move and keep the door open.
Once those three moves are in place, the first-impression problem is solved permanently. Every new member, at any hour, gets a welcome that feels like the community is staffed and paying attention.
Before the bot
- New members joined to silence, especially at night or on weekends
- My welcome quality depended entirely on whether I was at my desk
- About 30 percent of new members went cold within the first 48 hours
- Generic “@username welcome to the group” messages that felt like nothing
- No consistent orientation to step one, so most members never found it
After the bot
- Every new member gets a warm personal hello within about 3 seconds
- The welcome quality is the same at 3 AM as it is at 3 PM, every day
- Steady lift in 30-day member retention from a better first impression
- Each message uses their actual name and points them to one clear action
- The door is always open for a reply, turning a notification into a conversation
Prompt 1: write the welcome template for a free community
The template is the heart of the bot. Use this prompt to write a free-community welcome that feels warm and personal, names the community, gives one clear first action, and ends with an open door. Lock it once, the bot uses it on every new free-member join from that point forward.
Free-community welcome template writer
Act as a community host writing a welcome message for a new member who just joined a free online community. The message will be sent automatically by a bot within seconds of the member joining, so it must feel warm and personal, not mechanical. My community name: [paste] My community platform (Telegram, Discord, Facebook Group, etc.): [paste] What the community is about in one sentence: [paste] The single best first action for a brand-new member (pinned post, intro channel, getting-started video, etc.): [paste] My voice style (casual, formal, friendly, direct, conversational): [paste] Write a welcome message that does exactly these four things. One: open with their display name so the message feels personal. Use the placeholder [NAME] where the bot will fill in their actual name. Two: confirm what community they just joined and what it is for, in one warm sentence. Three: give them one clear first action with a direct link or instruction. Do not list more than one action. Four: end with a single open invitation to ask a question or share where they are starting from. Keep the whole message under 80 words. No bullet points. Plain conversational sentences. Write it in my voice style. Avoid corporate buzzwords and filler language. Plain words only.
The output is the template the bot loads every time a new free member joins. Lock it once per community. Update it whenever the community’s first action changes.
Prompt 2: write the welcome template for a paid community or course
Paid members need a different welcome. They have just spent real money and the first message they receive sets the tone for the whole membership. Use this prompt to write a paid-member welcome that acknowledges their decision, confirms what they have access to, and points them to module one or lesson one immediately.
Paid-member welcome template writer
Act as a community host writing a welcome message for a new paying member who just enrolled in a course or membership. This person has spent real money and the first message they receive shapes everything that follows. Write in a tone that acknowledges their decision without being sycophantic. My program or membership name: [paste] What the member just gained access to (course, coaching, resources, community): [paste] The single first action they should take right now (Module 1 / Lesson 1 link, onboarding video, private group invite): [paste] The one support channel or contact they should use if they have a question: [paste] My voice style (casual, formal, friendly, direct): [paste] Write a welcome message that does these four things. One: open with their display name. Use [NAME] as the bot placeholder. Two: confirm what they just unlocked in one grounded, non-hype sentence. Three: give them one clear first action with the exact link or instruction. No lists. One action only. Four: tell them exactly where to go if they hit a question. Keep the whole message under 100 words. Plain sentences. Write in my voice style. No bullet points. No exclamation marks unless they match my voice. No corporate language.
The paid-member welcome is the first content your new customer receives. It should feel like a host opening the door, not a confirmation email.
The 3-minute overview of how this works
Before the build steps, watch this short overview. It covers the mechanics behind machines like this one. 1,000+ students have used these mechanics to save two hours a day, with zero coding.
Want to learn the mechanics behind community bots like this one?
I teach the same mechanics that make this welcome bot run inside Automations Made Easy. 1,000+ students have used these mechanics to save two hours a day and make a one-person operation feel like a staffed community team. No coding required.
Week one: every new member welcomed, zero manual messages sent.
The first week of running a welcome bot is designed to be invisible to you and very visible to your new members. You do not send a single manual welcome. The bot handles every join event, 24 hours a day, whether you are recording, sleeping, or on holiday. What you are watching for in week one is not a retention spike, it is confirmation that the loop closes correctly: member joins, trigger fires, name is grabbed, right template is selected, message is sent, message reads naturally.
Week one in a community of 50 to 100 new members a month looks like this. About 15 to 25 new members join across the week. Each one triggers the bot. Each one receives a warm personalized welcome within seconds. Some of them reply. Some of them go straight to the first action. A few of them will message me directly to say the community feels active, not because the community is particularly active that week, but because someone said hello to them the moment they arrived. That single perception shift, from cold group to welcoming community, is what week one is meant to produce.
The point of the first week is not the numbers. The point is to prove the loop closes: member joins, bot fires, name lands correctly, message reads warm, first action is clear, door is open for a reply.
From there the maths compounds quietly. At 100 new members a month, a modest 10 percent improvement in 30-day retention from better first impressions is 10 extra members staying per month. Over 12 months that is 120 members who would have churned but did not. In a paid community at even a modest price point, 120 retained members is a meaningful number. The bot costs almost nothing to run and fires automatically every single time a new member joins. The welcome that used to depend on whether I was at my desk is now consistent, warm, and immediate, around the clock.
All of this runs while you create, travel, record, or sleep. The trigger watches the platform, the bot personalizes the message, the message lands in seconds. The community grows on a schedule that matches your content, and the first impression every new member gets is the one you designed on purpose.
Prompt 3: write a follow-up message for members who go quiet after day 3
The welcome message handles day one. But some members go quiet after the first 72 hours without completing the first action. Use this prompt to write a short, warm follow-up that is sent automatically three days after joining if the member has not yet engaged. This is the second line of defense against early churn.
Day-3 re-engagement message writer
Act as a community host writing a short re-engagement message for a member who joined three days ago but has not yet taken the first recommended action or posted in the community. The message should feel like a genuine check-in, not a nag. My community name: [paste] The first action you originally recommended to them: [paste] A secondary resource or entry point they might find easier (a video, a short intro post, a question to answer): [paste] My voice style: [paste] Write a message that does three things. One: open with their name using the placeholder [NAME]. Two: acknowledge that the community can feel overwhelming at first and offer a simpler starting point than the original one you recommended. Three: invite them to share where they are or ask a question, so you can point them in the right direction. Keep it under 60 words. No guilt language. No urgency language. Plain and warm. Write in my voice style.
The day-3 follow-up is the second touch in the onboarding sequence. Wire it to fire only if the member has not posted or clicked the first-action link within 72 hours of joining.
Prompt 4: build the onboarding sequence that runs for 7 days after joining
A single welcome is a good start. A short sequence is what builds a habit. Use this prompt to design a 7-day onboarding sequence: the welcome on day 1, the check-in on day 3, and a community highlight on day 7 that shows the new member what an active engaged member looks like and invites them to become one.
7-day onboarding sequence designer
Act as a community strategist designing a 7-day onboarding message sequence for a new member. The sequence should feel like a thoughtful host guiding a newcomer through their first week, not a drip campaign trying to sell them something. My community name: [paste] What the community is for: [paste] The single first action for day 1: [paste] One community resource or highlight worth sharing on day 7 (a popular discussion thread, a member win, a pinned resource): [paste] My voice style: [paste] Design three messages. Day 1: the welcome. Use [NAME] as the name placeholder. Personalized, one action, open door. Under 80 words. Day 3: the check-in. Send only if the member has not yet engaged. Simpler entry point, no guilt. Under 60 words. Day 7: the community highlight. Share one real example of what an engaged member does or achieves here. Invite them to try it. Under 80 words. For each message: write the full text, name the trigger condition, and note the platform action required (send DM, post in channel, tag user). Write in my voice style throughout.
The 7-day sequence replaces the first week of manual community management. Wire the three messages to a single automation, set the conditions, and let the sequence run on every new member automatically.
The exact build, step by step
Set the trigger on your community platform
The trigger is the source of the whole bot. Every major community platform exposes a new-member event you can listen to. Telegram fires new_chat_members the moment someone joins a group. Course platforms like Kajabi and Teachable fire enrollment webhooks you can catch in n8n or Make. Discord fires member-join events via its gateway API. Point a workflow tool at the correct event for your platform. When a new member arrives, the workflow wakes up once with the member’s ID, display name, and join timestamp. This single event is all the bot needs to start.
Look up the right welcome template for this community
If you run more than one community (a free Telegram group, a paid course, a membership), each one needs its own welcome template. Store each template as a row in Airtable or a small text file, keyed by channel ID or community name. When the trigger fires, the bot checks which community it came from, looks up the correct template, and pulls it forward. A paid-member join gets the paid-member welcome. A free-group join gets the free-community welcome. Same bot, different template, completely different message. The lookup adds about one second to the total time.
Personalize the template with the member’s name
The template contains a [NAME] placeholder the bot fills in from the trigger data. A simple string-replace operation: find [NAME] in the template text, replace it with the member’s actual display name from the platform. The rest of the message stays exactly as written in your template. This is the only personalization step needed for a free-community welcome. For paid communities you can also fill in [PROGRAM] or [MODULE_1_LINK] from a small lookup table so each paid-member welcome names their specific purchase. The more specific the fill, the more personal the message reads.
Send the welcome message via the platform’s API
With the personalized message ready, the bot sends it via the platform’s messaging API. For Telegram, that is a sendMessage call to the member’s chat ID. For Discord, a direct message to the member’s user ID. For email platforms, a transactional send to their address. The whole call takes about one second. The member’s device receives a push notification within moments of joining. From their perspective, someone noticed them the instant they arrived. That perception is exactly what a well-run community should produce, and the bot produces it every time at zero marginal cost per message.
Log the join event and the welcome sent to a tracking row
After the message is sent, the bot writes one row to Airtable: member name, community, join timestamp, welcome template used, and a confirmation flag that the message was delivered. This log is not just for hygiene. It is the data source for the day-3 follow-up trigger. When the day-3 timer fires, it checks the log for members who joined 72 hours ago and have not yet had a follow-up sent. It also helps you spot if a template is not performing: if members welcomed with template A respond and stay, and members welcomed with template B go quiet, the log tells you which template to rewrite. The whole row takes under a second to write.
Wire the day-3 follow-up for members who have not engaged
The final step closes the second line of defense against early churn. A scheduled check runs every day. It reads the Airtable log, finds members who joined exactly 72 hours ago and have no engagement event recorded against their ID, and sends the day-3 message from Prompt 3: a warm, low-pressure check-in that offers a simpler entry point. The check is a simple filter on the log: joined_at < now - 72h AND engaged = false. No engineering required. The follow-up fires only when it is needed and never fires twice to the same member. Members who engaged after the welcome receive nothing on day 3, because they do not need it.
Trigger fired
New member joins the community platform. The workflow wakes once with their name, ID, and the channel they joined.
Template selected
The bot looks up the correct welcome template for this specific community from the Airtable template table, based on the channel ID.
Message personalized and sent
The NAME placeholder is replaced with the member’s display name. The personalized message is sent via the platform API within seconds of the join event.
Logged and day-3 check armed
One row is written to the Airtable log. The daily schedule checks back in 72 hours for any member who has not yet engaged, and sends a warm follow-up if needed.
Build this welcome bot using the same playbook 1,000+ students use
Automations Made Easy teaches the mechanics behind bots like this one. Step by step, no code, plain English. Stop losing members to silence on day one and make a one-person operation feel like a properly staffed community.
The six months after I switched it on
Here is the shape of the first six months after the welcome bot went live across my communities. The numbers are modest in month one and steady from month three onward, because that is how retention compounds: each month the community is slightly larger, the bot fires more often, and the members who stay from a good first impression add their own activity to the group.
New members retained past 30 days, per month (welcome bot active)
Caption: extra members retained past 30 days each month compared to the pre-bot baseline. Three things matter on this chart. The gain stabilises around 26 to 28 extra retained members per month from month three onward. Every one of those retained members cost the same to acquire as a churned member would have. And none of those months required a single manual welcome message from me.
What other students built
I teach the simple mechanics behind systems like this in Automations Made Easy. Students who built their own welcome bot sent back what changed in the first month.
“I was losing about a third of my new Telegram members within the first two days. After I added the welcome bot, new members started replying, asking questions, posting. The community went from a ghost town in week one to an active group. The change was visible within days.”
“I have four communities across two platforms and I was physically unable to welcome everyone personally. The bot covers all four with different templates. Each community gets a message that matches its voice. My members have no idea it is automatic and several have told me the community feels personal.”
“The day-3 follow-up was the piece I did not expect to matter. Four people who had gone quiet after the initial welcome replied to the follow-up, completed their first module, and are still in the community three months later. That is real money recovered from something that used to just disappear.”
“Saved me about 30 minutes a day across my communities. That sounds small until you realize it is two and a half hours a week, every week, that I now spend on content instead of manually typing hello. The bot does it better than I did anyway because it never forgets and never sends the wrong template.”
What’s inside Automations Made Easy
AME is not a library of pre-built automations. Every business is slightly different. What is reusable across all of them is the underlying mechanics: how to set up small machines that listen, personalize, and follow up while you sleep, and how to wire the pieces together without writing code.
The program walks you through six modules: The Right Tools (the cost-effective, no-code stack I actually use), Task Selection Mastery (which automations are worth building first), Design Secrets (mapping an automation before you build it), Zero to Hero (complete beginner to confident automator), Real-World Application (we build a full automation together, end to end), and Monetization Mastery (turn the skill into a side-business).
It also includes done-for-you templates you import in two clicks, over-the-shoulder training videos, and the same playbook 1,000+ students have used to save two hours a day. No coding required. If you can copy and paste, you can build this.
The welcome bot: common questions
Pulled from what readers and Automations Made Easy students ask most about this automation.
Does the welcome message really feel personal, or does it read like a bot wrote it?
It depends on how you write the template, and that is the whole job of the prompts on this page. A welcome that opens with the member’s name, names the community they just joined, tells them one specific next action, and ends with an offer to answer questions reads nothing like a generic greeting. The bot fills the name and the channel automatically. The warmth comes from the template you lock once. When you write the template in your actual voice, the member has no way of knowing whether you typed it personally or not. Most members in my communities have replied to automated welcome messages asking me a follow-up question, which tells you the message landed as if it came from me.
Which community platforms does this work on?
Any platform that fires a trigger when a new member joins. Telegram groups fire a new_chat_members event the moment someone is added or joins. Course platforms like Kajabi, Thinkific, and Teachable all have enrollment webhooks. Email platforms like ActiveCampaign, ConvertKit, and Mailchimp all have new-subscriber triggers. The welcome bot wires to whichever trigger your community platform exposes. If your platform supports webhooks, the bot works. If it does not support webhooks, n8n and Make.com can poll it on a short schedule and achieve almost the same result.
What should a good welcome message actually say?
Four things, in order. One: greet them by name so the message feels like it was sent to them, not to the group. Two: confirm what they joined so there is no confusion about which community this is. Three: give them one clear first action, not a list, one. Where to start, what to read first, which channel to go to, whatever orients a brand-new member in under ten seconds. Four: make it easy to reply with a question, so the member knows the door is open. That is the whole structure. Short, warm, specific, one action. Everything else is optional decoration.
How much does early churn actually cost?
A member who goes cold in the first 48 hours and never engages again is worth effectively zero, even though you paid to acquire them. If acquiring a new member costs you somewhere between $2 and $20 in ad spend or effort, and 30 percent of new members go cold in the first 48 hours because nobody welcomed them, then at 100 new members a month you are burning $60 to $600 every month in lost retention from a single missing touch. A welcome message costs almost nothing to run and fires every time. The economics are not subtle.
Can I run different welcome messages for different communities or tiers?
Yes, that is actually the most common setup. Each community or membership tier gets its own welcome template stored as a small text file or an Airtable row the bot looks up by channel ID. When someone joins the free Telegram group, they get the free-community welcome that tells them where to find the pinned resources and invites them to introduce themselves. When someone joins the paid course, they get the paid-member welcome that names their first module, their first video, and the private support channel. Same bot, different lookup, completely different message. You build each template once and the bot serves the right one automatically for as long as the community runs.
More Money Makers like this one
Built from the same handful of mechanics. Each one captures, converts, or keeps members who would otherwise have walked away.
Run this welcome bot yourself, or learn the mechanics inside Automations Made Easy.
If you want to learn the mechanics behind community onboarding automations like this and build your own, Automations Made Easy is the playbook. Step by step, no code, plain English. If you want to talk through which trigger, template structure, and platform setup would work for your specific community first, I take a small number of consulting clients each month.
€497 one-time · Lifetime access · 1,000+ students
