Commands
All commands are slash commands unless noted. Type / in a text channel to see what is available in your server.
Your dashboard includes a searchable Discord commands page (sidebar → Discord commands) for each server. It lists every command, who can run it, whether it is available to your account, and per-command options. This docs page is the static reference; the dashboard page filters to what you can run today.
New to Ogma? Follow the setup guide first — it tells you exactly which commands to run and when.
Who can use what
| Access | Typical users |
|---|---|
| Server admin | Manage Server permission, or a role assigned as management in Settings |
| Support staff | A staff role from Settings, or Manage Channels |
| Ticket participant | The ticket owner or support staff |
| Anyone | Any member (when enabled) |
Staff roles and management roles are configured in dashboard Settings → Team & access.
Many staff commands accept either a configured staff role or Discord Manage Channels. Exceptions:
| Command | Who can run |
|---|---|
/close | Manage Channels only (staff role alone is not enough) |
/remove | Configured staff role only |
/add, /rename | Ticket owner or configured staff role |
/claim, /unclaim, /note, /macro | Staff role or Manage Channels |
/lockdown, /unlock | Management role or Manage Server |
Setup commands (run these first)
These require Manage Server (server admin).
| Command | When to use it |
|---|---|
/ogma-config setup | New server — opens a guided form to create channels, save settings, and post the ticket panel |
/ogma-config link | Existing channels — auto-connects #support, transcript channels, and ticket categories you already have |
/ogma-config view | Any time — shows linked channels, setup status, enabled ticket types, and a link to dashboard Settings |
/ogma autoconfig | After dashboard changes — creates or updates Discord channels from settings you saved on the website |
Permission note
Ogma needs Manage Channels on its bot role to create channels and tickets. If something is missing, the bot replies with a list of permissions to fix — go to Server Settings → Roles → Ogma and enable them.
Ticket commands
Use these inside an open ticket channel unless noted.
| Command | Who can use | What it does |
|---|---|---|
/close reason note? | Manage Channels | Closes the ticket, archives a transcript, deletes the channel, and sends the user a rating DM |
/claim | Staff role or Manage Channels | Assigns the ticket to you so others know you are handling it |
/unclaim | Staff role or Manage Channels | Releases your claim so another staff member can pick it up |
/note content | Staff role or Manage Channels | Adds an internal note (visible in the dashboard, excluded from user-facing transcripts) |
/add user:@someone | Ticket owner or staff role | Adds someone to the private ticket channel |
/remove user:@someone | Staff role | Removes someone from the ticket channel |
/rename name:text | Ticket owner or staff role | Renames the ticket channel |
/lockdown | Management | Restricts the ticket so only the customer and management roles can access the channel |
/unlock | Management | Lifts lockdown and restores normal staff access |
Closing a ticket
/close requires a reason:
- Resolved
- Duplicate
- User unresponsive
- Out of scope
- Spam / abuse
- Other
You can add an optional note (up to 500 characters). The ticket owner receives a CSAT rating DM after closure when one has not already been submitted.
Lockdown
Lockdown is for sensitive tickets (billing disputes, HR, moderation). Regular support staff lose channel access until lockdown is lifted. Configure management roles in Settings → Team & access before using /lockdown or /unlock.
Closed tickets that were under lockdown remain restricted to management in the dashboard.
Staff shortcuts
| Shortcut | Who can use | What it does |
|---|---|---|
/macro shortcut | Staff role or Manage Channels (Plus or Enterprise) | Inserts a canned response from Settings → Macros (e.g. /macro refund-policy) |
-# your note | Staff | Send a message starting with -# to save a quick internal note; the message is deleted after saving |
Macros require Ogma Plus or Enterprise. Create and edit macros in dashboard Settings → Macros.
Knowledge commands
| Command | Permission | What it does |
|---|---|---|
/ingest content title? | Manage Server | Adds pasted text to your knowledge base immediately |
The optional title helps you find the source later. For files, URLs, and synced sources, use dashboard Knowledge.
AI chat (raw GPT)
These commands chat directly with the AI model without searching your knowledge base. They count against your plan's direct AI question allowance (Playground uses the same meter).
| Command | Notes |
|---|---|
/ask prompt | Preferred command name |
/ogma askgpt prompt | Legacy alias — same behavior as /ask |
Both require Settings → AI & voice → Enable raw GPT commands. When disabled, the bot points you to Playground instead.
Hourly rate limits apply per guild, channel, and user. Monthly AI usage is tracked for billing and alerts; it does not hard-block /ask at the included monthly count — see Billing.
Testing vs general chat
| Tool | Use for |
|---|---|
| Playground (dashboard → Knowledge) | Testing real support answers — shows exactly which docs were used |
/ask or /ogma askgpt | General AI chat — ignores your docs |
For validating support quality, always use Playground, not raw GPT commands.
Quick setup reminder
| Your situation | Command |
|---|---|
| Brand new server | /ogma-config setup |
| Already have support channels | /ogma-config link |
| Changed settings on the website | /ogma autoconfig |
| Not sure if you are done | /ogma-config view |
Full walkthrough: Setup guide.
Related
- How tickets work
- Escalation
- Support ops macros (Settings → Macros)
- Billing & usage limits