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. If sensitive access is needed after review, we will arrange a separate secure handoff.
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. After you submit it, you will receive a response within 72 business hours.
Bot ownership and hosting
Choose whether you prefer us to manage the Discord application and hosting, client ownership, or a shared handoff.
Safe setup
Keep sensitive setup details out of intake forms. If they are needed later, we will arrange a secure handoff after review.
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.
Optional handoff setup
Client-owned handoff support can include a working bot, hosting setup, shared code workspace, update notes, and optional guidance for future changes.
Optional handoff workflow
Handoff details for teams that want client-owned setup.
Most projects can stay fully managed by Meowlyn Bots. When client-owned hosting or code access is part of the scope, we set up the bot and document how to get back into the hosting and code later. Sensitive access is handled through an agreed secure setup process, not the public intake form.
Bot app setup
We help set up the Discord bot app so it fits the ownership plan confirmed in your project scope.
Hosting login
The handoff can include the login path, status notes, restart steps, and hosting details for the server that runs the bot, often called a VPS.
Code workspace
The bot code can live in a shared code workspace, usually GitHub, so future changes are easier to review and support.
Future update workflow
Instructions can show how to open the server, check recent activity, make updates, run checks, and restart safely when handoff support is part of the scope.
Do not paste secrets, passwords, recovery codes, or account access details into intake forms or AI chats. Exact access, paid support access, and hosting/account costs are confirmed during review, then handled through a separate secure handoff when needed.
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.
Discord help
Turn on Developer Mode when IDs are needed.
These screenshots show where to click in Discord so you can enable Developer Mode and copy server, channel, role, or user IDs if we ask for them during setup.
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
Sensitive access comes after review
The first intake asks for project details only. If sensitive setup details are needed, we will arrange a secure handoff after the project has been reviewed.
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