How to use the discords.ai bot, step by step

Run /list in any channel of the server you want listed.

Fill in the form that opens.

The description is what people read in the directory, so write it for somebody who has never heard of your server. The invite must not expire, or the listing breaks the day it does.

Wait for review.

Every listing is read by a person before it goes live. You get a direct message either way, and a rejection says what to change.

Run /stats. Add a range to look further back.

Read the reply.

Views are how many people opened the listing. Joins are how many of them actually followed the invite, which is the number that matters.

Run /invite in any channel.

Any member can run it. The reply is posted where everybody can see it, not just you.

The bot posts the listing's invite, with the title linking to the listing itself.

If the listing has no invite recorded, it says so and links you to the dashboard.

It also tries to make one from the server first, and stores it if that works.

Run /invites.

Compare the uses against where you posted each link.

The point is not the total. It is finding the one link doing the work, so you can stop paying for the others.

Run /bump.

Anyone in the server can do this, not only staff.

Read what comes back.

Set up a reminder so the next one is not missed.

The cooldown is the whole game: a listing bumped twice a day outranks one bumped twice a week. Bump Reminders tells you the moment it expires, and Auto Bump does it for you on Gold and Platinum.

Run /members.

Read the trend, not the number.

A snapshot is taken once a day, so this starts being useful a week after the bot joins and gets better from there.

Run /activity.

Compare against member count.

A big server nobody talks in ranks worse than a small one that does, both here and with the people who join.

Run /vote.

Share the link.

Each person can vote once a day. Votes and bumps are separate: bumps move you up by recency, votes by support.

Run /review with a rating and a comment.

It appears on the listing.

One review per person. Running it again edits the one you left.

Run /tools.

Read the state, not just the list.

It says which tools are on for THIS server and links to where each is configured.

Run /ticket.

Pick what it is about, and answer its questions.

/ticket opens from the server's first ticket panel and asks what the panel's button asks. If more than one of that panel's ticket types is switched on, it asks what you need help with first, in a menu only you can see. If the type has an opening form, its questions come next, and your answers go into the ticket for staff. With one type and no form, or a panel with no types, it opens straight away. If none of the panel's types is switched on, it says so and opens nothing. If the panel needs a role you do not have, or you already have as many tickets open as the server allows, it tells you before asking anything.

Talk in the private ticket that opens.

You, the staff roles set on that panel and on that ticket type, and anyone with Discord's Administrator permission (or, in a thread, Manage Threads) can see it in Discord. The server's dashboard managers can read it too, and so can discords.ai administrators, for support. When it closes, a transcript is saved and searchable from the dashboard for as long as the server's plan keeps transcripts.

Describe the server you want in one sentence.

Read the plan before anything is made.

Nothing is created until you confirm. This is the step to actually read - it only ever adds, but undoing forty channels by hand is a bad evening.

Confirm, or change the description and run it again.

Run /reminderchannel and pick a channel.

Leave the channel out to switch the Discord reminder off again.

Check the bot can post there.

Type /tag and start typing the name.

The list narrows as you type and shows the one-line description of each, so you do not have to already know what exists. Staff-only replies appear only for staff.

Pick one and send it.

It posts publicly, because the point is that everybody reading the channel gets the answer rather than only the person who asked.

If you get the name wrong, it suggests the near ones.

Being told a tag does not exist teaches nothing. Being told which three are close gets you there.

Run /poll with the question and at least two answers.

Four more answer boxes are there if you need them, and empty ones are ignored.

Pick how long it runs, or leave it.

A day if you say nothing. An hour to a month, which are Discord's own limits rather than ours.

That is it. Nothing has to come back to it.

This is Discord's own poll, not a bot counting emoji. It renders natively with a bar per answer, counts itself, stops at the time you set and announces the result on its own.

Only you can end it early.

The button is in the reply nobody else can see. It has to work this way: Discord offers End poll to whoever posted the message, and the one who posted it is the bot.

Run /balance. Name a member to see theirs.

Read it.

This currency exists only in this server. It is not site credits and cannot be moved between servers.

Run /daily.

Come back tomorrow.

The bonus is paid on the seventh consecutive day, not a little more each day, so the run is what pays rather than the streak number.

Run /shop.

Buy from the list.

The owner sets what is in it - roles, colours, emoji access, anything they have added.

Run /pay with a member and an amount.

It moves immediately.

There is no undo. Both balances change the moment it goes through.

Run /richest.

Read the top ten.

Run /grant with a member, an amount and a reason.

The reason is worth writing. It is what the log shows when somebody asks where this came from.

It is logged.

Run /suggest with your idea.

It is posted on the board with a number.

The number is what people use to refer to it afterwards.

People vote with the buttons.

Buttons rather than reactions, because the bot cannot see a reaction being added. Pressing the same side twice takes your vote back, and nobody votes on their own.

Wait. You are sent a message when it is answered.

Approved, denied, considering or implemented, with whatever reason staff wrote.

Run /suggestion with the number.

Read it. Only you see this.

Anonymity that any member could undo would not be anonymity, and one nobody could undo would make the board unmoderatable the first time somebody abused it.

Answer it with the Decide button on the board itself.

There is no command for deciding: the button is on the suggestion, so there is nothing to look up.

Run /giveaway start with the prize and how long it runs for.

A random seed is generated at this moment, before anybody has entered, and its fingerprint goes in the giveaway message. That ordering is what makes the result provable later: a seed made at draw time could have been regenerated until it named somebody.

Members press Enter.

No reactions. The bot has no way to see one, and a button answers instantly and privately.

Leave it. The draw happens on its own within a minute of the end time.

Run /giveaway reroll if a winner does not claim.

Whoever already won is excluded, a fresh seed is drawn and committed, and the reroll count is on the record so a giveaway rerolled four times says so.

Anybody can press How this draw works to see the seed and check it.

For requirements beyond one role - account age, time in the server, bonus entries - use the dashboard rather than the command.

Run /birthday with the day and the month.

There is no year to fill in. The server is told a date, not your age, and that is the whole design rather than a missing field.

Check it took.

Run /birthday on its own to see what this server has.

Nothing else is needed. Run it again with a different date to change it.

Run /birthday with remove set to True to take it back.

The row is deleted rather than hidden. What you told one server was never shared with any other.

Run /birthdays.

Read the list.

Soonest first, wrapping past December, so in late December January shows near the top rather than at the bottom. Nobody in the list is pinged by it.

Run /remind with how long, and what about.

30m, 2h30m and 3d all work. A bare number means minutes, the same as it does in /timeout, and the reply says the duration back in words so a wrong guess is obvious now rather than in two hours of silence.

Read the confirmation.

The timestamp renders in your own timezone, not the server's. Only you see this reply.

Wait. It arrives on its own.

Within a minute of the moment you asked for, never before it. The bot has no live connection to Discord, so a check runs every minute and that is the latency.

Add where: By direct message if you would rather nobody else saw it.

A private reminder is not shown to staff on the dashboard either. If your direct messages are closed to the server it cannot be delivered, and the channel is told that a reminder was due WITHOUT being told what it said.

Run /reminders.

Read the list.

Yours only, soonest first, and the times render in your own timezone. Only you see it.

Pick one from the menu underneath to cancel it.

The menu only ever offers your own.

Read anything that could not be delivered, then clear it.

Listed below the waiting ones with the reason, because this is the only place you would ever find out one failed. The button only appears when there is something to clear.

Run /meeting start in the channel the meeting is in, with a title if you like.

Read the notice the bot posts. Everybody in the channel sees it.

It says who started it, that messages posted here until it stops go into the notes, and links to how they are kept. Nothing posted before the notice is recorded. One meeting runs per channel at a time.

Hold the meeting as normal, and press Add a note to put something on the record yourself.

Anybody in the channel can add one, up to 1000 characters, and their name goes beside it. A meeting holds up to 200 notes, and one person can add up to 20 of them. Notes always arrive with their text, even if Discord does not give the bot the text of ordinary messages, so they are the part of the record that always works.

Press Stop, or run /meeting stop, when it is over.

The person who started it, staff or whoever runs the server can stop it; anybody else is told which rule refused them. The write-up usually lands within a minute. One that does not finish is tried again within 8 minutes, up to 3 attempts. A meeting left running stops on its own after 4 hours, with a notice, and so does one whose notice is deleted, at the next five-minute check.

Read the write-up.

On Silver and up it opens with a summary written by Claude, Anthropic's AI model, from the messages and notes: decisions, action items with an owner only where somebody was named, and open questions. On Free it lists the notes instead. Either way the button underneath opens the full transcript, and the meeting is listed on the Meeting Notes page of the dashboard.

Run /guide.

Work down the list.

It is ordered by what pays off soonest, not by what is easiest to build.

Run /help.

Read it.

Generated from the same list the bot registers with Discord, so it cannot drift out of date.

Run /privacy status.

It answers two questions: what you have already turned off, and what is actually held about you across every server. Only you can see the reply.

Read what is held.

Run /privacy optout and pick an area to turn something off.

Everything, or just activity counts, or just what is kept from your messages, or just presence. It applies across every server the bot is in, not only the one you ran it in.

Run /privacy optin with the same area to turn it back on.

Warnings and bans are not covered either way. They are a server's own record of something it did, so they stay, and /appeal is the route if you think one is wrong.

Run /report with the member and what happened.

Read what your report counted for.

Reports are weighted and counted once per person. The reply tells you the running total, so you can see it is not a button that bans people.

Nothing more, unless staff ask.

At the threshold the member is muted and a ticket opens where staff decide. The mute is not the verdict.

Right-click the message, then Apps → Report to moderators.

On mobile, press and hold the message instead.

Say what is wrong with it.

This carries the message itself, so staff read what was actually said rather than your description of it. That is the reason to prefer it over /report.

Run /role add with the member and the role.

They are told they have it, and why, if you give a reason.

Or /role temp, and say how long.

30m, 2h, 3d, 1w. The role comes off by itself on the next sweep, which runs every five minutes, so the length is a floor rather than an exact moment. Running it again on the same person and role moves the expiry rather than stacking a second timer.

If it is refused, read which ceiling it hit.

Discord answers the same 403 whether the bot's role is too low or yours is, and the two are fixed in completely different places. The reply says which one, and for the bot's it says to drag its role higher.

A role carrying Administrator can only be given by the owner.

Administrator is not one permission, it is all of them, including the ones that would remove whoever granted it. Handing that out is a deliberate act in Server Settings rather than one command.

/role info reads a role back in words.

What it lets people do, how many hold it, and whether the bot could hand it out at all. How many hold it needs the Server Members intent; if that is off it says so rather than reporting zero.

Run /ban with the member and why.

The reason goes to them, so write it as something you would say to their face.

They are told before it happens.

Once somebody is banned the bot no longer shares a server with them and Discord will not deliver a DM, so the notice has to go first. If appeals are switched on for bans, the link goes with it.

Only you see the reply. The log channel gets the record.

The channel does not need to watch somebody being removed, and a log line naming the moderator and the reason is worth more than an announcement.

Nothing of theirs is deleted unless you say so.

Pick delete_messages to take their recent messages with them, from the last hour to the last 7 days, which is as far back as Discord goes. Leave it empty and the default on the Moderator Commands page applies, which starts at nothing: a ban is exactly the case where somebody later wants to read what was actually said.

Run /unban and start typing their name.

The list is this server's real ban list, with the reason each was banned for, so you never have to go and find a user id. A user id typed by hand is a user id typed wrong.

They will need a new invite.

Lifting a ban does not put somebody back in the server. It only stops Discord turning them away.

Run /tempban with the member and how long.

3d, 1w, 30d. A bare number means minutes, and the reply says the length back in words so a slip is obvious.

They are told when they can come back.

Sent before the ban lands, because afterwards the bot no longer shares a server with them and Discord will not deliver a DM.

The unban happens on a sweep, not to the second.

Every ten minutes, on the same pass that lifts mutes which have run out. So the length is a floor rather than an exact moment.

They need a new invite.

Lifting a ban does not put somebody back in a server. It only stops Discord turning them away.

Run /softban with the member.

It bans and immediately unbans them.

That is how Discord deletes somebody's last seven days of messages in one call. The ban is the mechanism; the deletion is the point.

Check the reply if it says they are still banned.

If Discord takes the ban and then refuses to lift it, the reply says so plainly rather than reporting a soft ban. Unban them with /unban.

Run /mute with the member, and a length if you want one.

Leave the length out and it lasts until you lift it.

It does whatever your mute mode says.

Discord's timeout, your muted role, or both. A muted role is worth having: it can be scoped so somebody is silent in general and can still answer in their own ticket, which a timeout cannot do.

A mute with no length is a role, not a timeout.

Discord cannot hold a timeout open, so that half runs for its 28 day maximum and the role stays until you lift it. The reply says so rather than letting you find out in a month.

A timed mute comes off on a sweep.

Every ten minutes. Discord lifts its own timeout; the role is what needs the sweep, and without it a member muted for an hour on a Friday is still muted the following month.

Run /unmute with the member.

Both halves come off, whatever your settings say now.

A server that switched from a muted role to a timeout last week still has members carrying the role. Lifting only the currently configured half would leave them muted with nothing on screen to explain it.

They are told they can speak again.

Run /kick with the member and why.

They are told, and told they can come back.

That is the whole difference between this and a ban, and saying it is what makes a kick a warning rather than an ending.

Run /timeout and type the length the way you would say it.

30m, 2h, 3d, 1w. A bare number means minutes.

Check the reply. It says the length back in words.

On purpose: typing 30 and meaning thirty days rather than thirty minutes is the mistake that turns up in an appeal a month later, and this is where it is cheap to spot.

28 days is Discord's ceiling, not ours.

Ask for longer and it is capped there and says so. For longer than that you want a ban.

Run /untimeout with the member.

They are told it has been lifted.

Otherwise somebody sits out the rest of two hours they are no longer serving.

Run /purge with how many recent messages to look at.

Up to 100. Add a member to take only theirs, or some text to take only the ones containing it.

Above 25 it asks first.

There is no undo, and /purge 100 for /purge 10 is a slip anybody can make. It shows what it is about to do and waits.

Pinned messages are always left alone.

Somebody pinned that on purpose. A purge aimed at a spam run should not take the server rules with it.

Anything over 14 days old goes one at a time.

Discord's bulk delete refuses older messages outright, so those are deleted individually, which is slower. The reply says how many actually went.

Run /slowmode with how many seconds between messages.

0 switches it off. 21600 is Discord's maximum, which is six hours.

Do not expect to change it twice in a row.

Discord allows two channel edits every ten minutes per channel, and slowmode is a channel edit. The third is refused and the reply says so rather than leaving you wondering.

Run /warn with the member and what it was for.

The reason is sent to them, so write it as something you would say to their face.

They are told before anything happens to them.

That order matters: Discord will not deliver a message to somebody who no longer shares a server with the bot, and a kick is exactly what stops them sharing one.

You are told the count and what it reached.

While test mode is on it says what it WOULD have done and does nothing, so you can find out whether your steps are what you meant before they fire on a real person.

Run /modlogs and pick the member.

Somebody who has already left is not in the picker. Use the id option instead: turn on Developer Mode in Discord, right-click them anywhere their name appears and pick Copy User ID.

Read the first line before the entries.

It says how many entries there are and how many of them actually count. A warning a moderator took back, a report staff threw out and anything that ran in test mode are all shown, and none of them count.

Page through with Previous and Next.

Six at a time, newest first. Only you can see any of it, and the buttons keep working later - the page number is carried in the button itself.

Run /warnings with the member.

Read it. Only you see it.

It shows how many still count, what each was for, and any private notes. Expired and withdrawn ones are shown but do not count.

Run /note with the member and what to write.

A note is never shown to the person it is about and never counts towards an escalation. It is for the things that are not a warning but are worth knowing.

It appears on /warnings and on their member profile.

Run /lockdown, with a reason if you have one.

Every channel that is not already locked, not private, and not on your exempt list is silenced.

Read what it tells you.

It says what was locked and what was left alone, with a reason for each - a channel that was already locked is never touched, because opening it afterwards would undo a decision somebody made on purpose.

Deal with it. Then run /unlock, or leave it.

The automatic unlock is checked every minute, so it lands within one. Nobody has to be awake for it.

Run /unlock.

Every channel goes back to exactly what it was.

Not to allowed - to whatever it actually was, which for most channels is inheriting from the category. That distinction is the whole reason this is a tool rather than two permission changes.

Run /whois and pick the member.

Only you see the answer, every time. Reading somebody's record should not announce to the channel that you are doing it, and the panel never pings them.

Read the three columns across the top.

Account is how old the Discord account is and how long they have been here, which is the pairing that matters: a two-day-old account that joined an hour ago is a different proposition from a two-year-old one. Moderation counts only cases that were upheld. Support is tickets, with open ones called out.

Check Taking part before you assume the worst.

Reports made, notes written, suggestions, giveaways and their economy balance. Somebody with three reports against them and two hundred in the economy is a regular having a bad week, not a drive-by.

Right-click instead when you are already looking at them.

The same panel is on Apps in the right-click menu of any member or message. Use that when you are reading a ticket, and /whois when all you have is a name.

Right-click the member, then Apps, then Member profile.

A context menu rather than a command, because you are already looking at the person - typing an id you have to copy first is the difference between a panel that gets used and one that does not.

Read it. Only you see it.

Facts with their dates rather than a risk score. A score invites acting on arithmetic nobody can see, and is unfair exactly where being fair matters.

Nothing here comes from another server.

A record spanning servers would be a profile of a person rather than your own notes, which Discord's developer policy does not allow. The panel says so on its face.

Right-click the message, then Apps → Add community note.

Write the correction.

It appears in a thread on the message itself, where the people who read the message will see it. A note is not a report and counts towards nothing.

Members vote on whether it helped.

Notes that nobody finds helpful stop being shown.