Every server has a handful of answers it gives over and over: the rules link, the support hours, how to apply, where the FAQ lives. Custom commands let you define those once and let members pull them up on demand — so your team stops copy-pasting the same paragraph forever.
Trigger in, reply out
A custom command is a simple pairing: a trigger your members type, and the response CloudMod sends back. Define rules, apply, socials, ip — whatever your community asks for — and anyone can call it. The answer is always identical, always current, and never depends on a moderator being awake.
Plain text or a full embed
A reply can be a quick line of text or a formatted embed with a title, body and colour for the things that deserve to look official — your ruleset, a support notice, a welcome guide. Same command, as polished as you want it.
Cooldowns keep them from being spammed
Each command has a per-user cooldown, so nobody can machine-gun a command to flood the channel. It fires when someone genuinely needs it and quietly ignores repeat presses within the window.
Curated by admins, per server
Only admins define commands, so the list stays intentional — this isn't a free-for-all tag system that fills up with junk. And because it's a per-server plugin, each server in your network can carry its own set: your main community and a sub-server can answer to different commands from the same dashboard.
Not the same as auto-responses
Custom commands are deliberate — a member calls them by name. Auto-responses are automatic — they trigger themselves when a message matches a pattern. Use custom commands for "give me the info I asked for," and auto-responses for "react when someone mentions X." They complement each other; many servers run both.
Getting-started tip
Start with the three answers your team types most — rules, how-to-apply, and support — as text commands. Once you see which ones get used, upgrade the important ones to embeds so they read like official notices.