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. A server can keep up to 50, and between them they cost Discord's command budget nothing extra, because they all share one command.
Where the boundary is
| Use | Reach for |
|---|---|
| Up to 50 saved answers, made in Discord in seconds | Tags: one shared /tag, nothing registered with Discord |
| A handful of real commands (up to 10) with an action list | Custom Commands |
| Something that happens with no command at all | Automations |
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
Switch it on
Community → Tags.
Create one
On the dashboard, or with
/tags createin Discord, which opens a form for the text when you don't type it into the command.Write the answer
A plain message by default. Switch to an embed when a tag deserves one.
Set who can use it
Channel and role allow- and block-lists (a category covers its channels and their threads), an NSFW tag switch and a cooldown per user, per channel or for the whole server.
Two names per tag
The command name is what members type (up to 40 characters, spaces allowed). 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 (up to 5) give one answer several names, and a claim system stops tags going stale with the member who wrote them: when a tag's owner leaves the server, /tags claim hands it to somebody else. Claiming takes the right to create tags, and a tag made on the dashboard can only be claimed by staff with Manage Server.
Where the answer goes
| Output | Behavior |
|---|---|
| Reply in the channel (default) | Everyone in the channel sees it. |
| Private reply | Only the person who used the tag sees it. |
| Direct message | Sent to their DMs; the channel gets a quiet confirmation. |
| Post in a specific channel | The response is posted in one channel wherever the tag is used. A restricted tag. |
A reply or a channel post can also delete itself (up to 60 minutes later) and carry up to 5 reactions. /tag also takes a target (reply to somebody), args (text appended into the tag) and hide (force it private for this one use).
Settings
- Who can create tags
- Everyone (the default), Only these roles or Staff only. Anyone who can manage the server always can; this only governs Discord.
- Tags per member
- How many tags one member may own through the commands (3 by default, up to 50). Tags made on the dashboard don't count.
- Tags belong to whoever made them
- On by default: only the owner (or your staff) can edit or delete a tag in Discord. Off makes tags a shared, wiki-style pool.
- Members can claim abandoned tags
- On by default. See claims above.
- Answer /tag privately by default
- Off by default. On, every
/tagreply is shown only to the member who ran it, as if they had passedhide. Tags that DM or post in their own channel are unaffected. - Logging
- Tags made, edited, claimed and deleted in Discord, and, if you want it, every use. A tag made on the dashboard is logged by Logging's Arclo category instead.
Commands
/tag <name> [target] [args] [hide]EveryoneSends a saved tag. The server's answer to a question it keeps being asked.
/tags create <name> [content] [category]EveryoneSaves a new tag. Opens a form for the text when none is typed.
/tags edit <name> [content]EveryoneRewrites a tag. Owners only, unless ownership is switched off.
/tags delete <name>EveryoneCannot be undoneDeletes a tag. Owners always may; staff may delete any tag.
/tags info <name>EveryoneWho owns a tag, how often it's used, and where it ranks.
/tags list [member] [category] [page]EveryoneLists this server's tags, one member's, or one category's.
/tags alias <name> <alias> [remove]EveryoneGives a tag another name to answer to, or takes one away.
/tags claim <name>EveryoneTakes 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.