A join event is the single most expensive moment in a member's lifetime, and it is the moment servers do the least with. Here is how to run an agent that treats a join as a short conversation instead of a broadcast slot.
The join event is one moment with the whole server watching. Most servers spend it on an embed listing channels. The member reads none of it, posts once or never, and the server has no idea which it was. Onboarding is a decision, not a message.
The classic welcome embed is a menu: read #rules, verify in #start-here, introduce yourself in #intros. A new member who is already interested skims it; a member who has no idea what the server is for does not know which item applies to them. The embed assumes the member has already decided what they want from the community, which is the thing they are least able to say at minute one.
Reaction-role and select-menu panels exist because static welcomes do not work — and they trade one drop-off for another. A member has to scroll, find the panel, decode which of eleven emoji correspond to their interest, and click. Every additional click is a point where someone decides it is not worth it. Role assignment is the single highest-value action in the flow and the one the platform makes the most friction-heavy.
Discord Server Insights gives you joins and total members. It does not tell you what fraction of this week's joins posted a message within 48 hours, which question in the welcome flow they abandoned, or which cohorts went quiet. So the one number that predicts retention — first-post rate — is never computed, and the flow is never changed. Bad flows persist for years because the failure arrives as a quiet Tuesday.
Trigger on the join event, ask two or four questions in-thread, map the answers to roles and channels, log the drop-off, and send a low-pressure DM at the 24-hour mark. No forms, no external bot, no watchtower.
Three outcomes: a member lands where they intended to instead of guessing, the staff stops hand-sorting newcomers, and you can see which questions lose people — the first-post rate and the drop-off funnel are both measurable.
The flow runs in the first minutes, before the member has decided whether the server is worth their evening. A scheduled welcome arrives too late to be an orientation — by then they have already drawn their own conclusion.
The member answers two or four questions and gets the roles and channels those answers imply. No reaction panel to scroll, no emoji to decode, no menu to abandon — the highest-value action in the flow happens without a separate click.
It records which question members stop at, not which members stop. That is the number that says which question to rewrite, and it is privacy-preserving by construction — the cohort count, not the person, is the unit.
Are you ready?
All without you getting tasks done on manual, missing out the opportunity you want, or putting your hard work in vain.
Try it with Zaira nowThe practical questions people ask before replacing their welcome channel with a conversation.
Two to four. Each must be answerable in one or two words and must unlock something concrete — a role, a channel, a resource. A question that cannot change what happens next is a social nicety and adds a drop-off point. If your current flow asks more than four, it is longer than the member's first few minutes.
No. The rules gate and the verification step stay — they are compliance, not onboarding. What changes is the part after them: instead of a static menu, the member has a short conversation that routes them. Many servers run both, with the conversation firing after verification completes.
That is the cohort the 24-hour DM is for, and it is the only one worth interrupting. Send one low-pressure message with a link to what they came for. Do not send a second — a second follow-up converts lurkers into leavers. Members who never answer and never respond are simply not interested, and the flow should leave them alone.
Yes. The answers map to roles and channels — a member who says they are a developer gets the Developer role and the contributing guide, a customer gets support. Zaira acts within the permissions you grant, so it can only assign roles below its own role in the hierarchy.
First-post rate — the share of new members who post within 48 hours — against last week. It is the metric Discord's own Server Insights does not compute, and it is the one most predictive of 30-day retention. The funnel by question tells you which question to shorten.
Yes, and that is where it pays for itself fastest. A small server cannot afford to hand-sort newcomers, and it also notices immediately when the flow is wrong — a single member's silence is visible at that scale.
Discord gateway connection