> For the complete documentation index, see [llms.txt](https://docs.samita.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.samita.io/sa-request-a-quote/quote-page-quote-history/how-customers-view-the-quote-history-page.md).

# How customers view the “Quote History” page?

Currently customers can view quote history in the customer account page after he logged in. 

If you want to let customers access the quote history quickly, please follow the steps below.

1. The admin should[ **add the Quote History item**](https://help.samita.io/docs/b2b-request-a-quotehide-price/settings-2/how-to-display-the-quote-history-item-on-the-header-menu/) to the header menu of the website
2. Customer logs in his customer account on the site 
3. He clicks on the **Quote history** item the admin added to the header menu to view quote history


---

# 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.samita.io/sa-request-a-quote/quote-page-quote-history/how-customers-view-the-quote-history-page.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.