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

# Help

Reach the Chirp support team — fill out the built-in contact form with your subject, email, and details.

Spotted a bug, wishing Chirp did something it does not, or want it to work with a device it does not yet support? The Chirp support team is ready to help. A quick contact form is built right into the interface and sends your message straight to **support \[at] chirpwireless.io**.

<figure><img src="https://1153890212-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxgYoHO4zlaBzHJcfIrto%2Fuploads%2Fgit-blob-42f2b779ef909cf1bdc147984432d2dfe95fd6a3%2Fsend-feedback.jpg?alt=media" alt="The Support request dialog with the Subject dropdown open, showing Bug report, Feature request and Integration request"><figcaption></figcaption></figure>

## Filling Out the Form

* **Subject** (required) -- pick one of three from the dropdown: **Bug report**, **Feature request** or **Integration request**. It tells the team what sort of message they are about to read.
* **Email address** (required) -- this is pre-filled with the email on your account. Change it if you would rather get the reply somewhere else.
* **Description** (required) -- tell the team what is going on. The more detail you include, the faster they can jump in. The form reminds you: *"Please describe as much as possible and make your text clear."*

### Picking the right subject

* **Bug report** — something is not working the way it should. The single most useful thing you can write is what you did, what happened, and what you expected to happen instead.
* **Feature request** — Chirp cannot do something you wish it could. Tell them what you are trying to achieve rather than the button you think you need; quite often there is already a way to do it.
* **Integration request** — you have a sensor, hub or service you would like Chirp to work with. Give the exact make and model, otherwise the team is guessing.

## Sending and Closing

Click **Send request** to fire off your message. When it goes through, you will see *"Request has been successfully sent"* and the form closes on its own. If something goes wrong, an error notification pops up so you can give it another try.

Click **Cancel** to close the form without sending anything.


---

# 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.chirpwireless.io/get-help.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.
