Tags

Save your server's stock answers once and recall them with /tag — plain messages by default, with aliases, restrictions and four ways to deliver them.

On this page

A tag is a saved answer with a name. /tag rules posts your rules summary; /tag appeal posts the appeal instructions. Hundreds of them cost nothing, because they all share one command.

Where the boundary is

UseReach for
Hundreds of saved answers, made in Discord in secondsTags — one shared /tag, nothing registered with Discord
A handful of real commands with an action listCustom Commands
Something that happens with no command at allAutomations

There are no trigger words

An auto-responder already exists: an automation on message contains that sends a message. A second one here would be a second place to look when a server answers something twice.

Creating a tag

  1. Switch it on

    Community → Tags.

  2. Create one

    On the dashboard, or with /tags create in Discord, which opens a form.

  3. Write the answer

    A plain message by default. Switch to an embed when a tag deserves one.

  4. Set who can use it

    Channel and role allow- and block-lists, plus an NSFW switch.

#support

rileyToday at 09:14

how do I get the color roles?

ArcloBOTToday at 09:14

Head to #roles and pick one from the color menu. You can change it as often as you like — picking a new one replaces the old.

A plain message by default — which is what makes a tag read as an answer rather than as a bot post.

Two names per tag

The command name is what members type. The label is what the tag is called on the dashboard and in the list — leave it blank and it follows the name. That way a tag named r can be listed as Server rules.

Aliases give one answer several names, and a claim system stops tags going stale with the member who wrote them.

Where the answer goes

OutputBehaviour
ReplyA normal reply in the channel. The default.
PrivateOnly the person who ran it sees it.
DMSent to them directly.
ChannelPosted to a channel you named, wherever it was run.

/tag also takes a target (reply to somebody), args (text appended into the tag) and hide (force it private for this one use).

Commands

  • /tag <name> [target] [args] [hide]
    Everyone

    Sends a saved tag — the server's answer to a question it keeps being asked.

  • /tags create <name> [content] [category]
    Everyone

    Saves a new tag. Opens a form for the text when none is typed.

  • /tags edit <name> [content]
    Everyone

    Rewrites a tag. Owners only, unless ownership is switched off.

  • /tags delete <name>
    EveryoneCannot be undone

    Deletes a tag. Owners always may; staff may delete any tag.

  • /tags info <name>
    Everyone

    Who owns a tag, how often it's used, and where it ranks.

  • /tags list [member] [category] [page]
    Everyone

    Lists this server's tags, one member's, or one category's.

  • /tags alias <name> <alias> [remove]
    Everyone

    Gives a tag another name to answer to, or takes one away.

  • /tags claim <name>
    Everyone

    Takes over a tag whose owner has left the server.

Why two command slots

Discord allows a command to take options or subcommands, never both. Folding the verbs into /tag would make every use read /tag show name:…, and recalling a tag has to stay the fast path.

Still stuck? Ask in the support server — somebody there has almost certainly configured this before.