Talk to unreel about bots.
No forms, no inboxes. Just Discord. DM him with what hurts in your server, and if it is interesting enough it can quietly turn into a build.
Write to him like you would explain the problem to staff. No need for technical diagrams. Clear description of what hurts in your server is enough.
A normal Discord conversation is enough to start a project.
There are no forms here. Each option is just a different way to shape the first message so it is easy to understand.
- Send a single DM that contains the short version of what hurts in your server.
- Mention what the bot should roughly handle – tickets, staff tools, slow flows.
- You do not need perfect wording. Clarity wins over fancy language.
- Write 3 to 7 bullets that describe what you expect the bot to do.
- Add how many staff touch tickets or panels so scale is obvious.
- If anything is weird, like cross-channel flows, call it out directly.
- Questions will come back in Discord instead of a formal doc.
- Flows are shaped around real behaviour of your channels, not a template.
- If things line up correctly, the conversation moves into an actual build.
Situations where a DM to unreel actually makes sense.
A few focused panels that staff can explain in one breath feel better than a thick interface nobody touches.
Contact makes sense when you care that the bot only surfaces what staff actually need to see during real incidents.
If you have been burned by messy perms and want something predictable, a DM is the right opening move.
Shape the message you will paste into Discord.
This form does not send anything on its own. It just gives you a calm place to write the DM, then you copy it and send it directly to @toounreel.
It stays light. A small loop, not a pipeline.
You are not signing up for some heavy intake process. It is just a short sequence where the idea is either sharpened or politely parked.
You explain what hurts: tickets get messy, staff tools feel heavy, or flows are impossible to follow at three in the morning.
The DM turns into small sketches of flows and states. What happens first, what has to never break, what the rest of the team should see.
If the work is a good fit and the timing makes sense, it moves forward into an actual build. If not, you still leave with clearer language.
Tiny answers before you ever send the DM.
A single clear message is enough to start. If the fit is wrong, the thread can just stay a thread. If it is right, it turns into a very opinionated build.