> For the complete documentation index, see [llms.txt](https://docs.freeflysystems.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.freeflysystems.com/astro/pilots-operating-handbook/getting-technical-support.md).

# Getting Technical Support

Freefly prides itself in providing the best technical support in the industry. You can send us a message any time, and our staff will get back to you as soon as possible. 

Our office hours are Mon-Fri, 8am - 4pm PST. 

### How to get in touch

1. Use our [contact page](https://freeflysystems.com/contact) (preferred)
2. Send an email directly to [support@freeflysystems.com](emailto:support@freeflysystems.com)
3. While you wait for a response, try using the AI search below for a quick answer to your questions that can be found on this guide. Since this is an aircraft, always be sure to verify information. <br>

{% hint style="info" %}
AI can make mistakes. If you're not sure, just contact us directly to verify information.&#x20;

Freefly is not liable for any mistakes that the AI generates for you.
{% endhint %}

<button type="button" class="button primary" data-action="ask" data-icon="sparkles">Ask a question…</button>

### Getting your issues resolved faster

When you reach out to our support team, there are a few things that are commonly going to be asked. To reduce the time it takes to get to a solution, it's best to provide as much detail as possible, including:

1. Your aircraft's serial number. For Astro, this will be found on the bottom chassis. \ <img src="/files/Gw32SJeyH04n4jyzaYB3" alt="" data-size="original">
2. Any photos and/or videos that can clearly demonstrate the issue.
3. Flight logs, even if the issue(s) took place on the ground. [How to send logs](/ecosystem/software/flight-logs.md).
4. Any other relevant information, including current firmware version, pilot statements, 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://docs.freeflysystems.com/astro/pilots-operating-handbook/getting-technical-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.