At a glance

• Command: /welcome <subcommand>

• Typical users: server staff / managers as allowed by your Command Permissions.

• Capabilities:

  • Enable/disable public welcome posting

  • Configure the welcome channel and the message template (with placeholders)

  • Preview how a welcome will look

  • Inspect or reset welcome settings

• Placeholders: {user} and {server} are supported (and the dashboard notes a special line-break token for premium-style formatting).

Commands

Each command below includes: purpose, syntax/options, examples, who can run it, and notes/tips.

/welcome enable

Purpose — Turn welcome posting on so the configured welcome message will be sent for new members.
Syntax

/welcome enable

Example

/welcome enable

Who can run it — Staff with the appropriate dashboard/command permissions.
Notes / tips — Enables the welcome pipeline (the server will begin posting welcome messages to the configured channel). If you staged a welcome message in the dashboard, ensure the channel and template are saved before enabling.

/welcome disable

Purpose — Turn welcome posting off so no welcome messages are posted.
Syntax

/welcome disable

Example

/welcome disable

Who can run it — Staff.
Notes / tips — Use this to pause welcome posting during edits, testing, or migrations. The dashboard and staging flows are unaffected by disabling; you can continue to edit and preview while off.

/welcome setchannel <channel>

Purpose — Set the destination channel where welcome messages will be delivered.
Syntax

/welcome setchannel channel:#welcome

Example

/welcome setchannel channel:#welcome

Who can run it — Staff / managers.
Notes / tips — The configured channel becomes the default destination for both public welcome posts and for the dashboard preview. Make sure the bot has Send Messages and Embed Links in that channel.

/welcome setmessage <message>

Purpose — Save a custom welcome message template. Templates may include placeholders.
Syntax

/welcome setmessage message:"Welcome {user} to {server}! Check #rules."

Example

/welcome setmessage message:"Welcome {user} to {server}! Grab roles in #roles and introduce yourself."

Who can run it — Staff.
Notes / tips

• Supported placeholders: {user} and {server} — they will be resolved when the welcome posts.

• The dashboard also supports premium-style line breaks (\n alternative noted in the docs) and provides an editor/preview. Use the dashboard preview to validate how the template renders on desktop and mobile.

/welcome preview

Purpose — Send a test welcome message (a preview) to the configured channel so staff can confirm rendering and placeholders.
Syntax

/welcome preview

Example

/welcome preview

Who can run it — Staff.
Notes / tips — Use this before enabling or after edits. The preview helps confirm avatar rendering, placeholder substitution, and any button/CTA behavior (if you use a button destination in the template).

/welcome settings

Purpose — Display the current welcome configuration: enabled state, the welcome channel, the saved template, DM follow-up settings and cooldowns.
Syntax

/welcome settings

Example

/welcome settings

Who can run it — Staff.
Notes / tips — Useful for audits and to confirm whether DM follow-ups and cooldowns are set. It mirrors the dashboard settings panel.

/welcome reset

Purpose — Return the welcome system to default values (clears custom message, resets channel and options).
Syntax

/welcome reset

Example

/welcome reset

Who can run it — Staff / admins.
Notes / tips — Use this when you want to wipe the welcome configuration and start fresh. Consider staging a replacement message in the dashboard before resetting if you want to avoid downtime.

Dashboard staging & previews

The dashboard uses a stage → preview → push flow for welcome messages and embeds. You can compose the message in the dashboard, preview it (including the embed and any button), and then push it live — or use the /welcome commands to set the same values directly. Staging keeps the message local to the dashboard until you confirm it, which reduces accidental public posts.

Best practices & recommendations

• Keep public welcomes concise. Put long onboarding instructions behind a button or a pinned message to avoid wall-of-text welcomes.

• Use placeholders responsibly. {user} and {server} personalize messages; avoid injecting raw Markdown or links that could be exploited by malformed templates. Confirm with /welcome preview.

• Enable DM follow-ups with care. If your server sends a DM to new members, ensure the cooldown is set so members aren’t spammed (and be mindful of moderators’ privacy policy).

• Stage and preview in the dashboard when designing complex embeds, images, or buttons. The dashboard’s preview helps catch mobile/desktop rendering differences.

Troubleshooting

• Welcome messages not posted — verify the welcome system is enabled (/welcome enable) and that a channel is configured (/welcome setchannel). Ensure the bot has Send Messages, Embed Links, and Send Messages in Threads if needed.

• Placeholders not resolving — confirm you used exactly {user} and {server} in the template. Use /welcome preview to validate.

• Buttons/CTAs not functioning — if you included a button that links to a channel or a destination URL, check the destination is valid and the bot has permissions to act where needed. Stage and preview the button in the dashboard first.

• Bot DMs not received — some users block DMs or have server privacy settings; DM follow-up may fail for those users. Consider enabling DM receipts in the dashboard or configuring a fallback public message.

Quick cheatsheet

/welcome enable # Turn welcome messages on
/welcome disable # Turn welcome messages off
/welcome setchannel channel:#welcome
/welcome setmessage message:"Welcome {user} to {server}! Grab roles in #roles."
/welcome preview # Send a test welcome to the configured channel
/welcome settings # Show current welcome settings
/welcome reset # Reset welcome config to defaults