> 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/how-it-works/overview/audience-context.md). # Audience context Audience context is the system's picture of *who* you sell to. It's the foundation the Harness scores and decides against — built during onboarding from public information, then sharpened by your connected tools. It covers: * **Ideal Customer Profile (ICP)** — the firmographic and fit criteria that define a good-fit account. * **Buyer personas** — the roles and people who evaluate and buy. * **Audience intelligence** — what the system has learned about how your audiences behave and respond. * **Business pain areas** — the problems your product solves, in your buyers' terms. Keep this accurate and current: every [FIRE score](/using-audience-loop/explorer/fire-scoring.md) and decision leans on it. --- # 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/how-it-works/overview/audience-context.md?ask=&goal= ``` `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.