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

# Support

How to contact Caliber and what to include in a support report.

## Reach a human

Email your Caliber contact or **<support@caliber-ai.dev>** / the address your account team provided for production support.

## What to include

1. Organization name as shown in Caliber
2. Your role (admin / team lead / member) and email
3. Page URL or Settings path where you see the issue
4. Integration involved (if any) and approximate time (include timezone)
5. Whether the issue started after a new connect, MDM push, or invite

Do **not** paste production Admin API keys, ingest tokens, or private keys into email threads. Rotate anything you accidentally shared ([Offboarding](/trust/offboarding-and-data-deletion.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 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.trycaliber.ai/trust/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.
