Y
youToday at 4:32 PM
@Bond set up a support area: a private ticket log only the staff roles can see, and a /ticket command members can run to open one
Free to start. Nothing to configure.
Manage your server by just talking to it.
Mention @Bond, describe the change, and it plans it, asks before anything it can't undo, then does it in your server.
761M tokens of work done for servers so far.
Today
BondAPPToday at 4:32 PM
Before I change anything, here is the plan. I read the server first: you have three staff roles and no Support category yet.
- 1.Create a Support category and deny @everyone the View Channel permission on it.
- 2.Add #ticket-log inside it, visible to Moderator, Support and Admin.
- 3.Register /ticket so it opens a channel named after whoever runs it.
Nothing existing is deleted or renamed.
BondAPPToday at 4:33 PM
Created category Support
Denied View Channel to @everyone on Support
Created channel #ticket-log
Granted access to @Moderator @Support @Admin
Registered command /ticket visible to everyone
This is the shape of a real run. Longer jobs use Ultra.
How it works
Ask. Plan. Approve. Run.
- 01
Ask
Mention Bond in any channel and describe the change in your own words.
- 02
Plan
It reads the server first, then states what it will create, change and remove.
- 03
Approve
Deleting anything asks first, on the exact channel, role or message Bond resolved.
- 04
Run
It calls the same Discord APIs you would reach through Server Settings.
Examples
What you actually type.
Other bots generate a new server. Bond edits the one you have.
It works in the server you already have.
Add Bond, then ask it for something.
It works in the server you already have. Ask it for one small thing first and see what it does with it.