The

fastest


way to run your server.

Get StartedExplore Features

Platform

One bot.
Every workflow.

Assistance replaces the patchwork — support, automation, and content in a single platform you manage from the web.

Read about library
Library
LibraryTemplates

Support

Folder

Welcome Panel

V2 Template

verify

Command

Auto-close

Automation

Templates, commands, and automations in one visual workspace. Folders, version history, and a block editor keep everything organized — tickets and commands pull from here.

Getting started

From invite to live server in three steps

No scattered bots, no config files. Configure everything from the dashboard and publish when you're ready.

  1. 01

    Invite Assistance

    Log in with Discord, pick a server you manage, and approve the permissions. You're in the dashboard right after.

  2. 02

    Build in the dashboard

    Write templates, commands, and automations from the web, then point a ticket panel at them. Edits go through a save bar, so nothing lands by accident.

  3. 03

    Publish when ready

    Automations run their published version, not your draft, and the library keeps version history. Slash commands deploy to Discord as their own step.

Verification

One clear path to access

Members run /verify or press a button on one of your templates, and Assistance walks them through only the steps you enabled. When they finish, it applies the role and nickname you configured.

Member journey
  1. Run /verifyAssistance opens a guided page
  2. Complete the stepsOnly the checks you enabled
  3. Role appliedPlus an auto-nickname, if set

Browser and network signals are stored as keyed hashes and deleted when they expire — you choose a retention window between 1 and 90 days.

Roblox account linking
Members link their Roblox account, and you can auto-nickname them from their Roblox username, display name, or user ID.
Browser and IP continuity
Optional signals that help you spot repeat verification. Assistance stores keyed hashes, never the raw values.
One account per network
Optionally reject a verification when its browser or network was recently used by a different Discord account.
Discord CAPTCHA
Require a challenge before access is granted, for when automated verification is a concern.
Read about verification

Packages

Set it up once, reuse it anywhere

A package bundles commands, templates, and automations into something you can install into another server — or hand to someone else entirely.

Install from the registry

Browse public packages, review the files a package contains, then install it into a server you manage.

Publish your own

Bundle commands, templates, and automations you've refined in one server and share them with everyone else.

Keep it private

Mark a package private so it stays out of public directories, and optionally protect it with a password.

Browse the registryHow packages work

And the rest

The parts you notice later

The things that stop mattering until they do — credentials, history, and a way out of the dashboard.

Secrets

Store API keys and tokens for automation HTTP requests. Encrypted at rest, scoped to hostnames you allow, and never shown again after you save.

REST API

Server-scoped API keys with opt-in scopes, so an integration can read members, post alerts, or run automations — and nothing more.

Variables

One ${…} syntax shared across templates, channel names, and nicknames. Insert them from a picker instead of memorizing them.

Components V2

Build messages from Discord's modern display components — sections, galleries, and containers — not just text and embeds.

Transcripts

Every closed ticket is captured as a readable snapshot, viewable in the dashboard and shareable by link when you publish it.

Risk signals

Advisory scores that point staff at what to review first. Assistance never bans, kicks, or times out a member from a score alone.

Questions

Before you invite

The things worth knowing up front. Everything else lives in the docs.

Read the docs
Do I need to write code?
No. Commands, message templates, and automations are all built in the dashboard — automations are a visual graph of triggers, data, and actions. If you do want to go further, automations can call external APIs and there's a REST API with server-scoped keys.
How do members open a ticket?
Through an action you add to a command or a template button. There's no built-in /ticket create command, which means the entry point, wording, and permissions are yours to define rather than something you have to work around.
What permissions does the bot need?
Manage Channels to create and close ticket channels, Send Messages to reply and post templates, Read Message History to build transcripts, and Embed Links to render rich templates. You'll need Manage Server on the Discord side to add the bot.
Can I move a setup to another server?
Yes. Package up your commands, templates, and automations, then install that package into any other server you manage. Installed items become ordinary server content you can edit freely.
Do changes go live immediately?
Only when you say so. Dashboard edits are applied through a save bar, automations run the published version rather than your draft, and the library keeps version history. Slash commands are deployed to Discord as a separate step.
Does verification require Roblox?
No. Roblox account linking is one option. Browser continuity, IP continuity, one-account-per-network, and Discord CAPTCHA are each independent toggles, so you can run verification with whichever combination fits your server.

Ready to run your server the Assistance way?

Add Assistance to your Discord server in seconds. Configure tickets, templates, and commands from the dashboard — no code required.

Invite to ServerRead the Docs