> For the complete documentation index, see [llms.txt](https://docs.bossithq.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bossithq.com/points/points-history-for-a-customer.md).
# Points History for a Customer
To view the record of points earned and used for a specific customer:
1. In the [**Admin Portal**](https://admin.gobossit.com/)**,** go to the **group level.**
2. Navigate to **Consumers**.
3. Locate the customer.
* You can search by customer's **name, phone number, or email address.**
4. Click the customer.
## Details tab
On the **Details** tab, you can see the customer's **Points Balance**.
## Points tab
On the **Points** tab, you have a detailed history of the **amount of points earned or used**. You can click on **Order** to go to the specific order tied to the points earn or used.
You can also:
* Filter by type and/or source.
* Select a date range.
* Export to XSLX.
---
# 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.bossithq.com/points/points-history-for-a-customer.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.