> For the complete documentation index, see [llms.txt](https://docs.aloop.icustomer.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aloop.icustomer.ai/using-audience-loop/meet-chat/ask-anything.md).

# Ask anything

Chat isn't only for setting goals. Ask it anything about your growth, and it answers from your own data.

Ask it to explain performance ("why did LinkedIn CAC jump last week?"), run root-cause analysis on an ad account, pressure-test a budget, or size an opportunity. Because the Harness sits on your unified data — audiences, signals, spend, and outcomes joined by one trace ID — the answers are grounded in what actually happened, not a channel tool's version of it.

Think of it as your most important growth marketing engineer, on call: fluent in your numbers, able to dig into the "why," and ready to turn an answer into a next step.


---

# 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.aloop.icustomer.ai/using-audience-loop/meet-chat/ask-anything.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.