Request workflow
Start with the short intake: what you want the bot to do, what should feel better, your timeline, and your project preferences.
Support
Support Guide
You do not need Discord IDs, channel IDs, role IDs, or bot artwork before starting. The first intake asks basic questions about the bot idea and what should feel better for your server. We will ask for setup details later only when the project needs them. Do not send bot tokens, passwords, private API keys, payment card numbers, or credentials.
Workflow docs
Support docs for the parts you may touch later.
After the deposit
Stripe confirms payment, we email a sign-in link, and you use the client portal to complete the first intake.
Bot ownership and hosting
Choose whether you prefer us to manage the Discord application and hosting, client ownership, or a shared handoff.
Safe setup
Never send bot tokens, passwords, API keys, payment card numbers, or private credentials through the website.
Optional assets
Artwork, banners, brand colors, embeds, and bot personality can be collected later if they matter to the build.
Handoff expectations
Handoff, support, maintenance, and future changes are confirmed in the final plan before build starts.
Later setup details
Discord IDs, only when we ask for them.
These steps are here for support and handoff. They are not required before you start the request intake.
1
Enable Developer Mode
In Discord, open User Settings, go to Advanced, and turn on Developer Mode. This reveals Copy ID in right-click menus.
2
Copy the server ID
Right-click the server icon, choose Copy Server ID, and save that numeric value when we ask for setup details.
3
Copy owner and admin user IDs
Right-click the owner and setup admins, choose Copy User ID, and list the people who can approve bot behavior when needed.
4
Copy important channel IDs
Right-click channels used for logs, tickets, staff, onboarding, announcements, premium access, or restricted commands.
5
Copy important role IDs
Right-click roles used for staff, members, premium access, onboarding, moderation, events, or custom commands.
6
Prepare bot profile assets
If bot artwork becomes part of the scope, prepare a square profile picture and optional wide banner image as PNG, JPG, GIF, or WEBP files.
Visual click paths
Discord click paths for later setup details.
These illustrative walkthroughs show where to click in Discord. They use mock server data so private community names, users, channels, and IDs are not published.
Enable Developer Mode
User Settings -> Advanced -> Developer Mode ON
Copy the server ID
Right-click server icon -> Copy Server ID
Copy owner and admin user IDs
Right-click owner or admin -> Copy User ID
Copy channel and role IDs
Right-click channel or role -> Copy ID
Never paste bot tokens or credentials
Tokens and API keys are credentials. The first intake asks for project details only. If a special ownership model is needed, choose that preference in the intake so access can be handled after review.
Right-click items in Discord
Use Copy ID, not display names
Confirm you can approve bot setup
Later setup checklist
Server ID
Owner/admin Discord user IDs
Important channel IDs
Important role IDs
Feature list
Desired bot personality or style
What the bot should and should not be allowed to do
Launch notes
Optional bot name/avatar/banner ideas