> For the complete documentation index, see [llms.txt](https://docs.void.enterprises/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.void.enterprises/modules/tickets.md).

# Tickets

Streamlining customer support

## About this feature

Tickets allow members within your server to request support. They are dedicated a private channel called a "ticket", where they may state their inquiry. 

## Setup

This guide will walk you through setting up the system to your needs

### Enabling the system

To enable or disable modules within VOID, we use "toggle" commands which toggle the state of the module; on or off. By default, all modules are usually disabled, so we have to toggle it on. To do this, run the following command:

<pre data-title=">_ "><code><strong>/ticket toggle setting: The module itself
</strong></code></pre>

If the system is successfully enabled, you will typically see 2 embeds; one stating the settings have been saved, and another displaying the settings for the current system.&#x20;

#### Forcing module state

If you wish to force enable or disable the module rather than toggling it, use the `overwrite` argument. When this argument is set to `true`, the system will be explicitly enabled, otherwise the argument `false` will disable this system.

### Logging

When a ticket is closed, a transcript can be generated containing the contents of the chat. This requires that a logging channel is set.

#### Enabling logging

To set a logging channel, provide any text channel of your choosing to the following command:

{% code title=">\_ " %}

```
/ticket log channel: <Text channel>
```

{% endcode %}

#### Disabling logging

To disable logging, simply run this command without any arguments:

{% code title=">\_" %}

```
/ticket log
```

{% endcode %}

### Ticket panels

To provide members a way to make a ticket, we use special messages called "ticket panels". These messages will contain a button, which will create a ticket when clicked.

#### Create a panel

To create a ticket panel, run the following command:

{% code title=">\_" %}

```
/ticket gui
```

{% endcode %}

#### Customisation

You may optionally provide a `title` and `description` for the ticket panel. If you wish to take more control over the design of the ticket panel, you may use `copy_channel` and `copy_message_id` to directly copy a message from a channel.&#x20;

### Learn more

* Ticket overwrites
* [Viewing your ticket settings](#viewing-your-settings)
* [Adding or removing members to tickets](#manage-ticket-members)
* Controlling who can and cannot close tickets

## Manage ticket members

By default, only the ticket author and the administrators of the server will be able to see the ticket. If the ticket is within a category, the ticket will inherit some permissions from that category.

#### Adding members or roles to the ticket

In order to add a member or role to the ticket, run the following command:

```
/ticket add target: <Member or role>
```

#### Removing members or roles from the ticket

In order to remove a member or role from the ticket, run the following command:

```
/ticket remove target: <Member or role>
```

## Viewing your settings

When the system is enabled, settings are typically shown after changing settings. In order to view the current settings, you can run the following command:

{% code title=">\_" %}

```
/ticket settings
```

{% endcode %}

<figure><img src="https://3463827031-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MNYdpLA_RQnpphNvzMQ%2Fuploads%2FDUzf1M0QPtCRTUuhgr3g%2Fimage.png?alt=media&amp;token=82a77067-b003-4f82-883f-174749d92ad2" alt="Image of the command output"><figcaption></figcaption></figure>

## Ticket overwrites