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

# How to contact Aviz Networks Support?

## Contact Support <a href="#contact-support" id="contact-support"></a>

The Aviz Network Support team can be reached by&#x20;

1. Sending an email to <support@aviznetworks.com>
2. Submitting a Ticket at <https://support.aviznetworks.com/hc/en-us/requests/new>
3. Live Chat on [https://support.aviznetworks.com](https://support.aviznetworks.com/)

## Submitting a Ticket <a href="#submitting-a-ticket" id="submitting-a-ticket"></a>

A ticket can be submitted with or without an account at the [support portal](https://support.aviznetworks.com/hc/en-us/requests/new)

Mandatory Fields:

* Subject
* Issue Type (Post Deployment, Pre-Deployment, General Query, RMA)
* Priority (Low, Normal, High, Urgent)
* Description

Optional Fields:

* External ID (Community Request ID or Past Case Number)
* Hardware (Switch Model)
* ASIC vendor (chipset)
* Serial Number
* Host Name
* Attachments (Tech Support Dump, Screenshots, Logs)

For Technical Issues, we recommend the description include the following:

* Repro steps, if the issue is reproducible
* The sequence of events that lead to the failure state
* Artefacts - Tech Support dump (tar.gz file), Logs, Command Outputs, Topology Diagrams etc...


---

# 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://aviznetworks.gitbook.io/ftas/support/how-to-contact-aviz-networks-support.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.