Apply for Beta Access
How The Roleplay Bot private beta application process works, start to finish.
Before applying
The beta is built for structured Discord RP organizations, not individual testers. Before you apply, make sure your organization can offer:
- Own or manage a Discord organization — a real server, not a personal test server.
- An active staff team — a real rank hierarchy with people actually running it day to day.
- Willingness to test features — beta slots are most useful when a server actually runs the platform rather than installing it and leaving it idle.
- Willingness to provide feedback during the beta — beta access is a two-way arrangement. We're looking for organizations that will tell us what's working and what isn't.
The application process
Step 1 — Submit your application
Sign in with Discord and fill in the application form on this page. Signing in is how we know who applied — we ask for nothing else from your account.
Step 2 — The team reviews your organization
A reviewer looks over your application — this is a manual, human review, not an automated approval.
Step 3 — If accepted, you'll receive beta access instructions
You'll be told directly in your application thread (or by DM), along with everything you need to invite the bot and get started.
Step 4 — Setup and testing begins
Invite the bot, run Quick Setup, and start testing the features that matter most to your organization.
Information to include in your application
Fill in every field in the #apply-for-beta template — incomplete applications take longer to review:
- Organization name
- Organization type — police, military, fire/EMS, government, general RP, or another structured Discord operation
- Server invite — so reviewers can see the community for real
- Owner contact information — your Discord username, and confirmation you own or manage the server
- Member count
- Current management tools — whatever bots, spreadsheets, or forms you're using today
- Current challenges — what isn't working with your current setup
- Why you want beta access
- Willingness to provide feedback — beta access depends on active participation, not just installing the bot
After acceptance
Once your organization is accepted into the beta, here's what changes:
- Access to the beta Discord — where the team and other beta organizations are directly reachable.
- Support resources — setup help and guidance getting your organization onto the platform.
- Bug reporting channels — report anything broken as you find it; real, in-progress reports are more useful to us than a summary at the end.
- Feedback channels — share anything from a confusing workflow to a missing feature.
- Direct communication with the platform team — and a real say in what ships next, since beta feedback directly shapes future updates.