Welcome Automation — first impressions that scale

What it is
A template-driven welcome system that posts configured welcome messages to a channel, optionally follows up with a DM, and supports placeholders for {user} and {server}. The dashboard lets you stage a welcome message, preview it in the target channel, and confirm cooldowns / follow-up behavior before going live.

Key UI elements

• Welcome channel selector and Save channel control.

• Button destination / button label (optionally show a button on the welcome that members can click).

• Welcome message template textbox (supports placeholders and premium line breaks).

• Welcome embed preview, Stage Message, Stage Preview, and DM follow-up options with cooldown between welcomes. (Screenshots show these staging controls and preview areas.)

Important slash commands

• /welcome enable & /welcome disable — toggle the system.

• /welcome setchannel channel:#welcome — choose the post destination.

• /welcome setmessage message:"Welcome {user} to {server}!" — save a template (templates support {user}/{server}).

• /welcome preview — send a preview to the configured channel.

• /welcome settings & /welcome reset — show or reset stored values.

How to use it

1. Select and save your welcome channel.

2. Compose a short, friendly Welcome message template, using {user} and {server} placeholders for personalization.

3. Configure DM follow-up if you want new members to receive a private message (set cooldown to avoid spamming).

4. Use Stage Preview / /welcome preview to sanity-check formatting and placeholders. Only push live once the preview looks correct.

Tips

• Keep the public welcome short and put details (rules, role pickers) behind a button or in a pinned message.

• Use cooldowns to avoid repeated DMs when bots or integration accounts join.

• Use the staging/preview flow to catch formatting and link issues before hitting the server.

Embed Messages — polished announcements with staging

What it is
A visual embed builder for announcements: title, content, accent color, attachments (images) and destination channel. The dashboard stages embeds locally so you can refine before the bot uploads files and publishes.

Key UI elements

• Embed title, accent color, destination channel and main content body.

• Attachments / Upload image (attachments typically limited to PNG/JPEG/GIF and scanned before staging — preview is available).

• Preview pane that shows how the embed will render.

• Stage Embed button (staged embeds appear in the staged activity area for later publishing).

Important command (dashboard / bot)

• /welcome embed (or /welcome embed channel:<#> title:"...") — use the embed command variant to stage and push embeds. The dashboard UI mirrors and can generate the same command for you.

How to use it

1. Fill in title, content and pick an accent color (for brand consistency).

2. Upload any images or provide an image URL (preview the embed).

3. Click Stage Embed to add the embed to the staged list. Review staged embeds and then push them when you’re ready.

Tips

• Stage embeds to test different layouts (image on desktop vs mobile).

• Keep CTA links short and test them in preview.

• For large announcements, test in a staff-only channel first and then push to the live channel.

Custom Commands — quick chat automations without code

What it is
A lightweight command designer that creates trigger→response pairs (keyword triggers or short trigger phrases). Use it for welcome shortcuts, rules auto-replies, or workflow helpers that reply in chat automatically. The dashboard and slash commands both manage these responses. Responses support template variables (like {user} and {channel}) to personalise replies.

Key UI elements

• Create command box (trigger phrase and response).

• Keywords (no slash) area for message keywords that auto-reply in chat.

• Command library on the right to edit, enable/disable and view live usage.

Important slash commands

• /custom create name:welcome response:"Welcome to the server!" — create a trigger.

• /custom edit name:welcome new_response:"Glad to have you!" — edit response.

• /custom delete name:welcome — delete.

• /custom show name:welcome — preview stored response.

• /custom enable / /custom disable — toggle availability.

• /custom variables — list available template variables.

How to use it

1. Choose a short, unobtrusive trigger (no leading slash required for keyword triggers).

2. Compose a clear response and use placeholders if appropriate.

3. Enable deployment (toggle live/disabled). Test with a few messages in a quiet channel.

Tips

• Avoid overly generic keywords that could trigger in normal conversation (e.g., use “rulebot” vs just “rules” if you want to reduce accidental triggers).

• Use the dashboard command library to keep replies organised and to see which are live or staged.

Social Alerts — creator feed router for multiple platforms

What it is
A creator feed router that tracks creators across platforms (YouTube, X/Twitter, TikTok, Instagram, Threads, etc.) and posts templated alerts to your channels. The builder supports platform-specific templates, staging, and a live alerts manager for enabling/pausing alerts per creator.

Key UI elements

• Platform chooser (select YouTube, X, TikTok, Instagram, Threads).

• Track creator form (username/handle + destination channel + template).

• Command preview showing the /alerts command syntax the dashboard will run.

• Active Alerts Manager on the right — list of tracked creators with quick Edit in Builder and Enable Alert controls.

Important slash commands

• /alerts add platform:youtube username:"Gamerogue" channel:#alerts — track a creator.

• /alerts remove platform:youtube username:"Gamerogue" — stop tracking.

• /alerts list — list tracked creators.

• /alerts test platform:youtube username:"Gamerogue" — send a test alert.

• /alerts setmessage platform:youtube message:"New drop: {user} just posted! {url}" — customise templates.

• /alerts enable / /alerts disable — toggle platform-level alerts.

How to use it

1. Pick a platform and compose a template using placeholders like {user}, {platform}, {url}.

2. Add the creator with /alerts add … or use the dashboard form; stage the add to preview the command.

3. Use Active Alerts Manager to enable or pause creator alerts without rebuilding the whole form.

4. Test formatting with /alerts test before enabling production posting.

Tips

• Use platform-specific templates to include branded language or a platform icon per alert.

• Stage new creators and run /alerts test to validate the template and channel formatting.

• Pause alerts easily from the Active Alerts Manager when a creator has gone quiet.

Workflows & best practices

• Staging-first — always stage message/embeds/alerts, preview in the dashboard, then push. The dashboard keeps staging local while the bot handles uploads/publishing. This reduces accidental posts and makes iteration safe.

• Preview before publish — use the preview or Stage Preview controls for welcome, embed, or alert templates to check placeholders and mobile rendering.

• Small rollout — publish to a staff-only channel first, test with live traffic, then promote to public channels.

• Use placeholders — {user}, {server}, {url}, {platform}, etc., let messages stay dynamic and feel personalized. See /custom variables or the welcome/custom docs for what placeholders are supported.

Troubleshooting checklist

• Preview looks wrong — check that placeholders are spelled exactly (e.g., {user}), and run the dashboard preview or /welcome preview (welcome) or /alerts test (social) to validate.

• Image/attachment failing — ensure attachments are in accepted formats (PNG/JPEG/GIF). The dashboard stages and the bot handles the upload — re-upload and re-stage if the preview does not render. (The UI includes an attachments/upload control and preview.)

• Custom command not triggering — confirm the command is enabled (/custom enable) and that the trigger word isn’t being blocked by automod or other chat filters.

• Social alert not posting — verify the chosen platform is enabled (/alerts enable), the creator handle is correct, and the destination channel is set. Use /alerts test to verify a sample payload.

Quick command cheat-sheet (announce & automation)

• Welcome:

  • /welcome setchannel channel:#welcome

  • /welcome setmessage message:"Welcome {user} to {server}!"

  • /welcome preview / /welcome enable / /welcome disable

• Embeds:

  • /welcome embed channel:#announcements title:"Update" … (dashboard mirrors this command; stage via the embed builder).

• Custom commands:

  • /custom create name:welcome response:"Hi!"

  • /custom edit name:welcome new_response:"Glad you joined!"

  • /custom show name:welcome / /custom enable / /custom disable

• Social Alerts:

  • /alerts add platform:youtube username:"Creator" channel:#alerts

  • /alerts test platform:youtube username:"Creator"

  • /alerts setmessage platform:youtube message:"New drop: {user} {url}"