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

# Prompts

Prompts are the questions Reach monitors across AI engines. They define the demand you are measuring, so prompt quality directly affects the usefulness of every visibility report.

## Review the prompt set

Use the Prompts page to:

* search and filter monitored questions;
* review performance by prompt;
* organize prompts by topic, label, audience, use case, or journey stage;
* disable prompts that no longer matter; and
* inspect suggested prompts before adding them to monitoring.

## Choose useful prompts

A strong prompt:

* represents a question a real buyer could ask;
* describes a problem, comparison, category, or decision;
* is understandable without internal company language; and
* is meaningfully different from the rest of the set.

Avoid filling the workspace with minor wording variations. A smaller, representative set produces clearer analysis than a large set of near-duplicates.

## Open prompt detail

Select a prompt to review its results over time. The detail view helps answer:

* which AI engines mention the brand;
* which competitors are recommended;
* which pages and domains are cited; and
* how the answer changed between runs.

Use single-day detail when you need to inspect the exact answer and evidence behind an aggregate metric.

## Keep the set current

Review prompts when the company launches a product, enters a market, changes positioning, or learns that customers use different language. Document material changes so period comparisons remain understandable.


---

# 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.usereach.ai/understand-your-visibility/prompts.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.