> For the complete documentation index, see [llms.txt](https://docs.maker.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.maker.co/maker-greatstore/insights-and-usage/chats.md).
# Reading chats
**Chats** lists every conversation, newest first, each marked `Active` or `Ended` with the opening exchange as a preview. Select one to read it in full.
Chats — every shopper conversation, newest first
## Location awareness
The assistant knows the shopper's approximate location from their IP address, and uses it as context — ask it "find the nearest store to me" and it starts from the shopper's city, then narrows down from whatever detail they give it. Pair this with a store-locations document in [Adding sources](/maker-greatstore/knowledge/adding-sources.md) and nearest-store questions answer themselves.
## Why read them
Chats are the fastest way to find gaps. A shopper asking something the assistant could not answer usually means a missing knowledge source. A shopper struggling to find a product usually means a connector or catalogue problem.
{% hint style="info" %}
Conversations appear here within moments of happening, so this is also the quickest way to confirm a fresh install is working.
{% endhint %}
---
# 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.maker.co/maker-greatstore/insights-and-usage/chats.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.