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

# Contact Support

How to reach the AOH Sync support team when you need help.

## Before you reach out

Working through the documentation first often saves time. Check:

* [Troubleshooting](/help-and-support/troubleshooting.md) — symptoms and step-by-step resolutions for the most common issues
* [FAQ](/help-and-support/faq.md) — answers to frequent questions about sync behavior, access, and data

If the issue is not covered there, the information below will get you to the right person quickly.

## Email support

Send a message to **<support@aohwv.dev>** for any issue that is not an active outage.

To help us respond without back-and-forth, include:

| What to include                 | Where to find it                             |
| ------------------------------- | -------------------------------------------- |
| Your organization name          | Shown in the top navigation bar              |
| A description of the issue      | What you were trying to do and what happened |
| The exact error message or code | Copy the text or attach a screenshot         |
| When the issue started          | Approximate date and time                    |
| Steps you have already tried    | Helps us skip suggestions you have ruled out |

## Documentation site

The full AOH Sync documentation is available at **<https://docs.aohwv.dev>**. Use it to browse all feature guides, concepts, and administration topics.

## What to expect

{% hint style="info" %}
Support is staffed during business hours. For critical issues — complete sync failures or inability to log in — flag your email as urgent in the subject line so it routes to the on-call queue.
{% endhint %}

| Priority | Definition                            | First response target   |
| -------- | ------------------------------------- | ----------------------- |
| Critical | Complete outage, no workaround        | Within 1 business hour  |
| High     | Major feature broken                  | Within 4 business hours |
| Standard | Partial impairment, workaround exists | Within 1 business day   |

## Related

* [Troubleshooting](/help-and-support/troubleshooting.md)
* [FAQ](/help-and-support/faq.md)


---

# 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.aohwv.dev/help-and-support/contact.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.