Game Org module · Cross-game

Recruiting an org is a pipeline. Not a bot that says "welcome" and walks off.

In most gaming orgs, a new Discord arrival gets greeted by a bot, then ignored until an officer runs into them by accident. The interview dossier is a mental post-it. Old rejects coming back under a new handle slip through unnoticed. And once accepted, the recruit floats across fifty channels with no idea what's expected of them. Game Org replaces all that with a tooled pipeline: the bot catches the arrival, returnee history reattaches by itself, the org defines its own mandatory integration steps, and the recruit sees their home turn into a live progress checklist.

Deploy for free See the demo

The pipeline starts on Discord. Not on a Google Form.

The candidate has nothing to fill out, nothing to share, no account to create. They join your Discord server — and they're already in your pipeline. The Game Org bot listens for arrivals, automatically creates an applicant in "New" status, and pushes the card onto every connected recruiter's screen in real time. The qualification chat happens on Discord, naturally. The recruiter fills in the interview dossier later, when they have the info. And if the Welcome Bot is plugged in upstream, the newcomer has already filled in your pre-form on Discord: their answers are attached to the card, and the recruiter starts with context instead of a blank page.

  • Zero candidate friction — no account to create, no public form, no link buried in a channel under three pings
  • Live updates — the moment a player arrives, their card pops up instantly on every connected recruiter's screen, no page refresh
  • No double-handling between recruiters — the shared list keeps two officers from picking up the same file in parallel
  • Three clear statuses — New, Dossier filled, Re-application. The recruiter knows at a glance where every candidate stands.
Applications tab: grid of candidate cards with colored tags (New, Dossier filled, Re-application), stats bar up top, per-card action buttons (Fill dossier, Friend, External).
Your candidate arrives on Discord. Your pipeline knows before you say hello.

Returnees don't slip through the cracks.

A former member who slammed the door and comes back under a new handle, a reject from six months ago trying again without saying so, a player classified as "Friendly" who now wants in for real: in most tools, none of this shows up. Game Org matches on the Discord ID, not the displayed handle. A name change no longer hides anything. The "Re-application" tag then appears — a neutral, factual signal: this person already has a file with you, read their history before you decide.

  • Match on Discord ID, immune to handle, avatar or server changes
  • History auto-attached — every past dossier (accepted, rejected, Friendly) is one click away on the card
  • "Re-application" tag — a neutral signal: this person has applied before. The recruiter opens the history and decides with full context.
  • Risk flag — for competitive orgs, a dedicated dossier field flags a profile that raised concerns, trace kept for the next application
Candidate card with a "Re-application" tag, a history panel open revealing three past dossiers: two rejections, one Friendly.
They changed their handle. Their Discord ID didn't. Neither did their history.

Your org decides what "ready" means.

In Game Org, an accepted recruit doesn't walk straight into an operational section. They enter an integration path whose steps are defined by your org. Trainings to complete, drills to pass, minimum event count, mid-path interview: you set the bar. Until every mandatory step is checked, the recruit stays in "In Training" with their progress bar visible. The moment they're all checked, they move to "Ready" and assignment unlocks.

  • Configurable mandatory steps set by the org — trainings, drills, event thresholds, manual validations
  • Three tracking boards — In Training (still boxes to tick), Ready (all steps cleared, assignment available), Assigned (operational)
  • Visible progress — progress bar and per-step badges. An officer spots the blocker at a glance.
  • Double gate — interview dossier validated by a recruiter AND integration steps all checked. The path is deliberately slow — it's an earnestness argument.
Recruit Tracking board in "In Training" mode: recruit rows with progress bar across mandatory steps, colored badges per training completed, assignment icon greyed out until progress is complete.
You set the bar. The tool enforces it.

For the recruit, home becomes an integration GPS.

A new member joining a gaming org usually DMs someone asking "so… what am I supposed to do?". Game Org answers for them. As long as a member sits in recruit status, their home page doesn't show the standard profile — it shows a dedicated widget: step checklist, live progress, event counter, direct CTA to request training. They always know what's left to tick. The day they're assigned, the widget quietly vanishes and the standard home takes over — silent transition, no action on their part.

  • Dedicated home widget for recruits — auto-swap on status detection (recruit grade + no section)
  • Live checklist — each step flips from "pending" to "validated" as it happens, no refresh
  • Embedded CTA — direct "Request training" button takes the recruit into the right Training module
  • Automatic switch — on assignment day, standard home. The recruit does nothing, they don't even notice.
Recruit home: colored recruit header up top, central integration widget with step checklist (trainings, events), state icons next to each step, Request training CTA.
No more "so what am I supposed to do?". Their home tells them.

The interview dossier — you build it. Without writing a single line.

Most tools force their questionnaire on you, or bounce you off to a Google Forms disconnected from everything else. Game Org ships a built-in form studio: you assemble your interview dossier question by question, drag and drop, without touching a line of code. Ten field types, sections, validation rules, a real-time preview of exactly what the recruiter will see. And you're not capped at one form — you create as many as you have types of recruitment, each with its own questions.

  • Drag and drop, zero code — add, reorder, duplicate or delete each question with the mouse; the section separator structures long dossiers
  • Ten field types — short answer, paragraph, email, link, yes/no, single choice, multiple choice, date, integer, decimal — each with its own rules (required, min/max, options, placeholder)
  • As many forms as you need — one dossier for pilots, another for infantry, a lighter one for express recruiting: create them without limit, set one as default, archive the rest
  • Live preview + ready-made templates — switch to "Preview" to see the recruiter's exact form; start from a duplicable Game Org template instead of a blank page
Form studio in edit mode: a column of question cards reorderable by drag and drop (short answer, dropdown, yes/no), a properties panel for the selected field, an Add question button at the bottom, an Edit / Preview toggle at the top.
Your org, your dossier. Ten field types, drag and drop, live preview — without a single line of code.

FAQ

Frequently asked questions

How does a candidate actually enter the pipeline?

They join your Discord server. That's it. The Game Org bot spots their arrival, grabs their Discord identity and current handle, automatically creates an applicant in "New" status, and makes their card appear live on every connected recruiter's screen — nobody has to refresh anything. The candidate fills in nothing, signs nothing, creates no account. Qualification happens on Discord, in your usual channels — where they already are. The recruiter then fills in the interview dossier when they have the info.

How do the Welcome Bot and Recruitment work together?

They're two floors of the same entrance. The Welcome Bot is the automatic door: it greets every newcomer on Discord, has them fill in your pre-form, sorts them and assigns the right role — no human intervention. Recruitment takes over in depth: the recruiter picks up the candidate, with their welcome answers already attached to the dossier, runs the interview and then drives integration. One qualifies at scale on arrival, the other recruits in depth. And nothing gets re-entered: the Welcome Bot's pre-form lands straight in the dossier the recruiter opens. You can use Recruitment on its own, but plugged into the Welcome Bot it starts every dossier with context.

Someone previously rejected comes back under a new handle: what happens?

Returnee matching runs on the Discord ID, which doesn't change when the handle changes. The bot recognizes the person on arrival, reattaches their past history to the new card, and the "Re-application" tag shows up automatically. The recruiter opens the history and sees every past dossier: rejections, Friendly status, past memberships. The tag is neutral — it just says the person has applied before, not a verdict. Up to the recruiter to re-read the history before deciding. Useful both for catching problematic returnees and for warmly welcoming those coming back for good reasons.

What's "Friendly"? How is it different from a rejection?

"Friendly" is a third path between accept and reject. The person doesn't join the org as a member — no grade, no section assignment, no access to private internal channels. But the relationship isn't closed: they stay in your base, their dossier is preserved, they keep a Discord role of Friend of the org. Handy for players from an allied org you meet at events, old members who left on good terms, a member's close friends, profiles without the time or appetite for full engagement. You don't have to choose between "we take them in" and "we show them out".

What counts as a "mandatory integration step"?

A step your org decides a recruit must clear before joining an operational section. Common types: an internal training to follow (e.g. org rules onboarding, combat training, section-specific training), a practical drill, a minimum number of events attended (e.g. at least 5), a mid-path interview with an officer. You define the list, the order, and whether each step is mandatory or optional. As long as a mandatory step is unchecked, the recruit stays in the "In Training" board with visible progress. The day it's all checked, they move to "Ready" and assignment unlocks.

What happens the day assignment is called?

An officer clicks the assignment icon in the "Ready" board (clickable only because every mandatory step is validated), picks the target section and grade, confirms. The action doesn't create a member directly — it creates a promotion request that lands in the HR module queue. An authorized HR officer validates it, the promotion goes live, the matching Discord role is applied, the recruit loses their recruit status. On the home side: the integration widget vanishes, the standard member dashboard takes over. The transition is silent — the recruit does nothing, they don't even notice.

Can you create several different application dossiers?

Yes, as many as you want. The built-in form studio lets you build each interview dossier by drag and drop, with ten field types (short answer, paragraph, email, link, yes/no, single choice, multiple choice, date, integer, decimal), section separators and per-field validation rules. Nothing limits you to a single form: you build one per type of recruitment — pilots, infantry, express recruiting for an event — set one as default, and archive the ones no longer in use. A real-time preview shows exactly what the recruiter will see, and you can start from a duplicable Game Org template instead of a blank page.

And how does it look in practice?

See how Game Org takes shape inside your guild.

Cross-gameWelcome BotYour recruits onboard themselves on Discord — your flows, your questions, the right role assigned automatically.Explore Cross-gameHuman resourcesPromote, validate, decorate, benchmark — in a single tooled console.Explore Cross-gameTrainingCourse catalog, registration workflow, chained prerequisites, in-app learning material.Explore Cross-gameSkillsMembers × skills matrix, fully custom hierarchy, automatic promotion, evaluation rights scoped by role and section.Explore Cross-gameEvents & calendarPlan once, publish to Discord, bidirectional signups — in a single tool.Explore Cross-gameMission ControlFrom the general order to each player's personal briefing — the op gets built once.Explore Cross-gameInsightsA command cockpit in six angles: engagement, members, operations, sections, decisions, events.Explore Cross-gameMiraYour Game Org copilot: a real face teaches you the app on video, an AI guides you day to day — and knows your whole org with Premium.Explore Cross-gameDiscord SyncYour members already live on Discord. So do your roles, your announcements, your signups.Explore Cross-gameSecurityGranular rights, per-org tenancy, no password to steal.Explore Add-on Star CitizenStar Citizen FleetDigitize hangars, aggregate collective power.Explore Add-on Star CitizenMission Control Star CitizenFrom the briefing to every gunner's brief — operations built seat by seat.Explore

Stop losing candidates between Discord and a spreadsheet.

Create your Game Org space, connect the bot to your Discord server, set your integration steps, and watch your pipeline fill itself. Zero candidate friction, long memory of returnees, adaptive recruit home. No demo gate, no sales form — the product is self-serve as soon as your org is registered.

Deploy for free