Recruitment that outlives the recruiter.
A public apply page with the fields you pick. Applications routed straight to your officer channel with approve and reject buttons. A status link the applicant 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 don't talk.
A Google form somewhere. A few DMs to the officer who happened to be online. And the rest in that 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 the door with them.
HootusPlootus puts the apply form, the decision, and the history in your server, where any officer can pick it up and the applicant can check in without pinging anyone.
- "Did anyone see the application from the Resto Druid?"
- "It's 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."
Apply, route, decide, track.
Four steps, and not one of them is retyping a name by hand.
Ask what you actually want to know.
The form is yours to shape. Turn on the fields that matter to your guild and leave the rest off. When an applicant types a character name, the bot looks it up against Blizzard and fills in class, spec, item level, and avatar, so you are reading a real character, not a name they typed from memory.
Discord sign-in is optional on the page. When recruitment is closed, the page says so instead of taking applications into a void. Submissions are rate-limited to three per Discord name a day, so a bad night doesn't flood your officer channel.
- Raid experience and previous guilds
- Availability across your raid nights
- Logs URL, addons, and raid completion
- A playstyle preset you choose to ask about
- Applications bucketed by pending, interviewing, accepted, rejected, and withdrawn
- Full detail per applicant: experience, addons, and prior applications by the same person
- A reason required on reject or reopen, kept as review history
- Approve an applicant and drop them into the next upcoming raid in one action
The decision happens once, and it sticks.
Click a button on the embed in your officer channel, or open the recruitment dashboard on the web and work the queue there. Either way the decision is stamped with who and when, a reject carries a reason, and the Discord embed stays in sync. Approve someone and slot them straight into the next upcoming raid without a second tool.
Because it all writes to one place, the officer who approved the Holy Paladin three weeks ago doesn't have to be online for anyone to see it. The history is the guild's, not theirs.
Set it up once, hand it to the next officer.
Recruitment config is a settings page, not a tribal secret. Open it, choose your channel, your recruiting roles and classes, and the fields on the form. Flip recruitment on when you need bodies, off when the roster is full.
- Toggle recruitment open or closed
- Pick the channel applications post to
- Set the roles and classes you are recruiting
- Choose which form fields applicants actually see
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.