Documentation

Punishment messages

Customize moderation responses, member DMs and logs for each action.

Set it up

1. Open Moderation > Punishment messages and expand an action.
2. Edit the supported Command response, Member DM or Log message using the existing embed editor and live preview, then save.
3. Use {action}, {user}, {username}, {userId}, {moderator}, {server}, {reason}, {details} and {case} placeholders. Case is — if the number has not yet been allocated.
4. Use the highlighted Universal punishment message at the bottom to set one design for responses, DMs and logs. Existing action-specific designs override it.

Departments

Department shifts, reports, evidence links and leave requests. Setup guides you through name, Discord roles and optional goals. Open a role dropdown and tick the roles you want; Shift admin allows corrections to completed shift hours.

Set it up

1. Open Departments under the ER:LC sidebar heading. ER:LC integration opens the connection settings. Manage Server or server ownership is required to create a department. Create up to 15 departments.
2. Choose membership roles and assign supervisor permissions separately for each department. Members sign in at /departments and automatically see departments matching their current Discord roles.
3. Set weekly or monthly hours, arrest and scene quotas. Periods use UTC. Quotas show progress and do not automatically issue infractions.
4. Start or end a department shift and submit arrest or scene details. Evidence is optional: add up to 10 HTTPS links. Direct file uploads are not supported.
5. Request leave with dates and a reason. Authorized supervisors approve or deny it; you cannot approve your own leave. Active approved leave marks your quota paused.
6. Department settings and records are saved across restarts. Removing department membership roles removes portal access on the next request.

Getting started

Add Relayed, open your server and configure your first module.

Set it up

1. Use Add to Discord on the website. The current invite requests Administrator; only install the bot in a server you are authorized to manage.
2. Sign in at /dashboard with Discord. Choose a server where you have Manage Server or Administrator.
3. Keep Relayed's role above the roles and members it needs to manage. Discord's role hierarchy still applies with Administrator.
4. Use Quick setup for a guided start, or open a module directly. Configure required roles and channels before enabling or publishing it.
5. Use Overview to set your command prefix. The default is !; slash commands remain available.
6. Type to search or scroll long role/channel menus. Duplicate names show an ID suffix, and Quick setup channel choices show their parent category. Multi-role checkboxes stay open while you choose. Refresh roles & channels after creating something in Discord.

Commands

Use Discord's command picker for current required fields. Prefix equivalents use your server's configured prefix.

Tickets & support

Create private support channels with separate panels, teams and custom questions.

Set it up

1. Tickets has three sections: Tickets, Panels and Settings. Open Settings for blacklists, transcript channels and numbering.
2. Open Tickets & support → Panel & embed editor. Use Add ticket panel for another panel, such as Billing or Bug reports.
3. Name the panel and choose its Panel channel and private ticket-log destination. Each panel keeps its own setup.
4. Choose a Components V2 layout, start from scratch or import supported JSON. Classic is available too. Edit the live preview and move the dropdown/buttons block where you want it.
5. In Support options, name each option and choose the staff roles that may see and handle its tickets. Different options can use different teams.
6. Optionally choose notification roles to ping. They do not gain access unless also selected in the handling team. Relayed needs permission to mention the roles.
7. Choose a category for each option or a fallback category at the bottom. A fallback is optional when all options have their own category. Create category asks before creating it.
8. Expand Opening questions under an option. Add 1–5 questions, up to 45 characters each, and mark required answers. Members can answer with up to 1,000 characters.
9. Choose Dropdown or Buttons. Button styles are Discord's blue, gray, green or red; custom hex button colors are not supported.
10. Save & publish the selected panel, then open a test ticket. Up to 20 panels and 20 options per panel are supported.
11. In a Components V2 option, use Emoji (optional) to place an icon before its dropdown label and button text. Paste one regular emoji, a custom Discord emoji code such as <:name:123456789012345678>, or its ID. The preview updates as you type. Save and publish the panel to update the Discord message.
12. In Tickets → Panel & embed editor → Edit ticket welcome message, use Welcome message for to select the shared default or one support option. Enable Use a custom welcome for this support option, edit its title, description, colors, images and fields, then Save message design. The same selector is available when editing Ticket welcome in the Embed editor.
13. At the bottom of Edit ticket welcome message, open Ticket buttons. Edit Claim, Close or Transcript text, emoji and Discord color; move or remove a button. Use Add a button to restore an action or add an HTTPS website link. Choose Shared welcome for panel defaults, or choose a support option and enable Use custom buttons for this support option. Button overrides are independent of custom welcome text. Save message design.

Commands

Use Discord's command picker for current required fields. Prefix equivalents use your server's configured prefix.

Moderation & permissions

Choose exactly which roles can use each moderation action.

Set it up

1. Open Moderation. Cases is the default view; search the loaded records by member, reason or case number.
2. Choose Permissions, select a command group and expand an action to choose its allowed roles. Save moderation settings when finished.
3. Choose Settings for the module switch, member DMs and moderation log channel. Choose Messages to edit Universal or one action’s message designs.
4. Open Moderation. Choose the log destination and whether Relayed attempts punishment notice DMs.
5. Expand each action you want to use, select Selected roles only and choose up to 25 allowed roles.
6. Leave actions disabled when they are not needed. Unconfigured actions stay disabled, including for administrators.
7. Save moderation settings. The same policy applies to slash commands and the server's configured prefix.
8. Test with an authorized moderator and an ordinary member. Member actions still check both the moderator's and bot's role hierarchy.

Commands

Use Discord's command picker for current required fields. Prefix equivalents use your server's configured prefix.

AutoMod & unsafe links

Block unwanted content and configure points-based responses.

Set it up

1. Open Auto moderation → Set up filters for the guided questions. Select blocked words, spam, invites, links, offensive language or mention spam.
2. Choose exceptions for trusted roles, categories and channels. Set a private alert channel when needed. Review whether each rule should be enabled now.
3. Under Block unsafe links, separately enable Scam & malware links and/or Adult-site links. Both begin off.
4. Open Exceptions to allow specific websites or exempt roles, categories and channels. Save link protection, then use Check a link with the saved settings.
5. Under Auto Punish, choose which new violations add points, how many points each adds and the counting window.
6. Add punishment thresholds, such as a warning before a later timeout. Enable automatic punishments and save only after reviewing the sequence.

Anti-Nuke

Quarantine members who exceed configured destructive-action limits.

Set it up

1. Open Anti-Nuke. The server owner completes the four-step setup; protection starts disabled.
2. Choose Authorized roles first. The owner controls this list; selected roles may manage protection and release quarantines, subject to dashboard access.
3. Set a rolling time window and limits for channel/role creation and deletion, bans, kicks and mass pings. Quarantine triggers on the limit, not one action after it.
4. Mass pings always includes @everyone and @here. Optionally select additional role mentions; ordinary member mentions do not count.
5. Choose explicitly trusted user IDs, a private log destination and whether quarantine notices should be sent by DM.
6. Optionally enable bot-addition protection. Relayed uses the audit log to identify the inviter, attempts quarantine and kicks the added bot.
7. Review and enable. Setup creates/reuses the Quarantined role below Relayed and applies channel isolation. If no logs channel was selected, setup can create a private Anti-Nuke logs channel.
8. After initial setup, use Scam Catcher & Anti-Nuke settings to edit limits, roles, logs and exemptions directly without repeating channel-isolation setup.
9. The server owner can turn on Scam Catcher under Scam Catcher & Anti-Nuke settings. It creates a top-level #do-not-type-here channel with a warning. Select kick, ban or soft-ban; any non-exempt message triggers the selected action.
10. If roles are manually restored without releasing quarantine, later protection triggers reapply role removal. A previous quarantine record is not an exemption.

Commands

Use Discord's command picker for current required fields. Prefix equivalents use your server's configured prefix.

Applications

Publish recruitment forms and review submissions privately.

Set it up

1. Open Applications, enable the module and choose the panel channel, private review channel and optional reviewer/acceptance roles.
2. Choose Components V2 and a layout, start from scratch or import supported JSON. Customize the live preview.
3. Add application options, each with its own name, description and questions. Collapse options while editing. Up to 20 applications and 25 questions per application, with up to 1,000 characters per question are supported.
4. Choose a dropdown or buttons, with optional custom labels and Discord button styles.
5. Choose Direct messages or Discord form for answers. Save and publish the panel.
6. For DMs, applicants answer one question at a time, then click Submit application. Review pending submissions in the dashboard or private review channel.
7. Accept or decline with an optional reason. Relayed attempts to DM the decision and reason to the applicant.
8. In a Components V2 option, use Emoji (optional) to place an icon before its dropdown label and button text. Paste one regular emoji, a custom Discord emoji code such as <:name:123456789012345678>, or its ID. The preview updates as you type. Save and publish the panel to update the Discord message.

Staff management

Record promotions, demotions and infractions with editable notices.

Set it up

1. Open Staff management → Ranks & permissions. Select which roles may run promote, demote and infract; configure the available ranks and log destination.
2. Open Message designs. Pick a promotion, demotion or infraction template and edit its text, fields, images and preview.
3. Save the message design for future actions. Templates replace the current unsaved design, so save or back it up first.
4. Use Actions & history or a configured command. Select the member, appropriate rank and reason; review the action before submitting.
5. Search/filter retained staff records and export the available history as CSV when needed.

Commands

Use Discord's command picker for current required fields. Prefix equivalents use your server's configured prefix.

ER:LC integration & staff workspace

Connect a private game server, view live activity and manage staff shifts.

Set it up

1. Open ER:LC integration. Enter only a server API key you are authorized to use, then save and test the connection.
2. If remote commands are denied, follow the private-server authorization link shown for Relayed in the ER:LC owner dashboard. Read access does not itself grant command access.
3. Choose reviewer roles for staff access. Show the permanent staff join code and share it privately with your team.
4. Staff sign in at /staff and request access with that code. A manager or configured reviewer approves or denies them; reviewers must have approved staff access themselves.
5. Approved staff open /staff, select their server, and choose Server staff or a department under Your shift. Start/End shift follows the selected team’s permissions and ledger.
6. Server managers can use Run command in the integration. Review carefully: commands execute in game immediately.

Commands

Use Discord's command picker for current required fields. Prefix equivalents use your server's configured prefix.

Sessions & voting

Publish startup, shutdown, full, low-population and interest-vote messages.

Set it up

1. Open Sessions and choose the announcement channel, ping roles, join information and any connected ER:LC details.
2. Expand Edit under Startup, Shutdown, Server full, Low population or Interest vote. The Sessions page keeps its existing layout; each type has its own Components V2 design. Older classic embed content is converted when a design is first opened.
3. Edit text, images, text with thumbnail, divider spacing/line visibility and accent color. Move or remove content blocks. Move the Vote & join buttons block anywhere in the message. The preview updates as you type.
4. For interest votes, customize Vote button text, emoji and blue/gray/green/red style. Customize the join label/emoji, show or hide the join button, and choose Vote/Join order. Join URLs still use your connected ER:LC code; Discord link buttons are gray. Set vote goal and a duration from 1 to 1,440 minutes in Session settings.
5. Post the desired announcement. Members can add/remove interest votes. Authorized staff use /voters for the relevant vote.
6. Start a session separately when ready; reaching a vote goal does not start one automatically.
7. Add Extra buttons for HTTPS website links or colored private-answer buttons. Add Dropdown for information choices with private answers. Customize labels and regular or accessible custom emojis. These controls provide information only; they do not run game commands, grant roles or start sessions.
8. Layouts & JSON contains four existing layouts, Start from scratch and Relayed session V2 JSON import/export. Applying a layout replaces unsaved message blocks while retaining button settings; save/export first.
9. Use ER:LC placeholders in text, button labels and private answers. Click a placeholder to insert it into the last focused message-text or built-in button-label field, or copy it if none is focused. Test private answers in the preview, then Save the design.

Commands

Use Discord's command picker for current required fields. Prefix equivalents use your server's configured prefix.

Welcome, goodbye & reaction roles

Greet members and offer safe self-service roles.

Set it up

1. Open Welcome & goodbye. Enable the module and separately choose welcome and goodbye delivery, destinations and plain text or embed format.
2. Use supported placeholders such as {user}, {username}, {server} and {count}. Preview the message and send a test.
3. For a join role, enable Automatically give new members a role and select the ordinary member role. Save.
4. Open Reaction roles to create a role-button panel. Name each button, select its role and choose a panel channel.
5. Save and publish. Members click once to add a role and again to remove it.

Message editor & drafts

Design classic embeds or custom Components V2 messages with live previews and working controls.

Set it up

1. Open Embed editor, or use the message editor inside Tickets, Applications, Sessions, Staff management or Welcome & goodbye.
2. Choose the message you want to change. Use a starter layout or start from scratch where available.
3. Edit text, colors, images, fields and supported controls. The Discord-style preview updates as you type.
4. Use supported JSON import to load a compatible design. An arbitrary Discord/Discohook document may need adjustment.
5. Save the design. For posted panels, use Save & publish to replace the published version; a draft alone does not change Discord.
6. Use Past saves to review available history. Keep separate exports for important designs.
7. Unfinished editor work saves to this device as you type and syncs privately to your account/server. Returning with unchanged saved settings restores the draft, open sections and page position. Saved settings and cloud-synced current drafts survive bot/server restarts.
8. New custom message starts in Components V2; existing classic messages retain their format. Choose Message style to switch a custom message. Add, move or remove text, image, text with thumbnail, divider, button-row and dropdown blocks.
9. Buttons can open HTTPS links or show editable private responses. Dropdown options have a label, optional description/emoji and an editable private response. Test those responses in the preview.
10. Choose a saved-message name and destination. Save design stores custom messages without posting; Save & publish message updates their published copy.
11. Use the V2 Import / export layout JSON section for this editor’s Relayed V2 schema. Classic embed JSON import remains available in Classic embed mode.
12. For a saved custom message using Classic embed, use Link buttons → Add link button below the embed fields. Set each label, HTTPS URL and optional emoji; add up to five or remove rows. The preview updates immediately. Save design, then Save & publish message. Existing V2 messages use their button-row blocks.
13. In custom Components V2 messages, add a Dropdown block and set an option’s When selected action to Toggle a role. Choose an ordinary Discord role below the bot, then save and publish. Members select that option to add or remove that role; confirmations are private.

Commands

Use Discord's command picker for current required fields. Prefix equivalents use your server's configured prefix.

Logging & activity

Route moderation, ticket, staff and server events to the right channels.

Set it up

1. Open Logging and choose destinations for the event types you need. Keep ticket and personnel records in private channels.
2. Enable the relevant log types, save and use Send test to verify delivery.
3. For transcripts, also confirm the private ticket-log destination in the selected ticket panel.
4. If delivery fails, check View Channel, Send Messages, Embed Links and Attach Files, plus any category overrides.

Relayed Plus & custom bot

Understand paid modules and the customer-bot setup process.

Set it up

1. Open /pricing and choose a plan. Sign in with Discord if prompted, choose the server in the dropdown and continue to Stripe. Only servers you manage are listed; Plus requires Relayed installed. The chosen server ID is carried into checkout.
2. Plus covers Applications, Partnerships and additional ticket panels. All other modules, including Staff management, Sessions and ER:LC integration, are free. Existing first-100-server lifetime grants remain associated with their server ID.
3. For Custom Bot, choose the server and billing interval on /pricing. Hosting capacity is checked and reserved before Stripe checkout. Confirmed payment automatically enables setup for that purchaser and server; the success redirect alone never grants access.
4. Follow /white-label: create your own Discord application, enable Server Members and Message Content intents as needed, paste its Application ID to generate an invite restricted to the purchased server, then enter the bot name and token privately. The server invitation and token are checked. Paid setups start hosting after connection.
5. Configure its name and artwork, enable the required Discord intents, and follow the setup/start controls. The bot needs role hierarchy and channel access just like Relayed.
6. Review imported same-server settings after the first start. Republish existing panels through the customer bot; Discord messages belong to the bot that posted them.
7. Support-approved one-time Custom Bot plans can cover one bot in up to two approved servers for one calendar year from payment. Invite the same application to both servers before connecting its token once at /white-label. Branding and hosting are shared; each server keeps separate module settings and records. Start/stop affects both servers. Access ends on the payment anniversary without an automatic renewal or charge; the bot and settings are retained. A separate recurring subscription is not canceled by a custom plan. Contact support for changes.

Ask Relayed & troubleshooting

Get product guidance without sharing secrets or private server records.

Set it up

1. Open Ask Relayed in the bottom-right of the website or dashboard and sign in if prompted.
2. Describe the module and what you are trying to do. The assistant uses maintained documentation and supports follow-up questions.
3. For missing commands, check module access, configured issuer roles, Use Application Commands and whether the correct bot is active.
4. For missing channels or roles, use Refresh roles & channels. For failed role changes, check Manage Roles and role order.
5. For rate limits, wait for the displayed cooldown and avoid repeated refresh/reconnect attempts.
6. If the guide is insufficient, join the support server and describe the issue with sensitive details removed.

Commands

Use Discord's command picker for current required fields. Prefix equivalents use your server's configured prefix.

Shift Logging

Start and end duty in Discord, correct hours, and optionally track weekly staff requirements.

Set it up

1. Open Shift Logging and choose Set up Shift Logging. The full-screen guide covers roles, logs and weekly requirements.
2. The server owner chooses authorized setup roles. Only the owner can change that list. Dashboard management access is still required. Choose tracked staff roles and separate roles for start, end and hour corrections. Unconfigured commands are owner-only.
3. Optionally select a private log channel and enable DM notices for corrections and weekly infractions.
4. Optional weekly targets: shift hours and messages across all server channels the bot can see. Messages from bots, webhooks and system events are excluded; only aggregate counts are retained, not message text.
5. Save and enable. Use /shift manage in Discord for a private personal embed with Start, Pause, Resume and End buttons, completed shift count, total/average duration, current shift and weekly hours. /shift start and /shift end remain available. Paused time does not count, and shift state survives restarts.
6. Use /shift admin member action reason hours to add/remove hours or set this week’s hours. Decimal hours are supported. Cancel discards an active shift’s unsaved time; past shift history is retained. Corrections are logged with the actor and reason. Choose Remove a completed shift and select its shift-id to void a saved shift while preserving its correction trail. View hours shows a selected member’s weekly and total time without changes or a required reason.
7. In setup, customize the management-panel title, description, accent color and optional HTTPS image. Description placeholders: {status} and {user}. Start/resume uses configured start roles; pause/end uses configured end roles. Buttons belong to the person who opened the panel, and permissions are checked on every use.

Commands

Use Discord's command picker for current required fields. Prefix equivalents use your server's configured prefix.

Partnerships

Use saved posting defaults, collect an ad in a ticket, and publish only after staff approval.

Set it up

1. Open Dashboard → Partnerships. Choose the default posting channel, default ping (@everyone, @here or No ping), authorized command roles and Plain text or Embed. Save and enable; it starts disabled. At least one staff role and a default channel are required to enable through the dashboard.
2. Inside an open Relayed ticket, staff runs /partnership or the configured prefix followed by partnership. Relayed uses the saved defaults and immediately asks the ticket opener for their ad. Nothing begins automatically from ordinary chat.
3. Override one request with slash channel/ping options, or use !partnership [everyone|here|none] [#channel] with your server’s prefix. Explicit No ping overrides a saved broad ping. Custom role pings are not supported.
4. The ticket opener sends their next text message (up to 1,900 characters; use image links, not attachments). Relayed pings the initiating staff member with the ad preview, destination, selected ping and invite-check warnings.
5. The initiating staff member, still authorized, must click Approve & post before anything publishes. They can instead Request changes with a reason or Deny with an optional reason. A replacement ad needs a new approval. The requester receives the decision; approval includes a direct post link.

Commands

Use Discord's command picker for current required fields. Prefix equivalents use your server's configured prefix.

Custom commands

Create prefix shortcuts for text, embeds, saved messages and working panels.

Set it up

1. Open Custom commands → Set up your first command. The full-screen guide has four steps.
2. Name the command without a prefix. Add up to five aliases and an optional description. Start with a reply, embed, support, application, saved-design or partnership-information preset. The chosen starter has an orange highlight, checkmark and Selected label.
3. Add one to five responses. Choose plain text, a new embed, a saved custom message from the Embed editor, a published ticket/application/reaction-role panel, or the server dashboard link.
4. For a plain-text or new-embed reply, open Link buttons → Add link button. Enter a label, HTTPS URL and optional regular/custom emoji. Add up to five links; previews update as you type. Remove a row to remove that button. Saved-message replies use the links saved in the Embed editor.
5. Choose the current channel, a specific channel or DMs. Interactive server panels and saved V2 messages require a server channel. Publish linked panels in their own module first.
6. Choose Everyone explicitly, or select allowed roles. Optionally restrict usage to selected channels. Set a per-person cooldown from 1–3,600 seconds. The default is five seconds.
7. Review, enable and save. Run your configured prefix plus the name, for example !rules, or use /custom name:rules. Each server supports up to 25 commands. Edit, disable, delete or search commands from the module.

Commands

Use Discord's command picker for current required fields. Prefix equivalents use your server's configured prefix.

Anti-spam

Choose an exact number of messages in a rolling time window.

Set it up

1. Open Auto moderation > Anti-spam and enable it.
2. Choose 2–100 messages within 1–120 seconds, add optional role/category/channel exceptions, then Save anti-spam.
3. At the limit, Relayed removes the recent message burst and continues removing messages while the count remains over the limit.

Import settings and records

Preview and import compatible JSON from Server settings.

Set it up

1. Open Server settings > Import and download the template for the supported format.
2. Upload a JSON file up to 200 KB. Choose Add to existing or Replace selected data.
3. Select supported sections, preview the counts, confirm and import.

ER:LC server automation

Optional time, weather and exact-account username protection.

Set it up

1. Connect your ER:LC server and authorize remote command access, then open ER:LC integration > Server automation. All three automations start disabled.
2. Time Sync: choose an IANA time zone. It sets the game clock about every five minutes while players are online. Set in-game Length of Day to 1440. Daylight saving changes follow the selected zone.
3. Search for a city at the top of Server automation. Suggestions include region and country; selecting one fills the time zone, latitude and longitude for Time Sync and Weather Sync. Search supports typing and arrow keys/Enter. You can still edit the fields manually. Weather Sync: choose a public location. Disable Automatic Weather Cycle in-game; ER:LC Premium Settings Pack is required. Forecasts are cached for at least 15 minutes and longer when the provider requires it.
4. Enable username protection only if you want accounts whose usernames begin with all or other banned. Checks use live ER:LC players and ban a validated numeric Roblox ID, never an all/others selector. Legitimate matching names are also affected.

Giveaways

Customize a giveaway, collect entries and draw winners automatically.

Set it up

1. Open Dashboard → Giveaways. Enable the module, select manager roles and optionally a default channel. Server managers always have access.
2. Customize Classic embed or Components V2, text, accent color, images, footer and the entry button. Preview active/ended messages; save before creating. Changes apply to new giveaways.
3. Run /giveaway create with a prize and duration such as 30m, 2h or 3d. Optionally choose a channel and 1–20 winners.
4. Members click to enter and click again to leave. The count updates within a few seconds. Winners are drawn at the saved deadline.
5. To finish early, run /giveaway end and search the active prize names, or paste the original giveaway message link.
6. Joining or leaving saves the entry and immediately requests a participant-count update. No background batching delay is added. Discord may still delay edits; failed edits retry without losing entries.

Commands

Use Discord's command picker for current required fields. Prefix equivalents use your server's configured prefix.

Role dropdowns

Let members manage their own roles through a private dropdown.

Set it up

1. Open Reaction roles and choose Buttons or Dropdown, then Classic embed or Components V2.
2. Choose up to 20 safe member roles below the bot. Add labels, optional descriptions and emojis; edit the panel message.
3. Save and publish. The Self Roles dropdown appears directly on the message. Select roles to add them; select them again to remove them. Personal role changes are confirmed privately.
4. New role panels use Components V2 and a direct dropdown by default. Add, remove or reorder text, images, dividers and the role selector, set an accent hex color and dropdown placeholder, and edit each role’s label, description and emoji. The preview updates as you type. Existing panels need republishing to adopt the new controls.

Ticket logging & numbering

Separate transcripts from activity notices and choose the next ticket-number minimum.

Set it up

1. Open Tickets → Logging & numbering. Choose an activity channel and a separate private transcript channel.
2. Choose a starting ticket number. The next-number preview respects existing higher counters. Save these settings independently of your panel design.
3. Use /transcript inside a ticket to send its export to the configured private destination. Closing also archives there before deletion.

Commands

Use Discord's command picker for current required fields. Prefix equivalents use your server's configured prefix.

Staff workspace controls

Manage shifts and save logs with immediate feedback.

Set it up

1. Open /staff and choose your approved server. The desktop layout places shifts, log creation and activity side by side.
2. Start or end your shift. Starting/Ending is shown immediately, then replaced by the confirmed state; an error restores your previous state.
3. Enter a Roblox username, choose Warn, Kick or Ban and add a reason. Create log saves the record without executing a game command. Proof remains optional.
4. A pending card appears while the log saves. If saving fails, the form is preserved and the provisional card is removed.
5. If permitted, explicitly enable Also run this in game for a kick or ban. These live commands retain a separate review and confirmation.

Try the feature showcase

Explore Relayed with safe sample workflows.

Set it up

1. Open the homepage Features section and choose See all features to expand every card.
2. Choose Try on a card or a Showcase tab. Follow the sample member and staff actions, then use Reset demo to start over.
3. Examples use sample data only. They do not contact Discord, run game commands, change roles or make purchases.
4. Custom Bot is the new name for the former White Label service; existing setup links continue working.

Find your module settings

A consistent layout for configuring and using Relayed.

Set it up

1. Choose a module from the sidebar. Use its section tabs to separate activity, configuration and message design.
2. Tickets: use Tickets for open requests, Panels for the message and support options, and Settings for blacklists, transcript destinations and numbering.
3. Applications: choose Submissions, Forms or Eligibility. Reaction roles: choose Roles, Message design or Settings. Welcome & goodbye: choose Welcome, Goodbye or Auto roles.
4. Auto moderation: choose Spam, Links, Discord filters or Punishments. Giveaways: choose Giveaways, Settings or Message design. Partnerships: choose Activity or Settings.
5. ER:LC integration: choose Overview, Connection, Staff access, Commands or Automation. Sessions: choose Announcements, Message designs or Settings. Logging: choose Channels or Test delivery.
6. Anti-Nuke: complete initial setup, then use Overview, Quarantines, Incidents or Settings. Shift Logging and Custom commands keep their guided setup.