Using ReactionBot AI

You do not need to use exact slash command names or option labels when speaking to ReactionBot AI.

You can describe the result you want in the same way you would explain it to another moderator.

For example: “Stop people from using the fire emoji in this channel.”

Start by clearly describing what you want ReactionBot to do.

Common supported actions include blocking an emoji, unblocking an emoji, limiting reactions, restricting a member, creating an Allow Only rule, and removing existing reactions.

Direct wording helps ReactionBot separate an actionable request from ordinary conversation.

Include the emoji, member, channel, or rule that should be affected.

For standard emojis, you can often use either the emoji itself or a common name such as “fire emoji.”

For members and custom emojis, direct Discord mentions or the actual custom emoji are generally the clearest options.

Tell ReactionBot whether the action should apply to the current channel, another channel, or the entire server.

Use phrases such as “in this channel,” “in #general,” “here,” “server-wide,” or “across the entire server.”

Server-wide actions may require ReactionBot Premium even when the same action is available for free at the channel level.

Timed requests should include a clear duration whenever the supported feature allows one.

For example: “Restrict @User from reacting in this channel for two hours.”

Avoid vague phrases such as “for a while” when the exact duration affects how the rule should be created.

When limiting reactions, include the exact number of reactions each member should be allowed to add.

For example: “Limit everyone to one reaction per message in this channel.”

A request such as “limit reactions here” may be incomplete because it does not specify the maximum.

When removing existing reactions, include a supported date range when you do not want ReactionBot to scan the entire available history.

For example: “Remove all fire reactions from this channel posted today.”

You can also use wording such as “from the last seven days” when supported by the equivalent removal feature.

ReactionBot AI can understand many common emoji descriptions, such as “fire emoji,” “puke emoji,” or “laughing emoji.”

Using the actual emoji is usually the clearest option when several emojis could match the same description.

Custom Discord emojis should normally be inserted directly into the request.

Use a Discord member mention when asking ReactionBot to restrict or unrestrict someone.

A direct mention helps avoid confusion when several users have similar usernames or display names.

For example: “Stop @User from reacting in this channel for one hour.”

Use the current channel when you say “here” or “in this channel.”

Mention a specific channel when the action should apply somewhere else and the feature supports selecting another channel.

For example: “Block 🔥 in #general.”

Your message can contain normal conversation and a supported action at the same time.

For example: “How are you? Also block the fire emoji in this channel.”

ReactionBot can respond to the conversational portion while separately processing the moderation instruction.

You can include more than one supported action in a single request.

For example: “Block 🔥 and limit members to one reaction per message in this channel.”

Each action is separated and checked independently before ReactionBot reports the result.

Words such as “first,” “then,” and “after that” can help explain the intended order of multiple actions.

For example: “First unblock 🔥, then make it the only allowed reaction in this channel.”

Always review the response because each action may still be validated independently.

ReactionBot will respond after interpreting and validating your request.

The response may confirm a completed action, explain a failed action, request clearer information, or identify a missing permission or plan requirement.

Read the complete response when your message contains multiple actions.

A message containing several actions may produce a mix of successful and unsuccessful results.

For example, a channel-based block may succeed while a server-wide limit fails because Premium is not active.

You can resend only the failed instruction after correcting the missing detail or requirement.

ReactionBot may be unable to continue when the request does not clearly identify the target, scope, duration, limit, or date range.

A message such as “restrict him” may be rejected because no member or scope can be confirmed.

Resend the request with the missing information included.

If ReactionBot selects the wrong scope or misunderstands part of your request, correct the setting using a clearer AI message, the equivalent slash command, or the dashboard.

For example: “Remove that channel rule and block 🔥 server-wide instead.”

Review the new confirmation before making additional changes.

Slash commands are useful when you already know the exact action and want direct control over each option.

They are also helpful when a feature has not yet been connected to ReactionBot AI.

Standard commands do not consume ReactionBot AI requests.

The dashboard is useful for reviewing existing configuration and making precise changes across several settings.

It may be easier than natural language when configuring many channels, users, rules, or advanced options at once.

ReactionBot AI, slash commands, and the dashboard all work with the same underlying ReactionBot systems.

Keep related actions together, but split very large or unrelated configuration changes into separate messages.

Include the exact emoji, member, channel, scope, duration, limit, or date range whenever it matters.

Always review the confirmation before assuming the requested changes were applied correctly.

Continue to Supported Actions to review every Reaction Control action currently available through ReactionBot AI.