# Tickets

Formify supports two related ideas:

1. **Ticket templates** — reusable setups you publish (button, support roles, category, embeds).
2. **Ticket logs** — the list of support channels that were actually opened.

In the dashboard sidebar, **Tickets** means templates. **Ticket Logs** means open/closed support channels.

---

## Ticket templates

A template defines how a support button works and what happens when someone opens a ticket.

### Create a template

1. Go to **Tickets** → **New ticket** (or install from [Marketplace](/guides/marketplace/)).
2. Configure:
   - **Title** and button label
   - **Support roles** — staff who can claim, close, and manage the ticket
   - **Category** — where Discord channels are created
   - **Channel name format** — e.g. `support-{user}`
   - **Max open per user** — limit duplicate tickets
   - Transcript and close behavior

3. Save, customize **Embeds** if needed, then **Publish** to a channel.

Members click the button (or pick the template from a ticket panel) to open a private channel.

---

## Ticket panels

**Ticket panels** work like form panels: one message, multiple ticket types.

1. Go to **Ticket Panels** → create a panel.
2. Set title, description, and display type (buttons or dropdown).
3. Attach one or more ticket templates.
4. Publish to Discord.

See embed settings per panel under **Embeds** on the panel editor.

---

## Form-linked tickets

Forms can open tickets automatically or when staff click **Ticket Response**:

- Configure the **Tickets** tab on the form
- Or enable ticket output / approve-to-ticket options

Those tickets show up in **Ticket Logs** with a form origin. The submission detail page links to the ticket when one exists.

---

## Working tickets in Discord

Common slash commands (see [Commands](/reference/commands/) for the full list):

| Command | Purpose |
|---------|---------|
| `/ticket claim` | Assign yourself to the ticket |
| `/ticket close` | Close with optional reason |
| `/ticket reopen` | Reopen a closed ticket |
| `/ticket info` | Show ticket metadata |
| `/ticket add` / `remove` | Add or remove members (Manage Server) |
| `/ticket closerequest` | Ask the submitter to approve closing |

Support roles on the template (or Manage Server) can use most actions. Formify needs **Manage Channels** to create and manage ticket channels.

Inside the ticket channel, staff may also see buttons for close, approve, deny, and claim depending on how the template was set up.

---

## Ticket logs in the dashboard

Go to **Ticket Logs** to:

- Filter by open, closed, or claimed
- Filter by origin (form, panel, or standalone template)
- Search and sort
- Open detail view and use **Claim**, **Close**, or **Reopen**
- Jump to the channel in Discord

Pagination shows 50 tickets per page.

---

## Close requests

When staff run `/ticket closerequest`, the submitter gets approve/deny buttons. If they approve, the ticket closes along your template's rules. If they deny, staff can continue the conversation.

---

## Related

- [Submissions](/guides/submissions/) — form-linked tickets
- [Embeds](/guides/embeds/) — ticket message templates
- [Permissions](/getting-started/permissions/)
- [Troubleshooting](/help/troubleshooting/)