Onboarding methods that actually stick — a catalog, not a calendar

Onboarding is a set of doors, not a month. The 30-day member calendar already told you when to do the human work: first session, second hook, day-30 review. This article is the catalog of methods you hang on those days — welcome PM versus welcome thread, first-question design, Discourse’s TL0 reading gate, a XenForo validating or Established group, notices, fields, queues, checklists. Pick three. Staff them. Do not install twelve.

This is also not how you found a board. Launch week — seed threads, first ten members, the staff list — is a different job from “someone just confirmed their email.” Do not copy a founding checklist onto a registration. And this is not XenForo engagement chrome (watches, thread types, trophies). Chrome amplifies a door. It is not the door.

XenForo community sources we queried are technical about new accounts (link holds, profile-field locks, promotions into an Established group) and silent about welcome copy. Discourse official material is specific about the TL0 sandbox and silent about your tone. Where a method is operational practice, the sentence says so.

What “onboarded” means (so the catalog has a job)

A method is only good if you can say which door it opens.

Door	The member can	Method families
Confirmed	Mail works, they are not stuck in Unconfirmed	Email, validating group, Discourse ID
Oriented	They know the two rooms that match why they signed up	Start-here thread, notice, landing, fields
Permitted	They can post in the obvious room without a puzzle	Groups, TL0 honesty, test account
Spoken	A first public post that is not “thanks”	First-question design, intro thread
Answered	A human replied in public	Staff habit, template, watch
Returned	A second session that is not “check if anyone replied”	Watch explanation, ritual, not a contest

The calendar already said a registration is not a member. Here: a welcome PM is not oriented, a sandbox is not spoken, a like is not answered. Stack methods that cover different doors. Two methods on the same door is decoration.

Measure the doors with the health metrics set (new → first post, time to first human reply). Do not invent a “healthy onboarding rate.” Your four-week baseline is the number.

How to use this catalog

1. Map your current stack onto the table. Most boards have Confirmed and nothing else.
2. Pick one method per empty door. The rest of this article is options, not a shopping list.
3. Test every permission or trust-level change with a fresh account. The permissions primer is the XenForo map. Discourse: do not turn TL0 off to make day one prettier.
4. Write the owner. A method without an owner becomes a plugin you forget.

If you cannot staff public replies this month, do not add a campaign that creates more first posts. The calendar already said that. It is still the constraint.

Method 1 — Welcome thread (public, default)

A short “start here” thread in the room new people can actually see. Not two categories down under Archive / Meta / Other.

Door: Oriented, and a place to Speak if you ask a question.

What to put in post one (one screen).

• What this board is for, in one sentence.
• Three links: introduce yourself or the first-question thread; the main topical room; rules that fit on one screen (the rest in a separate thread).
• How watches / notification levels work, in two sentences.
• If you are on Discourse: that TL0 is a sandbox, that the composer will not warn about the one-image cap until publish, and that invited people start at TL1.
• If you are on XenForo: that Unconfirmed cannot post, and that a New member banner (if you use one) is temporary.

What not to put. Lore bibles. Staff process. A 12-page changelog. A Discord-only instruction that makes the forum optional.

Staff habit. Reply in public to every intro for as long as you run the thread. A template is allowed: welcome, we moved this, here is a related thread, here is one question. A like and silence is not a method.

Platform notes. XenForo: prefix Start here, sticky one thread, Block notice for message count 0. Discourse: pin in the default category, not a tenth category named Welcome. IPS: do not hide the only lively room inside a Club they have not found.

This is the default because it teaches the next lurker that humans live here. A private PM does not.

Method 2 — Welcome conversation / PM (private, optional)

A one-to-one message after confirm. Useful when the first public room is loud, or when you need to send a handle, a whitelist next step, or a “your post is in the queue.”

Door: Oriented (weak), Permitted (if it explains a hold).

Rules that keep it from becoming spam.

• One message. Not a five-step drip. The calendar already said one useful email; the PM is the same sentence in another pipe.
• Sent by a personal staff profile, not the root Admin account. XenForo community practice: casual contact from the nuclear badge shrinks the room. Admin stays for official/system mail.
• Contains the same three links as the welcome thread, plus “we also replied in public” if you did.
• No bot that only says “welcome to the family.” If you cannot write a sentence, do not automate a worse one.

When to skip it. If mail already fails (SPF/DKIM, or Discourse still on Discourse ID without SMTP), a PM you also email is theatre. Fix transport first. If you cannot staff the public reply, do not add a private one “to be personal.”

Private welcome is polite. Public reply is the demonstration. Do both only if you can staff both.

Method 3 — First-question design

The first post should be answerable in five minutes by a stranger who read one pinned page. That is a design problem, not a vibe.

Door: Spoken.

Shapes that work.

Shape	Prompt	Bad version
Intro	“Name, what you came for, one thing you are stuck on”	“Tell us your life story and list every game since 2004”
Weekly open	“What are you working on this week?”	“Remember the 2014 outage?”
Show the thing	“One photo / one config / one character”	“Best build contest, prize TBA”
Question type	A support ask with a solution box	Main hangout converted to questions

XenForo question threads keep the question on every page and let someone mark a solution. Use that in Support, not in the hangout. Discourse Solved (official plugin; hosted Pro and up) is the same job: topic owner and staff mark a reply; ?solved=yes filters the list. TL1 is the default group that can accept solutions. Neither tool writes the prompt.

Rules.

• The title a new person sees must not require lore.
• Staff move misplaced first posts with a sentence, not a silent yank.
• Do not grade the first post. “Wrong forum, read the bible” selects for veterans.
• Contests are not first-questions. They rent entries. See events.

If you already have a ritual thread, that is your first-question. Do not add a second one called “New member tasks.”

Method 4 — Discourse TL0 as an on-ramp (not a punishment)

Official trust-level behaviour, not a rank plugin. Full model: trust levels. Week-one vocabulary: beginner guide.

Door: Permitted, with honesty.

What TL0 actually is. New registrations start sandboxed so they cannot wreck the room or themselves. Documented default limits from the Discourse notebook: 1 embedded image (newuser max embedded media), 2 links, 2 mentions, 50 likes/day, 24-hour own-post edit, chat 20 messages / 30 seconds. They cannot flag, mute, or ignore. They cannot use core chat or personal chat until the allowed groups say so — default is not TL0. Exact visit / read / like counts to reach TL1 are admin-configurable; this article will not invent them. TL1 is an automatic job on the order of fifteen minutes once those requirements are met. Invited users typically start at TL1.

The method. Put the sandbox in the welcome topic. Tell them the composer will not warn about the image cap until publish. Give them a first-question that does not need four screenshots. Do not turn the sandbox off to “increase activity.” Meta practice (and the first-month failure list) is explicit: that is a spam magnet.

Reading gates. Requiring time in a rules category before general posting is allowed if you also tell them how to finish it. A silent gate is how sessions look fine and first posts never happen. Do not invent a numeric “read 30 topics” rule in your copy unless you opened your site settings and quoted them.

SSO / staff. Corporate and product communities often map employees to TL3 or TL4 on day one so the sandbox is not the staff experience. That is a group map, not an onboarding method for strangers.

Method 5 — XenForo confirming, validating, and Established

XenForo will sandbox nobody you did not sandbox. Registered can post in every public node the day they confirm, unless you built groups and a habit.

Door: Confirmed, then Permitted.

Unconfirmed / email confirmation. Setup → Options → User registration is where boards turn Enable email confirmation on. Until they click the mail, they are not a member you should measure. If confirmation mail never arrives, you do not have an onboarding problem. You have a mail problem. Test with a throwaway address you can open.

Validating as a human gate. Some boards keep new accounts in a restricted group until staff (or a promotion) moves them. That is a permission design: primary group stays Registered (or the system default), a secondary group carries the lock or the unlock. Never on Registered for “post” will also lock everyone you later promote — Never wins. Baseline on Registered, Yes on the group that is allowed, or Revoke on the node you want quiet. Analyze permissions with a test user after every change.

Do not confuse this with a whitelist application. Whitelist is a human yes/no on a character or a slot. Validating is “this account may speak in public.” Two doors.

Established as anti-spam, not as a welcome. XenForo community practice: hold posts that contain URLs when the author’s message count is below a threshold you set; keep unestablished accounts from filling profile metadata (location, occupation, website) until they have posted at least one valid message. High-risk privileges such as starting conversations or posting external links sit Not set on Registered and flip on via a promotion into an Established Members secondary group when criteria match — registered at least X days and at least Y messages. Official promotions live under Groups & permissions (also referenced as Access privileges → Promotions). They run hourly, and only for recently active members. No criteria means never awarded. Disabling a promotion does not demote people already in.

Those numbers X and Y are yours. Do not copy someone else’s screenshot. If the obvious first-question needs a link or a screenshot host, your Established gate is a lurker tax. Either allow one image/link in the intro room, or change the prompt.

New member banner (reversible). Official promotions can mark new users. A secondary group with a banner, given for “under 14 days or under 10 messages,” then removed, is a signal to staff: answer this person. Same permissions as Registered. The ranks article is the ladder. Here it is an onboarding highlighter, not a rank.

Method 6 — One notice, one action

Communication → Notices on XenForo. Criteria: user (guest, group, message count, avatar, registration age) and page. Types this site already documented from the manuals: Block, Scrolling, Floating, Fixed. One live Block per audience.

Door: Oriented.

Good notices.

• Guest, first screen: one sentence, one register button.
• Registered, message count 0: “Introduce yourself here” plus the watch hint.
• Search-engine landing: “There are N rooms. Start here.”

Bad notices. A scrolling stack of Discord, donate, merch. A Block that only staff see. An event notice that outlived the event.

Discourse equivalent: a banner theme component or a pinned topic, not five official topics the wizard seeded and you never rewrote. Change the default language in the wizard before you rewrite seed content — the beginner guide already said that.

Method 7 — Custom fields as intake, not decoration

Official XenForo: Users → Custom user fields. An ID you cannot rename, text versus choice, display on profile or next to posts, criteria for notices and promotions. Full design: custom user fields.

Door: Oriented (they told you why they came), sometimes Permitted (promotion on a choice).

Onboarding set that pays rent.

Field ID	Type	Why it exists
came_for	Choice: support / hangout / game X / other	Notice and auto-watch one room
region	Choice	LFG filters, not a free-text box
discord_handle	Text, contact	Optional. Do not require Discord to finish register

Do not collect twenty free-text boxes. Community practice: lock website/location on unestablished accounts. A required Discord handle on day zero is how you tell people the forum is a satellite. The forum versus Discord piece is the product choice.

Discourse user fields exist; do not invent a settings tour. Same rule: choice over text if you will filter on it.

Method 8 — Watches explained once

A watch is a promise: tell me when this moves. If the welcome never mentions it, you trained people to refresh like it is 2006.

Door: Returned.

Method. Two sentences in the welcome thread and the one useful email: how to watch this thread, how to watch this room, how to turn it off. Auto-watch one room they joined for (the came_for choice, or the default topical forum). Do not auto-watch everything. That is an unsubscribe on day two.

Discourse: notification levels per topic, category, and tag. Same sentence, different nouns.

If nothing moves, watches amplify silence. Create movement with a ritual or an answered first post, then ask them to watch it.

Method 9 — Staff reply budget and a template

Software cannot greet people. A named human answering new-member posts within a day is the method the calendar already treated as non-negotiable. Here it is written as a system.

Door: Answered.

Write the budget. “Weekdays, first posts in Intro + Support, personal accounts, template allowed.” Not “we are a family.” The active users article is the activity consequence of an unanswered first post: the next first poster learns the room is a museum.

Template (public). Welcome by name. If you moved the thread, say where and why. Link one related thread. Ask one question they can answer without lore. Sign the personal profile.

What the template is not. An auto-welcome add-on that posts “welcome!” and leaves. A like. A warning for the wrong prefix.

Admin identity again. Greetings are not official announcements. Use the unbadged or lightly badged profile. Save Admin for mail that has to look like the system.

If you cannot staff thirty days of replies, do not restyle the header this month. The next member will bounce on the silence, not on the font.

Method 10 — Two checklists (staff and member)

Checklists are methods. They are not articles you publish as the homepage.

Staff checklist (private staff room). Paste, tick, date.

1. Fresh test account can register, confirm, and post in the intended room.
2. Start-here is one click from the first logged-in view.
3. Rules fit on one screen.
4. Named humans own first-post replies this week.
5. Watches explained once.
6. One first-question a stranger can answer.
7. Welcome / staff process not readable by guests.
8. Discourse: TL0 limits mentioned; sandbox still on.
9. XenForo: confirmation mail arrives; Analyze permissions on the test user; Established gate does not block the intro prompt.
10. Day-7 look: first posts and second sessions, not registrations. The metrics article is how to read the sheet.

Member checklist (in the welcome thread, short).

1. Confirm mail (if you use it).
2. Read the one-screen rules.
3. Watch this thread or this room.
4. Answer the first-question or introduce yourself.
5. Come back when you get a reply — or on the ritual day.

Do not make the member checklist a twelve-step quest. That is a game you invented because the room was empty.

Method 11 — Landing and first screen (only if the hallway is the problem)

If guests never find the door, no welcome method will fire. A campaign landing has one button you will turn off. A portal has a first-screen job. Neither is onboarding. They are how some people arrive.

Method, not a rebuild: guests see one sentence and the start-here link. New Registered see the notice in Method 6. Returning members see What’s New / Latest. If those three stories disagree, you are not done. Test three sessions after every change.

Do not build a second homepage for the welcome sentence.

What not to copy from other boards

• A 40-node tree “so new people have a place.” XenForo community practice: deep segmentation looks empty and discourages participation. Broad rooms, prefixes, one obvious live room. The nodes article is the carpentry.
• The root Admin as greeter. Stifles disagreement. Use a person.
• Turning off TL0 or email confirmation because a friend complained. That friend is not your spam queue.
• Requiring Discord before the first post. You onboarded them to another product. See forum vs Discord.
• A contest as week-one onboarding. Entries are not members. Events owns contests.
• A points shop as a tutorial. Rewards people who already posted. Rewards is a later design conversation.
• Duplicating the 30-day calendar as a public quest. The calendar is for you. Members need one screen and one question.

Worked pairings (so you do not stack everything)

Hobby hangout, XenForo. Confirmation on. Welcome thread + first-question ritual. New member banner for staff eyes. One Block notice at 0 messages. Established promotion for links/PMs after your own X/Y. No welcome PM unless mail already works and you have spare minutes.

Support / docs, Discourse. TL0 left on. Welcome topic explains the sandbox and Solved. First-question is a real support ask in Support, not General. Staff (or mapped SSO staff at TL3/TL4) answer and mark solutions. No contest. See technical Discourse.

Game / RP with a human gate. Whitelist is the application article. Onboarding after approve: welcome thread in the playable room, character field, one ritual. Do not also invent a validating maze on top of the whitelist. The gaming architecture piece is the cupboard.

Small board, one admin. Methods 1, 3, 9. Stop. You cannot staff a PM drip, a field taxonomy, and an AMA. When hype from launch week dies, habits matter more than a new method.

FAQ

Is a welcome add-on worth it?
Only if it sends the same three links you already wrote, from a non-Admin account, once. If it posts a public “welcome!” and leaves, it is anti-onboarding. Write the thread first. Automate later if the sentence is stable.

Should first posts go to a moderation queue?
Queue links from unestablished accounts (community practice) if spam is real. Do not queue every intro. A queued intro is a delayed first reply, and reply latency is the product.

How long until we promote them?
Discourse: the software promotes TL1 on its job once your thresholds are met; do not invent the counts. XenForo Established: pick X days and Y messages you can explain, then test the intro prompt against them. There is no universal healthy number.

Do we need a separate welcome forum?
Only if the main room is so fast that intros vanish and you will staff the welcome room. Otherwise a prefix in the main room. Empty welcome forums are a hallway.

Takeaways

• The calendar is when. This catalog is what. Launch-week founding is neither.
• One method per door: confirmed, oriented, permitted, spoken, answered, returned.
• Default stack: public welcome thread, a first-question a stranger can answer, a staff reply budget, watches explained once.
• Discourse TL0 and XenForo Established are sandboxes. Explain them. Do not turn them off to look friendly.
• Welcome PMs, fields, notices, and landings are optional extras with owners. Without owners they are junk chrome.
• Test with a fresh account. Greet with a person, not Admin.

Pick three methods. Write the owners on a staff page. The next registration will tell you if you picked the right doors.