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

# Contact Technical Support

Select [**Customer Support**](https://dryadnetworks.zendesk.com/hc/en-001/requests/new) and in the form that appears enter the following information:

* **Email** (required): Enter your company email address.
* **CC**: Another contact email address that may be helpful.
* **Full name** (required): Enter your full name.
* **Customer Type** (required): Select from
  * Reseller
  * End Customer
  * I am not a customer
* **Request Type** (required): Select from
  * Product Information
  * Payment & Billing
  * Shipping & Delivery
  * Deployment Assistance
  * Using Silvanet
  * About Dryad
* **Description** (required): Enter a detailed description of the nature of your request. If your request is about a Dryad device, provide a Device Name (for example Pilot 2 MG 5) or Device ID (for example, mg-2m2nXX-641XXX000XXXXXXX).
* **Attachments**: Attach a document, image file or other file type that helps explain your request.

Select **Submit** to send your request to Dryad Customer Service.

An email is immediately sent to the email address provided indicating Customer Support has received your request.


---

# 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://docs.dryad.app/dryad-documentation/resources/contact-technical-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.