Recruitment that outlives the recruiter.
Apply from a button in Discord or from your page in the public directory, with the fields you pick either way. Applications route straight to your officer channel with approve and reject buttons on them, and the applicant gets a status link they can check on their own. The pipeline lives in your server, not in one officer's memory.
Most guild recruitment lives in three places that do not talk.
A form somewhere. A few DMs to whichever officer was online. And the rest in one person's head, the one who knows who applied last week and what they said. The applicant waits and asks. The officers lose track.
Then that officer takes a break from the game and the whole pipeline walks out with them. Hootus puts the form, the decision, and the history in your server, where any officer can pick it up.
The deeper problem with a form bolted on from somewhere else is that it has no idea who is in your guild. It cannot tell you the character is real, it cannot see that you are short two healers on Tuesday, and it certainly cannot put the new recruit in that raid. It collects answers and stops. Hootus is already holding your roster and your raid calendar, so approving somebody is a decision rather than the start of a separate job.
- Did anyone see the application from the Resto Druid?
- It is in my DMs, give me a sec.
- Hey, any word on my app? Posted it Tuesday.
- Wait, who approved them? When?
- Ash handled recruitment. Ash quit. Nobody else has the form.
One applies without leaving Discord. One applies without joining it.
The Resto Shaman already sitting in your server hits Apply to join the guild on the recruitment board and answers a modal. No browser, no tab, no link to lose. Hootus checks the character name against the armory on the way through, so class, spec and item level are read rather than typed.
The Holy Paladin who found you in the guild directory fills in the same form on your public page and never joins your Discord to do it. Same questions, same armory lookup, and both land in your officer channel as the same embed, built by the same code on both sides.
- In Discord
A button on the recruitment board
The board sits pinned in a channel listing what you are short of. Apply, name a character, pick a role, fill in the modal. Discord only allows five inputs on one modal, so when your form asks for more Hootus follows up with a button for the rest rather than quietly dropping the questions.
- On the web
Your page in the guild directory
The directory listing and the form are one page. Sign in with Discord, type a character name, and the armory fills in the rest. Nobody has to join your server first, which is rather the point of being listed at all.
The application shows up where your officers already are.
No tab open, no inbox to refresh. It posts to the channel you chose, with the decision buttons sitting on it.
- Availability
- Tue / Thu, 20:00
- Experience
- Kara clear, SSC 4/6
- Logs
- warcraftlogs.com/...
- Alts
- Lumitred, Sablewing
Submissions are rate-limited to three per Discord name a day, so one bad night cannot flood the channel. When recruitment is closed, the apply page says so instead of taking applications into a void.
- Decide in Discord or on the webClick the button on the embed, or work the queue on the recruitment dashboard. Either way it writes to the same place and the embed stays in sync.
- A reason on every rejectRejecting or reopening asks why, and the answer is kept as review history. The next officer reads it instead of asking.
- Approve straight into a raidTake someone on and drop them into the next upcoming raid in the same action. No second tool, no retyping a name.
Apply, route, decide, track.
Four steps, and not one of them is retyping a name by hand.
- They apply
A page you shaped, not a fixed template
Discord sign-in first, whichever door they came through. They type a character name and Hootus pulls class, spec, item level, and avatar from Blizzard, so you are reading a real character. The rest is the fields you turned on, with presets to fill the obvious ones.
- It routes
Into your officer channel, as an embed
It lands in the channel you pointed recruitment at, with Approve, Interview, and Reject sitting right on it. No tab to keep open, no inbox to refresh, the decision happens where your officers already are.
- One officer decides
Stamped with who, and when
Whoever clicks gets their name on it with the time. The embed recolours and the buttons lock, so the next officer scrolling past knows it is handled and nobody doubles up.
- They can check
A status link instead of a DM
Every application carries a link the applicant can open: pending, interviewing, accepted, or rejected. They can withdraw themselves too. Nobody has to ask an officer for a word.
The Resto Shaman has to find you first.
Every guild in the directory opened recruitment on purpose. Yours can sit there too.
Set it up once, hand it to the next officer.
Recruitment config is a settings page, not a tribal secret.
- Open or closed. Flip recruitment on when you need bodies, off when you do not.
- The channel. Pick where applications post. Change it whenever.
- Roles and classes. Say what you are recruiting, and the directory says it too.
- The form itself. Choose which fields an applicant sees.
Ash handled recruitment. Ash quit. The pipeline stayed.
The officer who approved the Holy Paladin three weeks ago does not have to be online for anyone to see it. The form, the decision, the reason, and the history all belong to the guild, and the next person to pick it up starts with all of it.
Put the form where your guild lives.
Add HootusPlootus, point recruitment at your officer channel, pick your fields. Applications stop living in DMs and start landing where any officer can act on them.