How to Re-Engage Discord Members Who Never Finished Onboarding: Three Timed Follow-Ups
A day-by-day sequence for joiners who stalled before their first role, with the wording for each message, the rule that stops it, and the day you remove them.
The whole sequence in seven lines
- Define stalled. Joined more than a day ago, and still without the role that finishing your first step gives.
- Day one. A reminder inside the server that names the one step left and what it opens.
- Day three. One question from a named staff member that takes a single word to answer.
- Day seven. A last notice with the removal date and a working invite.
- Day fourteen. Removal by kick, with a line in a log.
- Stop early the moment the member replies or completes the step.
- Count the results weekly and fix the step where most people stall.
Those day numbers are the ones I use, and they are a recommendation. Keep the order if you change the spacing. I served as Head Discord Moderator for Google Developers, and I still run this sequence today.
Some words used throughout: a role is a label on a member that decides which channels they see. Onboarding is whatever a newcomer must do between accepting the invite and seeing the full server. The entry role is the role given for finishing it. A kick removes someone who can then rejoin with a working invite, and a ban blocks the account from coming back.
Start with the reason for removing people
Every server gathers members who accepted the invite and went no further. No role picked, the required step never done. They see almost nothing and say nothing. The usual responses are to ignore them or to post one more announcement for everybody.
Decide first why they should not sit there forever, because the reason shapes the whole sequence.
- The count stops being honest. Stalled accounts inflate the member number, and they drag down every rate measured against it.
- Mentions turn into noise. A mention sent to the whole server reaches people who cannot use the server, and each one teaches them to ignore the next.
- Unknown accounts stay inside. Nobody on staff can vouch for an account with no role and no messages after months.
Removal here is housekeeping. The door stays open, and the member is told so before it happens.
Who counts as stalled
The test has to give the same result whoever runs it. Mine is this: the member joined more than one day ago and has no entry role.
That depends on an entry role existing. Servers using Community Onboarding, Discord's set of arrival questions, can create one from what is already there. Discord's help center (2023) states that each pre-set answer can assign channels and roles and that a question can be marked required. Put one shared role on every answer to a required question. From then on, holding that role means the person finished.
The list comes from your server's Members page. Per Discord's help center (2024), that page shows each member's join date, how they joined, their roles and whether they agreed to the rules, and it can be sorted by join date. It is available on desktop or in a browser only. Sort by join date, pass over the last day's arrivals, and write down each name with an empty space where the entry role should be. Record the join date and join method beside it.
The three follow-ups side by side
| Follow-up | Day | Sender | Place | What it asks for |
|---|---|---|---|---|
| Reminder | 1 | The server, by staff post or automation bot | The single channel a member with no role can see | Complete one named step |
| Question | 3 | One staff member, by name | Direct message, or a private thread if that fails | One word: A or B |
| Last notice | 7 | The same staff member | Direct message, or the same private thread | Any reply before a stated date |
Each one asks for less effort than the one before and carries more weight. The first asks the member to finish the step. The second asks for a single word. The third asks only for a sign of life.
The second is the one that recovers people. An announcement to the whole server is addressed to no one, usually sits where a stalled joiner cannot read it, and repeats the instruction they already abandoned. A question from a named person is addressed to them alone and costs one tap. Once the member answers A or B, staff have what they need to assign the entry role and the right channels by hand, so the member never returns to the step that stopped them.
The wording for all three
Copy these and change the names. [first name] stands for whichever staff member owns the list, and the button named in the first message stands for your own step.
DAY 1, posted in the channel a stalled joiner can see
@name You are one step from the full server.
Press "Choose your path" at the top of this channel and pick
the option that fits you. That opens the help channels and the
main chat.
Stuck on it? Reply here and a person will help you.
DAY 3, direct message from a named staff member
Hi, this is [first name] from the team at [server name].
One quick question so I can set you up properly.
Which fits you better?
A. I am here to get help with something
B. I am here to learn and talk with other members
Reply A or B and I will open the right channels for you.
DAY 7, direct message from the same person
Hi, [first name] again. This is my last note.
Your access to [server name] is still not set up. On [date] we
remove accounts that never finished joining. It is housekeeping
and nothing against you.
To stay, reply A or B to my last message, or just reply here.
If now is a bad time, this link will let you back in whenever
you are ready: [invite link]A few notes on using them.
On the reminder. Start it with a mention, meaning an at-sign and the member's name, so the member is notified. Name one step and one result and stop. Should a role-less member see no channel whatsoever, grant read access to your start here channel before anything else. With heavy daily joins, hand this post to an automation bot that looks for the missing entry role a day after joining, and try it on a spare account first.
On the question. Offer two options and make both welcome. Sign it with a real first name and send it from that person's account. Leave out links, instructions and anything that must be read first. If the direct message will not send, use a private thread, which is a side conversation in a channel visible only to the people added to it.
On the last notice. It must hold a date, a way to stay and an open door. Test the invite. Discord's help center (2023) says a link created in the app lasts 7 days by default, so a default link sent on day seven has expired by day fourteen. Use one you have set to last.
What ends the sequence early
A reply of any kind stops the follow-ups. So does the member completing the step without a word. Past that point they hear only from a person.
- They answer the question. Assign the entry role and channels by hand that day. Confirm with one line.
- They describe a problem. A button did nothing, or a channel would not open. This goes to a person the same day. Fix their access by hand and write the problem down for the weekly count.
- They say it is not for them. Thank them. Send nothing further.
- They finish quietly. Remove the name from the list.
A problem report deserves the fastest handling of the four. It came from someone who wanted in, and the same fault is probably stopping people who did not write back.
Removal on day fourteen
kick. Never a ban, which would stop a person who did nothing wrong from returning.The log line holds the removal date, the member, their join date, how they joined, which follow-ups went out and who removed them. Keep it somewhere outside Discord. Discord's developer documentation (checked October 2026) describes the audit log as a record of administrative actions whose entries are kept for 45 days, which is too short for a record you will want next quarter.
What Discord's prune tool catches and what it misses
Prune is Discord's built-in mass removal, and it is easy to assume it does this whole job. It does part of it. Discord's help center (2022) explains that prune removes members who have not logged in to Discord for a chosen period, 7 or 30 days in the app, and that by default it only removes members holding no roles.
Two settings choices follow from that. I use the 30 day period, and only as an occasional sweep. Anyone absent from Discord for 30 days must have joined at least 30 days ago, so they are past day fourteen already. The 7 day period could remove someone eight days after joining, before the date your last notice gave them.
The second choice is the entry role again. Prune targets members without roles. If members who completed onboarding hold no role, prune cannot tell them from the ones who stalled.
The weekly count
One person fills this in each week. It takes the list, the log and a few minutes.
| Line | What a high number tells you |
|---|---|
| Joined | The size of the week. Every other line is read against it |
| Finished without help | The join flow is doing its job |
| Finished after the day one reminder | The step works and people overlook it. Make it harder to miss on arrival |
| Finished after the day three question | People wanted in and the step blocked them. Their replies say why |
| Finished after the day seven notice | A deadline moved them. The earlier messages may be too easy to skip |
| Removed on day fourteen | Check how these members joined. One source may be sending people with no intent to stay |
When most stalls happen at the same step, the step is the fault. Repair it in the join flow. Follow-up recovers people one at a time, and a repaired step stops the stall for everyone after them.
Where this follow-up sits
This sequence is one piece of onboarding and the first 48 hours, alongside entry design, the welcome, the first action and human contact. Support routing, documentation and reporting are separate layers next to it.
Nothing here needs more than the Members page, three saved messages and a log, so it can start this week. Begin with the day three question to everyone currently on the list. It is the message most likely to get an answer.
An inflated member count flatters nobody who has to act on it, and a short question followed by an open door keeps the number true. More at danieljeong.org.
Want a properly managed community?
Get Your Free Analysis →