Terminology
Key terms and how the pieces of Assistance fit together.
Assistance reuses a few concepts across tickets, commands, automations, and the library. Understanding them upfront makes every guide easier to follow.
Template
A template is a rich Discord message — text, embeds, buttons, and other components. Templates live in the library and are sent by commands, ticket panels, and automations.
Templates support variables like
${triggeredBy.username} that are filled in when the message is sent.
Assistance supports two template formats:
- Traditional templates — classic embeds and action rows
- Components V2 — sections, galleries, and containers
Library
The library is a file manager for your server. It stores templates, folders, and other content — similar to Finder on macOS or File Explorer on Windows.
Because commands and tickets reference library templates, editing a template updates every place it is used.
Package
A package is an exported bundle of templates, commands, and related content that can be installed into a server. Packages are a fast way to get started. Try the demo package to see one in action.
Action
An action is something Assistance does when triggered — send a template, open a ticket, run a command, and more. Actions are wired to:
- Buttons and select menus on templates
- Custom commands
- Automations
See the full list in the actions guide.
Command
A command is a slash command or message (prefix) command members run in Discord. Each command runs one or more actions — usually sending a template or opening a ticket.
Slash commands must be deployed to Discord after you save them. Message commands take effect immediately.
Automation
An automation is a visual workflow that reacts to server events — a member joining, a message being sent, a button click, and more. Automations can send templates, run actions, and pass custom variables through the graph. See the automations guide for the full breakdown of triggers, nodes, and publishing.
Ticket
A ticket is a private channel between one member and your staff. Tickets are
opened through actions (there is no built-in
/ticket create command). Each ticket panel defines how channels are named,
who can respond, and what message is sent on creation.
Variable
A variable is a placeholder in a template or ticket name that resolves at
send time — for example ${guild.name} or ${ticket.id}. Built-in variables
cover guild, member, ticket, and random values. Automations can also define
custom ${metadata.*} variables.
Guild API token
A guild API token (gt_…) lets your backend call the Assistance REST API
on behalf of a server. Tokens are created from the Tokens page and
scoped to specific permissions. This is separate from OAuth, which is reserved
for internal Assistance applications.
OAuth application
OAuth applications are currently internal-only. They are not available for external app registration or third-party sign-in. For server automation and external services, use guild API tokens instead.
Where to go next
How is this guide?