Most “dead forum” post-mortems blame the platform, the theme, or Google. The quieter failure is onboarding: someone registers, cannot see where they belong, posts once in the wrong place, and never comes back. Software cannot fix that. A 30-day plan can.
This is written for XenForo and Invision Community admins. The buttons differ. The sequence does not.
What “joined” actually means
A registration is not a member. A member is someone who:
- can find the two or three forums that match why they signed up
- has been answered by a human within a day of their first post
- has a reason to open the site on day 7 that is not “check if anyone replied”
If you only measure registrations, you will celebrate the week the board dies.
Days 1–3: make the first session obvious
Cut the empty hallway. The first logged-in view should not be a dump of every node you ever created. Use a short welcome thread, a “Start here” prefix, or an IPS Page that links to three places: introduce yourself, the main topical forum, and the rules in one screen of text.
Answer the first post like it matters. The first reply teaches people whether the room is alive. A moderator template (“Welcome, we moved this to X, here is a related thread”) is better than a like and silence.
Do not make them hunt for permissions. If they cannot post in the obvious forum, they will assume the site is broken. Test this with a fresh account every time you change groups — see the XenForo permissions guide.
Send one useful email, not a drip novel. “You registered. Here is the introduce-yourself thread. Here is how watches work.” If your mail never arrives, fix SPF/DKIM before you write more copy.
Days 4–14: give them a second hook
People who survive week one still leave if the only activity is old regulars talking to each other.
- A weekly open question in the main forum, posted by staff, with a title that a new person can answer without lore. “What are you working on this week?” beats “Remember the 2014 outage?”
- A staff reply budget. If you cannot reply to new posters for two weeks, do not run a campaign that creates more of them.
- One ritual that is not a contest. Contests attract entries, not members. A Friday link thread or a monthly “show your setup” thread creates a reason to come back without inventing winners.
On IPS, Clubs can isolate new people from the main conversation. Do not put the only lively room behind a club they have not found. On XenForo, do not hide the welcome forum two categories down under “Archive / Meta / Other”.
Days 15–30: promote or let go
By day 30 you know who is going to stay.
Promote with work, not titles. A trusted new member can help with a FAQ thread, a tag clean-up, or greeting — before you hand them a moderator group. Early staff badges without a job create politics.
Close the loops you opened. If you asked people to introduce themselves, staff should have replied. If you asked for feedback on a feature, publish what you will or will not do. Unanswered official threads train people to ignore staff.
Look at the actual numbers. Registrations, first posts, second sessions in seven days, posts by accounts younger than 30 days. If first posts are fine and second sessions are not, the problem is the homepage and watches — not the registration form.
A checklist you can paste into a staff forum
- Fresh test account can register, confirm mail, and post in the intended forum.
- “Start here” is one click from the first logged-in view.
- Rules fit on one screen; the rest lives in a separate thread.
- A named human answers new-member posts within 24 hours.
- Watches / follows are explained once, in the welcome mail or thread.
- One recurring staff thread exists that a stranger can reply to.
- Welcome / staff forums are not readable by guests if they contain process.
- Day-30 review: second-session rate, not just new accounts.
Onboarding is not a plugin. It is a calendar. If you cannot staff thirty days of replies, do not spend the month restyling the header. The next member will bounce on the silence, not on the font.