> For the complete documentation index, see [llms.txt](https://guide.tiledesk.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guide.tiledesk.com/guides-for-human-agents/browsing-past-chats-in-history.md).

# Browsing past chats in History

#### History tab: whereabouts & purpose <a href="#history-tab-whereabouts-purpose" id="history-tab-whereabouts-purpose"></a>

From History tab on the dashboard, you can review details about your visitors and chats, like in the example below. To make your search easier, you can simply use the search bar by typing key words or ticket IDs. You can also export your

<figure><img src="https://1328774413-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FVguk6y5OMn3pAaHZSiwU%2Fuploads%2FKMcuS8lIAGl8XdsUem0A%2F1v1rrz-image.png?alt=media&amp;token=3130f4c8-3da6-4603-93c5-3928ba424e33" alt=""><figcaption></figcaption></figure>

You can also opt for an advanced search by filtering agents by clicking on the ⬇️ symbol at the right of the search bar that lets you filter conversation by agent, date, tag, department and conversation type.

<figure><img src="https://1328774413-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FVguk6y5OMn3pAaHZSiwU%2Fuploads%2FwVaSBaAp9Z3iDmGS2zGC%2F1v1rx8-image.png?alt=media&amp;token=379e3346-b3cd-4422-9bcf-9d8db5f1a8a4" alt=""><figcaption></figcaption></figure>

For more info on who we are, what we do, or what is our shtick, visit[ Tiledesk.com](https://tiledesk.com/) 👩‍🚀


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://guide.tiledesk.com/guides-for-human-agents/browsing-past-chats-in-history.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
