> For the complete documentation index, see [llms.txt](https://ticketking.xyz/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ticketking.xyz/docs/custom-commands/use-cases.md).

# Use cases

<i class="fa-crown">:crown:</i> **Premium feature.** What custom commands are good for, with examples.

## FAQ replies

Set the answer once and reuse it.

| Trigger        | Name             | When to use                             |
| -------------- | ---------------- | --------------------------------------- |
| `!faq.refund`  | Refund Policy    | Common billing questions                |
| `!faq.rules`   | Server Rules     | Members asking what is allowed          |
| `!faq.discord` | Discord Tutorial | New users confused about Discord itself |

Each command's response can be a clear embed with the answer. A staff member types the trigger, the bot posts the response, and the conversation moves on.

## Wrong-ticket nudges

When a member opens a ticket on the wrong option, use a saved redirect instead of writing one each time.

| Trigger        | Name                                  |
| -------------- | ------------------------------------- |
| `!wrongticket` | Polite redirect to the correct option |

Sample content:

> You have created the wrong ticket or used the wrong ticket for your support request, please create the correct ticket.

Set it to **Ticket Only** so it can use the `{USER}` and `{TICKET_NUMBER}` placeholders.

## Quick greetings

Make ticket openings feel personal without typing each time.

| Trigger  | Name                                                                                           |
| -------- | ---------------------------------------------------------------------------------------------- |
| `!greet` | "Hello {USER}! Thanks for opening ticket #{TICKET\_NUMBER}. Someone will be with you shortly." |

Set it to Ticket Only so the placeholders are filled in.

## Common troubleshooting steps

The first replies a support team types over and over.

| Trigger    | Name                                        |
| ---------- | ------------------------------------------- |
| `!restart` | "Have you tried restarting the bot or app?" |
| `!update`  | "Make sure you are on the latest version."  |
| `!cache`   | "Try clearing your cache."                  |

## Pointers and links

| Trigger     | Name                                                |
| ----------- | --------------------------------------------------- |
| `!ping`     | A quick "I'm here"                                  |
| `!escalate` | Points the member to the escalation channel or role |
| `!docs`     | Sends a link to your docs                           |

## What custom commands cannot do

* They cannot take moderation actions. They cannot ban, mute, or kick. They only send a response.
* They only fire when someone types the trigger text. There is no "when X happens, do Y" behavior.

## Combined with link buttons

A useful pattern is a response that includes a link button.

For example, `!docs` with the text "Here is our docs page." and a link button labeled "Read Docs" that opens your docs page. The member sees the text and a button that goes straight to the resource.

## Tips

* Choose triggers your staff will remember. `!faq.refund` is easier to recall than `!fr1`.
* Use **Delete Command Message** for one-off responses to keep the channel tidy.
* Use **Reply to Command Message** to keep the response attached to the member's message.
* Mark ticket-specific commands as **Ticket Only** so they do not fire in other channels.
* Keep a list of your custom commands somewhere your staff can read.

## Related

{% content-ref url="/pages/reYPizVLVHsc3ThwnHHX" %}
[Creating a custom command](/docs/custom-commands/creating-a-command.md)
{% endcontent-ref %}

{% content-ref url="/pages/ubV1L6dUEUGdjD9IyaxC" %}
[What custom commands are](/docs/custom-commands/overview.md)
{% endcontent-ref %}


---

# 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://ticketking.xyz/docs/custom-commands/use-cases.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.