How onboarding works
Onboarding is done for you. We train the agent on your game and stand it up in your server, and you approve each step. Many studios are live within a day or two of kickoff.
The steps
| Step | Who does it | What happens |
|---|---|---|
| 1. Kickoff | You and us | A short call to confirm your game, your server, and who on your team will run the agent. |
| 2. Training | Us | We train the agent on your published game so it knows the game’s data. No files to prepare. |
| 3. Invite | You | You add the agent to your server with an invite link we provide. |
| 4. Configure | You | You set the persona, pick channels, connect any source code and design docs, and tune spoiler rules in the dashboard. |
| 5. Staging test | You and us | The agent goes live in one private channel so your team can ask it real questions. |
| 6. Go live | You | You open it up to the channels your players use. |
Steps 4 through 6 are yours to control from the dashboard, and you can change any of it later.
What we need from you
Very little. We train the agent on your published game ourselves, so there are no files to hand over and no data export to prepare. At kickoff we confirm a few things:
- The game. The exact title and platform you want the agent to know.
- The server. Which Discord server it joins, and whether you want it in a staging server first.
- The owners. The people on your team who should be able to configure it and read analytics.
- The sources. Any source code or design docs you’d like the agent to learn from, beyond the published game.
Connecting your sources
The agent always learns from your published game. You can also connect your source code and design docs for deeper answers: a GitHub repository for exact mechanics, and Notion, Google Docs, or Atlassian for intent and wording. Connect them yourself under Sources in the dashboard, during onboarding or later. See how the agent is trained.
Adding the agent
When you’re ready for step 3, you’ll get an invite link. Opening it brings up Discord’s standard authorization screen, where you pick your server and grant the agent the channel permissions it needs: viewing and posting in the channels you choose. You narrow where it looks with the channel allowlist right after. The message-content access that lets it read questions is enabled as part of onboarding, so it isn’t something you set on this screen.
Adding a bot needs the Manage Server permission on Discord, so make sure whoever clicks the link has it. Most server admins do.
Going live
Before you open the agent to players, spend a day with it in a staging channel. Ask it the questions your community asks most and confirm the answers read the way you want. When the persona and the answers feel right, add your public channels to the allowlist. That’s go-live.
Your first week covers what to watch once players start asking.