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

# Support & Community

Official customer assistance and verified links for Zynox Development

***

## 🎧 Official Verified Channels

We take customer satisfaction and script reliability seriously. If you encounter bugs, installation problems, or compatibility questions with any of our resources, our dedicated support team is available 24/7.

* 💬 **Discord**: [**discord.gg/2yuPTmsqjX**](https://discord.gg/2yuPTmsqjX) *(Open a ticket in `#tickets`)*
* 🛍️ **Tebex Store**: [**zynoxdev.tebex.store**](https://zynoxdev.tebex.store/)
* 🔑 **Cfx.re Keymaster Grants**: [**keymaster.fivem.net/asset-grants**](https://keymaster.fivem.net/asset-grants)
* 📺 **YouTube Previews**: [**youtube.com/@ZynoxDevelopment**](https://www.youtube.com/@ZynoxDevelopment)
* 🐙 **GitHub Organization**: [**github.com/zynoxdevelopment**](https://github.com/zynoxdevelopment)
* 🌐 **Cfx.re Forum**: [**forum.cfx.re/u/zynoxdev**](https://forum.cfx.re/u/zynoxdev/summary)
* 📱 **TikTok**: [**tiktok.com/@zynoxdev**](https://www.tiktok.com/@zynoxdev)
* ✉️ **Support Email**: `support@zynoxdev.com`

***

## 🎫 How to Open a Support Ticket

To ensure the fastest possible resolution, follow these steps when requesting assistance:

### 1. Join & Verify

1. Join our Discord community at [**discord.gg/2yuPTmsqjX**](https://discord.gg/2yuPTmsqjX).
2. Link your Cfx.re account or provide your **Tebex Transaction ID** (starts with `tbx-...`) in `#verify-customer`.
3. You will automatically receive the verified **Customer** role.

### 2. Open a Dedicated Script Ticket

1. Go to the `#tickets` channel.
2. Click **Create Ticket** and select the resource category.
3. Paste the completed support checklist below in your first message.

***

## 📋 Ticket Support Checklist

Please have this information ready when opening a ticket:

```
1. Resource Name: (e.g. ZX Restart Warning or ZX Loading Screen)
2. Framework: (Qbox / QBCore / ESX / Standalone)
3. FXServer Artifact Build: (e.g. 5848, 6683, etc.)
4. Issue Description: (What happens, what was expected)
5. Screenshots / F8 Console Errors: (Attach any client or server error logs)
6. Transaction ID: (tbx-xxxxxxxxxxxx)
```

> \[!TIP] Always check the **Troubleshooting & FAQ** section of the specific resource before creating a ticket. Most setup queries (e.g. NUI CEF audio muting, missing ACE permissions) are solved there in under 2 minutes!

***

-# © 2026 Zynox Development • Built for Elite FiveM Communities


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://zynoxdev.gitbook.io/docs/support.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.