> For the complete documentation index, see [llms.txt](https://invomagic.gitbook.io/ticketsdocs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://invomagic.gitbook.io/ticketsdocs/pro/whitelabel.md).

# Tickets Whitelabel

{% hint style="warning" %}
This is an experiment, not all servers have it

Request an experiment: <https://s.dscinv.xyz/support>
{% endhint %}

<figure><img src="/files/EKTBx80yB8mUd3t02q3u" alt="" width="450"><figcaption></figcaption></figure>

Tickets Whitelabel allows you to fully customize Tickets's appearance  to your liking!\
This includes The Avatar, Banner, and Bio that shows up in your server!\
This way Tickets looks like it is at the center of your server being all proper and personal

## Whitelabel Usage

### Setup

Run `/whitelabel` and add the images you wish (Limited to jpg, jpeg, and png)

<figure><img src="/files/WRq2R3SS4sz65arYoynz" alt="" width="375"><figcaption></figcaption></figure>

You will see a menu with buttons pop up, this menu willl autoupdate when you make a changes

The buttons are as follows\
Change Avatar: Changes this the bot's avatar to the image you uploaded\
Change Name: Change's the bot's name via the name you'll select in a popup\
Change Bio: Changes the bot's bio via the text you'll select in a popup\
Change banner: Changes the bot's Banner to the image you uploaded\
Reset to Normal: Resets Tickets's appearance to normal via clearing custom settings\
Write Bio with AI: Automatically Generates a Bio for you to use based on the bot's name and the server's name

#### Examples

**This Configuration**

<figure><img src="/files/RcsVn4hxPt8C1ZWJXFyR" alt="" width="375"><figcaption></figcaption></figure>

**Makes the bot look like this**

<figure><img src="/files/L7WoAlMDsxicdXNv38pO" alt="" width="375"><figcaption></figcaption></figure>

### Whitelabel Examples

Below are some examples of whitelabels you could do!\
The Sky's the limit!

{% tabs %}
{% tab title="Kaito" %}

<figure><img src="/files/ZcU5YwtL6ceHNPVaFrIC" alt="" width="375"><figcaption></figcaption></figure>
{% endtab %}

{% tab title="Astro" %}

<figure><img src="/files/1wjq3hZMlZwTAJ6X6tdN" alt="" width="375"><figcaption></figcaption></figure>
{% endtab %}

{% tab title="Wizardly" %}

<figure><img src="/files/o3uhbLNBca7L828Tbxbp" alt="" width="375"><figcaption></figcaption></figure>
{% endtab %}

{% tab title="Bunny" %}

<figure><img src="/files/XdbDFQTHRBkJzQP4tLFr" alt="" width="375"><figcaption></figcaption></figure>
{% endtab %}

{% tab title="Rainbow Utility" %}

<figure><img src="/files/4aZP0EC6w6aP7Rt7tE06" alt="" width="375"><figcaption></figcaption></figure>
{% endtab %}
{% endtabs %}

We currently monitor the whitelabels you create to figure out whether or not you are abusing it.

## Experiment

This is the currently an **experiment** currently, TicketsPRO Servers are eligible however this will likely change to a separate payment from TicketsPRO when this feature we feel is ready for full wide usage\
To request approval please go to our [Support Server](https://s.dscinv.xyz/support) and ask


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://invomagic.gitbook.io/ticketsdocs/pro/whitelabel.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.